GHSA-393w-9x6h-8gc7 — pingora-core
GHSA-393w-9x6h-8gc7 is a security vulnerability in pingora-core. A fix is available for pingora-core — see the affected versions and patch details below.
Pingora update for MadeYouReset HTTP/2 vulnerability
Real-World Exposure
pingora-coreReal-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
| Ecosystem | Package | Vulnerable range | Fix |
|---|---|---|---|
| 🦀crates.io | pingora-core | all versions | 0.6.0cargo update -p pingora-core --precise 0.6.0 |
Detection & mitigation playbook
Open-source dependencyDetect
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.
How O3 protects you
O3 Security's impact-aware SCA analyses which vulnerable code paths your application actually calls, so a match like GHSA-393w-9x6h-8gc7 can be triaged on real exposure rather than presence alone.
Tailored to GHSA-393w-9x6h-8gc7. 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-393w-9x6h-8gc7 in your dependencies?
O3 Security finds GHSA-393w-9x6h-8gc7 across crates.io dependencies, including transitive ones, and its impact-aware SCA ranks findings by whether your code actually calls the vulnerable path.