How severe is GHSA-8r5v-vm4m-4g25?

No CVSS score has been assigned to GHSA-8r5v-vm4m-4g25 yet. Review the advisory details and affected package list to assess your exposure.

Which packages are affected by GHSA-8r5v-vm4m-4g25?

GHSA-8r5v-vm4m-4g25 affects the following packages: h2 (crates.io), h2 (crates.io). Ecosystems affected: crates.io.

How do I fix GHSA-8r5v-vm4m-4g25?

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.

How do I detect GHSA-8r5v-vm4m-4g25 in my crates.io dependencies?

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.

How do I mitigate GHSA-8r5v-vm4m-4g25 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.

Is GHSA-8r5v-vm4m-4g25 actively exploited in the wild?

No public exploit code has been indexed for GHSA-8r5v-vm4m-4g25 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.

When was GHSA-8r5v-vm4m-4g25 published, and has it been updated?

GHSA-8r5v-vm4m-4g25 was published on January 19, 2024 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.

Resource exhaustion vulnerability in h2 may lead to…

Real-World Exposure

2 pkgs affected

🦀h2🦀h2

Real-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

2 total 2 fixed

Ecosystem	Package	Vulnerable range	Fix
🦀crates.io	`h2`	all versions	0.3.24`cargo update -p h2 --precise 0.3.24`
🦀crates.io	`h2`	≥ 0.4.0&&< 0.4.2	0.4.2`cargo update -p h2 --precise 0.4.2`

Detection & mitigation playbook

Open-source dependency

Detect
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.

Frequently Asked Questions

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](https://github.com/hyperium/h2/pull/737), which limits the total number of internal error resets emitted by default before the connection is closed.

O3 Security · Impact-Aware SCA

Is GHSA-8r5v-vm4m-4g25 in your dependencies?

Find it across crates.io, including transitive dependencies.

Scan my dependencies How O3 SCA works

Resource exhaustion vulnerability in h2 may lead to Denial of Service (DoS)GHSA-8r5v-vm4m-4g25