Summary
Pingora update for MadeYouReset HTTP/2 vulnerability
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
Impact
Affected versions
Security releases
Kodem intelligence
Severity tells you how bad this could be in the worst case. It does not tell you whether you are exposed. Exploitability and impact are functions of runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A vulnerable package can sit in your dependency tree and never run.
Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter. Kodem's runtime-powered SCA identifies whether this CVE is reachable in your applications.
Already deployed Kodem?
See it in your environmentNew to Kodem? Get a demo →Remediation advice
Kodem Kai can prioritize this vulnerability in your dependency tree and generate a fix recommendation.
Frequently Asked Questions
- What is GHSA-393W-9X6H-8GC7? GHSA-393W-9X6H-8GC7 is a high-severity security vulnerability in pingora-core (rust), affecting versions < 0.6.0. It is fixed in 0.6.0.
- Which versions of pingora-core are affected by GHSA-393W-9X6H-8GC7? pingora-core (rust) versions < 0.6.0 is affected.
- Is there a fix for GHSA-393W-9X6H-8GC7? Yes. GHSA-393W-9X6H-8GC7 is fixed in 0.6.0. Upgrade to this version or later.
- Is GHSA-393W-9X6H-8GC7 exploitable, and should I be worried? Whether GHSA-393W-9X6H-8GC7 is exploitable in your environment depends on whether the vulnerable code is present and reachable. A CVSS score is a worst-case rating; it does not account for your specific deployment, configuration, or usage patterns. Kodem, an Intelligent Application Security platform, uses runtime intelligence to show which vulnerabilities actually execute in production, so you can focus on the ones that represent real risk. Get a demo
- What actually determines whether GHSA-393W-9X6H-8GC7 is exploitable, and how bad it is? Exploitability and impact are not fixed properties of a CVE. They depend on runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A high CVSS score on a dependency that never runs is not the same as real risk. Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter.
- How do I fix GHSA-393W-9X6H-8GC7? Upgrade
pingora-coreto 0.6.0 or later.