How severe is GHSA-393w-9x6h-8gc7?

No CVSS score has been assigned to GHSA-393w-9x6h-8gc7 yet. Review the advisory details and affected package list to assess your exposure.

Which packages are affected by GHSA-393w-9x6h-8gc7?

GHSA-393w-9x6h-8gc7 affects the following packages: pingora-core (crates.io). Ecosystems affected: crates.io.

How do I fix GHSA-393w-9x6h-8gc7?

Update pingora-core to 0.6.0 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-393w-9x6h-8gc7 is resolved across your whole dependency graph.

How do I detect GHSA-393w-9x6h-8gc7 in my crates.io dependencies?

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

How do I mitigate GHSA-393w-9x6h-8gc7 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-393w-9x6h-8gc7 actively exploited in the wild?

No public exploit code has been indexed for GHSA-393w-9x6h-8gc7 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-393w-9x6h-8gc7 published, and has it been updated?

GHSA-393w-9x6h-8gc7 was published on September 17, 2025. Advisory data evolves as severity scores, affected ranges, and exploit intelligence are revised — always check the latest version of the advisory before acting.

Pingora update for MadeYouReset HTTP/2 vulnerability

Real-World Exposure

1 pkg affected

🦀pingora-core

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

Pingora deployments that include HTTP/2 server support may be affected by the vulnerability described in CVE-2025-8671. Under certain conditions, Pingora applications may allocate buffers before the HTTP/2 reset and resulting stream cancellation is processed by the server. Repeated resets can force excessive memory consumption and lead to denial-of-service.

Impact: On affected versions, malicious clients could trigger unusually high memory consumption, which may result in service instability or process termination.

Credits: Reported responsibly by security researcher Gal Bar Nahum (@galbarnahum)

Mitigation: This issue is addressed by ensuring Pingora uses patched versions of HTTP/2 dependencies that include reset-handling safeguards to release connection resources before excessive memory buildup. Users should upgrade to the latest Pingora release, which incorporates the required fixes.

Users are requested to upgrade to latest version of Pingora >= 0.6.0

Affected Packages

1 total 1 fixed

Ecosystem	Package	Vulnerable range	Fix
🦀crates.io	`pingora-core`	all versions	0.6.0`cargo update -p pingora-core --precise 0.6.0`

Detection & mitigation playbook

Open-source dependency

Detect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for pingora-core, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update pingora-core to 0.6.0 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-393w-9x6h-8gc7 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

Pingora deployments that include HTTP/2 server support may be affected by the vulnerability described in CVE-2025-8671. Under certain conditions, Pingora applications may allocate buffers before the HTTP/2 reset and resulting stream cancellation is processed by the server. Repeated resets can force excessive memory consumption and lead to denial-of-service. **Impact**: On affected versions, malicious clients could trigger unusually high memory consumption, which may result in service instability or process termination. **Credits**: Reported responsibly by security researcher [Gal Bar Nahum](

O3 Security · Impact-Aware SCA

Is GHSA-393w-9x6h-8gc7 in your dependencies?

Find it across crates.io, including transitive dependencies.

Scan my dependencies How O3 SCA works