GHSA-8r5v-vm4m-4g25 — h2
Fix: hyperium/h2#737GHSA-8r5v-vm4m-4g25 is a security vulnerability in h2. A fix is available for h2 — see the affected versions and patch details below.
Resource exhaustion vulnerability in h2 may lead to Denial of Service (DoS)
Real-World Exposure
h2🦀h2Real-time download stats are indexed for npm and PyPI packages. This vulnerability affects crates.io packages — download data is not available via public APIs for these ecosystems.
Description
An attacker with an HTTP/2 connection to an affected endpoint can send a steady stream of invalid frames to force the generation of reset frames on the victim endpoint. By closing their recv window, the attacker could then force these resets to be queued in an unbounded fashion, resulting in Out Of Memory (OOM) and high CPU usage.
This fix is corrected in hyperium/h2#737, which limits the total number of internal error resets emitted by default before the connection is closed.
Affected Packages
| Ecosystem | Package | Vulnerable range | Fix |
|---|---|---|---|
| 🦀crates.io | h2 | all versions | 0.3.24cargo update -p h2 --precise 0.3.24 |
| 🦀crates.io | h2 | ≥ 0.4.0&&< 0.4.2 | 0.4.2cargo update -p h2 --precise 0.4.2 |
Detection & mitigation playbook
Open-source dependencyDetect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for h2, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update h2 to 0.3.24 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-8r5v-vm4m-4g25 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-8r5v-vm4m-4g25 can be triaged on real exposure rather than presence alone.
Tailored to GHSA-8r5v-vm4m-4g25. Runtime protection reduces exposure until a permanent patch is applied and verified — it complements patching, it doesn't replace it.
Frequently Asked Questions
Is GHSA-8r5v-vm4m-4g25 in your dependencies?
O3 Security finds GHSA-8r5v-vm4m-4g25 across crates.io dependencies, including transitive ones, and its impact-aware SCA ranks findings by whether your code actually calls the vulnerable path.