How severe is GHSA-jj6m-r8jc-2gp7?

GHSA-jj6m-r8jc-2gp7 has a CVSS score of 6.5/10, rated MEDIUM. Review your exposure and patch according to your risk tolerance.

Which packages are affected by GHSA-jj6m-r8jc-2gp7?

GHSA-jj6m-r8jc-2gp7 affects the following packages: github.com/pterodactyl/wings (Go). Ecosystems affected: Go.

How do I fix GHSA-jj6m-r8jc-2gp7?

Update github.com/pterodactyl/wings to 1.4.4 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-jj6m-r8jc-2gp7 is resolved across your whole dependency graph.

How do I detect GHSA-jj6m-r8jc-2gp7 in my Go dependencies?

Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for github.com/pterodactyl/wings, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.

How do I mitigate GHSA-jj6m-r8jc-2gp7 if there is no patch (or I can't update yet)?

Cap what an attacker can consume: apply request size, rate and timeout limits in front of the affected component, and run it with memory and CPU limits so exhaustion degrades one worker rather than the whole service.

Is GHSA-jj6m-r8jc-2gp7 actively exploited in the wild?

No public exploit code has been indexed for GHSA-jj6m-r8jc-2gp7 yet. This does not mean the vulnerability cannot be exploited — absence of public exploits does not imply safety. Apply the recommended fix and use O3 Security to monitor your exposure.

What is the EPSS score for GHSA-jj6m-r8jc-2gp7?

GHSA-jj6m-r8jc-2gp7 has an EPSS (Exploit Prediction Scoring System) score of 0.3%, placing it in the 17th percentile of all CVEs. EPSS is maintained by FIRST.org and estimates the probability that a vulnerability will be exploited in the wild within the next 30 days. This score indicates relatively lower exploitation probability, though the CVSS severity should still guide your patching priority.

What type of vulnerability is GHSA-jj6m-r8jc-2gp7?

GHSA-jj6m-r8jc-2gp7 is classified as Uncontrolled Resource Consumption (CWE-400), CWE-770 (CWE-770). These weakness types describe the underlying flaw category, which helps determine the potential impact and the right class of mitigation.

When was GHSA-jj6m-r8jc-2gp7 published, and has it been updated?

GHSA-jj6m-r8jc-2gp7 was published on June 23, 2021 and was last updated on July 8, 2026. Advisory data evolves as severity scores, affected ranges, and exploit intelligence are revised — always check the latest version of the advisory before acting.

🐹

🐹 Go

Not in CISA KEV

MEDIUM severity

Asymmetric Resource Consumption (Amplification) in Docker containers created by WingsGHSA-jj6m-r8jc-2gp7

MEDIUMFix: pterodactyl/wings@e0078ee

GHSA-jj6m-r8jc-2gp7 is a medium-severity (CVSS 6.5) Uncontrolled Resource Consumption vulnerability in github.com/pterodactyl/wings. A fix is available for github.com/pterodactyl/wings — see the affected versions and patch details below.

Also known asCVE-2021-32699GO-2022-0919

Published

Jun 23, 2021

Updated

Jul 8, 2026

Affected

1 pkg

Patched

1 / 1

Exploits

None indexed

Exploitation data as of Oct 12, 2026 · OSV.dev, NVD, FIRST.org (EPSS)

EPSS Exploitation Probability

via FIRST.org ↗

0.3%probability of exploitation in next 30 days

Lower Risk-0.00%

Lower risk than most CVEs17th percentile — riskier than 17% of all scored CVEsHighest risk

Probability of exploitation in the next 30 days, from FIRST.org EPSS.

How urgent is this, really

GHSA-jj6m-r8jc-2gp7 by exploitation likelihood (EPSS) against impact (CVSS). Outside the shaded patch-first corner.

Where this sits among everything scored

Of 385,738 CVEs with a current EPSS score, this one falls in the < 10% band (highlighted). Counts from FIRST.org, log-scaled.

Real-World Exposure

1 pkg affected

🐹github.com/pterodactyl/wings

Real-time download stats are indexed for npm and PyPI packages. This vulnerability affects Go packages — download data is not available via public APIs for these ecosystems.

Description

Impact

All versions of Pterodactyl Wings preior to 1.4.4 are vulnerable to system resource exhaustion due to improper container process limits being defined. A malicious user can consume more resources than intended and cause downstream impacts to other clients on the same hardware, eventually causing the physical server to stop responding.

Patches

Users should upgrade to 1.4.4.

Workarounds

There is no non-code based workaround for impacted versions of the software. Users running customized versions of this software can manually set a PID limit for containers created.

For more information

If you have any questions or comments about this advisory:

Contact us on Discord
Email us at dane ät pterodactyl dot io

Affected Packages

1 total 1 fixed

Ecosystem	Package	Vulnerable range	Fix
🐹Go	`github.com/pterodactyl/wings`	all versions	1.4.4`go get github.com/pterodactyl/wings@v1.4.4`

Affected Products

1 product · 1 configurations

Application

wingspterodactyl

< 1.4.4

range

Detection & mitigation playbook

Open-source dependency

Detect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for github.com/pterodactyl/wings, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update github.com/pterodactyl/wings to 1.4.4 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-jj6m-r8jc-2gp7 is resolved across your whole dependency graph.
Workarounds
Cap what an attacker can consume: apply request size, rate and timeout limits in front of the affected component, and run it with memory and CPU limits so exhaustion degrades one worker rather than the whole service.

Frequently Asked Questions

### Impact All versions of Pterodactyl Wings preior to `1.4.4` are vulnerable to system resource exhaustion due to improper container process limits being defined. A malicious user can consume more resources than intended and cause downstream impacts to other clients on the same hardware, eventually causing the physical server to stop responding. ### Patches Users should upgrade to `1.4.4`. ### Workarounds There is no non-code based workaround for impacted versions of the software. Users running customized versions of this software can manually set a PID limit for containers created. ### Fo

O3 Security · Impact-Aware SCA

Is GHSA-jj6m-r8jc-2gp7 in your dependencies?

Find it across Go, including transitive dependencies.

Scan my dependencies How O3 SCA works

CVSS Score

6.5/10CVSS v3 base

Vector breakdown

Attack Vector

Local

Attack Complexity

Low

Privileges Required

Low

User Interaction

None

Scope

Changed

Confidentiality

None

Integrity

None

Availability

High

Raw vector

CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:C/C:N/I:N/A:H

CWE Classification

CWE-400Uncontrolled Resource Consumption CWE-770CWE-770

Weaponization

No known public exploit tooling found.

OpenSSF Scorecard

Package health score

wings

6.1/10

Code-Review1/10

Maintained10/10

Branch-ProtectionN/A

Assessed Oct 5, 2026

Timeline

Disclosed

Jun 23, 2021

Last updated

Jul 8, 2026

Identifiers

GHSA-jj6m-r8jc-2gp7

GO-2022-0919

References

Advisorynvd.nist.gov Webgithub.com Webgithub.com Packagegithub.com

Related vulnerabilities

This CVE is medium severity; 8 of 8 other CVEs affecting wings are rated as high or higher (top: critical).

CVE-2026-52856CVE-2026-52855CVE-2026-52857CVE-2026-54593GHSA-rhq6-9rgh-v45cGHSA-hr7j-63v7-vj7gCVE-2026-21696CVE-2025-69199

Provenance

Sources

OSV.devNVDFIRST.org (EPSS)

Last verifiedJul 8, 2026