How severe is GHSA-hgr8-6h9x-f7q9?

GHSA-hgr8-6h9x-f7q9 has a CVSS score of 7.5/10, rated HIGH. Immediate patching is strongly recommended.

Which packages are affected by GHSA-hgr8-6h9x-f7q9?

GHSA-hgr8-6h9x-f7q9 affects the following packages: golang.org/x/net (Go). Ecosystems affected: Go.

How do I fix GHSA-hgr8-6h9x-f7q9?

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-hgr8-6h9x-f7q9 is resolved across your whole dependency graph.

How do I detect GHSA-hgr8-6h9x-f7q9 in my Go dependencies?

Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for golang.org/x/net. O3's reachability analysis confirms whether the vulnerable code path is actually invoked in your application, so you act on real exposure instead of every transitive match.

How do I mitigate GHSA-hgr8-6h9x-f7q9 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-hgr8-6h9x-f7q9?

O3 pinpoints whether GHSA-hgr8-6h9x-f7q9 is reachable in your code and exactly where to fix it, then blocks exploitation in production at runtime until the patched version is deployed.

Is GHSA-hgr8-6h9x-f7q9 actively exploited in the wild?

No public exploit code has been indexed for GHSA-hgr8-6h9x-f7q9 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 type of vulnerability is GHSA-hgr8-6h9x-f7q9?

GHSA-hgr8-6h9x-f7q9 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-hgr8-6h9x-f7q9 published, and has it been updated?

GHSA-hgr8-6h9x-f7q9 was published on May 24, 2022 and was last updated on February 4, 2026. Advisory data evolves as severity scores, affected ranges, and exploit intelligence are revised — always check the latest version of the advisory before acting.

GHSA-hgr8-6h9x-f7q9: golang.org/x/net/http vulnerable to ping f…

Blast Radius

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 ping floods, potentially leading to a denial of service. The attacker sends continual pings to an HTTP/2 peer, causing the peer to build an internal queue of responses. Depending on how efficiently this data is queued, this can consume excess CPU, memory, 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

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. O3's reachability analysis confirms whether the vulnerable code path is actually invoked in your application, so you act on real exposure instead of every transitive match.
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-hgr8-6h9x-f7q9 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 pinpoints whether GHSA-hgr8-6h9x-f7q9 is reachable in your code and exactly where to fix it, then blocks exploitation in production at runtime until the patched version is deployed.

Tailored to GHSA-hgr8-6h9x-f7q9. Runtime protection reduces exposure until a permanent patch is applied and verified — it complements patching, it doesn't replace it.

Frequently Asked Questions

Some HTTP/2 implementations are vulnerable to ping floods, potentially leading to a denial of service. The attacker sends continual pings to an HTTP/2 peer, causing the peer to build an internal queue of responses. Depending on how efficiently this data is queued, this can consume excess CPU, memory, or both. ### Specific Go Packages Affected golang.org/x/net/http2

O3 Security · Impact-Aware SCA

Is GHSA-hgr8-6h9x-f7q9 in your dependencies?

O3 detects GHSA-hgr8-6h9x-f7q9 across Go dependencies and uses function-level reachability to confirm whether the vulnerable code path is actually reachable — not just present. No false positives.

Scan my dependencies How O3 SCA works

GHSA-hgr8-6h9x-f7q9