How severe is GHSA-39qc-96h7-956f?

GHSA-39qc-96h7-956f has a CVSS score of 7.5/10, rated HIGH. Immediate patching is strongly recommended.

Which packages are affected by GHSA-39qc-96h7-956f?

GHSA-39qc-96h7-956f affects the following packages: golang.org/x/net (Go). Ecosystems affected: Go.

How do I fix GHSA-39qc-96h7-956f?

Update golang.org/x/net to 0.0.0-20190813141303-74dc4d7220e7 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-39qc-96h7-956f is resolved across your whole dependency graph.

How do I detect GHSA-39qc-96h7-956f in my Go dependencies?

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

How do I mitigate GHSA-39qc-96h7-956f if there is no patch (or I can't update yet)?

If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.

How does O3 Security protect against GHSA-39qc-96h7-956f?

O3 Security's impact-aware SCA analyses which vulnerable code paths your application actually calls, so a match like GHSA-39qc-96h7-956f can be triaged on real exposure rather than presence alone.

Is GHSA-39qc-96h7-956f actively exploited in the wild?

No public exploit code has been indexed for GHSA-39qc-96h7-956f 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-39qc-96h7-956f?

GHSA-39qc-96h7-956f has an EPSS (Exploit Prediction Scoring System) score of 83.4%, placing it in the 100th 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. A score above 50% indicates significantly elevated exploitation risk — immediate patching is strongly recommended.

What type of vulnerability is GHSA-39qc-96h7-956f?

GHSA-39qc-96h7-956f is classified as Uncontrolled Resource Consumption (CWE-400). This weakness type describe the underlying flaw category, which helps determine the potential impact and the right class of mitigation.

When was GHSA-39qc-96h7-956f published, and has it been updated?

GHSA-39qc-96h7-956f was published on May 24, 2022 and was last updated on September 10, 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

HIGH severity

GHSA-39qc-96h7-956f — net

HIGH

GHSA-39qc-96h7-956f is a high-severity (CVSS 7.5) Uncontrolled Resource Consumption vulnerability in golang.org/x/net. EPSS puts its 30-day exploitation probability at 83.4% (100th percentile). A fix is available for golang.org/x/net — see the affected versions and patch details below.

golang.org/x/net/http vulnerable to a reset flood

Also known asCVE-2019-9512 CVE-2019-9514 GHSA-hgr8-6h9x-f7q9GO-2022-0536

Published

May 24, 2022

Updated

Sep 10, 2026

Affected

1 pkg

Patched

1 / 1

Exploits

None indexed

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

EPSS Exploitation Probability

via FIRST.org ↗

83.4%probability of exploitation in next 30 days

Very High Risk0.00%

Lower risk than most CVEs100th percentile — riskier than 100% of all scored CVEsHighest risk

EPSS (Exploit Prediction Scoring System) is a daily probability model maintained by FIRST.org. It estimates the likelihood a CVE will be exploited in production environments within the next 30 days, derived from real-world threat intelligence signals.

How urgent is this, really

GHSA-39qc-96h7-956f plotted by exploitation likelihood (EPSS) against impact (CVSS). The shaded corner — EPSS 50%+ and CVSS 7.0+ — is where this CVE sits: patch-first territory.

Where this sits among everything scored

Of 376,715 CVEs with a current EPSS score, this one falls in the 50–90% band (highlighted). Real counts from FIRST.org, not a sample — log-scaled since the landscape is heavily right-skewed.

Real-World Exposure

1 pkg affected

🐹golang.org/x/net

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

Some HTTP/2 implementations are vulnerable to a reset flood, potentially leading to a denial of service. Servers that accept direct connections from untrusted clients could be remotely made to allocate an unlimited amount of memory, until the program crashes. The attacker opens a number of streams and sends an invalid request over each stream that should solicit a stream of RST_STREAM frames from the peer. Depending on how the peer queues the RST_STREAM frames, this can consume excess memory, CPU, or both.

Specific Go Packages Affected

golang.org/x/net/http2

Affected Packages

1 total 1 fixed

Ecosystem	Package	Vulnerable range	Fix
🐹Go	`golang.org/x/net`	all versions	0.0.0-20190813141303-74dc4d7220e7`go get golang.org/x/net@v0.0.0-20190813141303-74dc4d7220e7`

Detection & mitigation playbook

Open-source dependency

Detect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for golang.org/x/net, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update golang.org/x/net to 0.0.0-20190813141303-74dc4d7220e7 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-39qc-96h7-956f is resolved across your whole dependency graph.
Workarounds
If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.
How O3 protects you
O3 Security's impact-aware SCA analyses which vulnerable code paths your application actually calls, so a match like GHSA-39qc-96h7-956f can be triaged on real exposure rather than presence alone.

Tailored to GHSA-39qc-96h7-956f. Runtime protection reduces exposure until a permanent patch is applied and verified — it complements patching, it doesn't replace it.

Fixing This On Your OS

If you run this on a Linux distribution, patch through your package manager against the distro's own security advisory below — it tracks the exact backported fix for your release, which can ship on a different timeline (and sometimes a different severity) than the upstream project.

Red HatImportant

The golang package in Red Hat OpenStack Platform 9 Operational Tools will not be updated for this flaw because it is in technical preview and is retiring as of 24.Aug.2019. This issue did not affect the versions of grafana(embeds golang) as shipped with Red Hat Ceph Storage 2 and Red Hat Gluster Storage 3 as they did…

Product	Fixed in	Advisory
Red Hat AMQ	see advisory	RHSA-2020:0922
Red Hat AMQ 7.4.3	see advisory	RHSA-2020:1445
Red Hat Data Grid 7.3.3	`netty`	RHSA-2020:0727
Red Hat Decision Manager 7	`netty`	RHSA-2020:3196
Red Hat Developer Tools	`go-toolset-1.11-0:1.11.13-1.el7`	RHSA-2019:2682
Red Hat Enterprise Linux 7 Extras	`containernetworking-plugins-0:0.8.1-4.el7_7`	RHSA-2020:0406
Red Hat Enterprise Linux 8	`go-toolset:rhel8-8000120190828225436.14bc675c`	RHSA-2019:2726
Red Hat Enterprise Linux 8	`nodejs:10-8000020190911085529.f8e95b4e`	RHSA-2019:2925

Frequently Asked Questions

O3 Security · Impact-Aware SCA

Is GHSA-39qc-96h7-956f in your dependencies?

O3 Security finds GHSA-39qc-96h7-956f across Go dependencies, including transitive ones, and its impact-aware SCA ranks findings by whether your code actually calls the vulnerable path.

Scan my dependencies How O3 SCA works