GHSA-3qmp-g57h-rxf2
Duplicate Advisory: Pingora Request Smuggling and Cache Poisoning
- Severity
- 0.0 / 10
- High · CVSS 4.0
- Exploit chance (EPSS)
- —
- No score published
- Known exploited
- No
- Not in CISA's catalog
- Weakness
- CWE-444 Inconsistent Interpretation of HTTP Requests ('HTTP Request/Response Smuggling')
- Fix
0.5.0- Upgrade pingora-core to this version or later
Description
Duplicate Advisory
This advisory has been withdrawn because it is a duplicate of GHSA-93c7-7xqw-w357. This link is maintained to preserve external references.
Original Description
Pingora versions prior to 0.5.0 which used the caching functionality in pingora-proxy did not properly drain the downstream request body on cache hits.
This allows an attacker to craft malicious HTTP/1.1 requests which could lead to request smuggling or cache poisoning.
This flaw was corrected in commit fda3317ec822678564d641e7cf1c9b77ee3759ff by ensuring that the downstream request body is always drained before a connection can be reused.
See the blog post for more information.
Affected versions
crates.io
| Package | Vulnerable | Fixed in |
|---|---|---|
| pingora-core | < 0.5.0 |
0.5.0 |
How to fix
Move to the fixed version or later with your package manager, update the lockfile, and run your tests. If the package only arrives through another dependency, upgrade that dependency first. If none of its releases pulls a fixed version yet, force the version with your package manager's override.
pingora-core crates.io → 0.5.0
- cargo
cargo update -p pingora-core --precise 0.5.0
Severity breakdown
CVSS 4.0 0.0
CVSS:4.0/AV:N/AC:H/AT:P/PR:N/UI:A/VC:H/VI:H/VA:N/SC:L/SI:L/SA:N
- Attack vector
- Network
- Attack complexity
- High
- Attack requirements
- Present
- Privileges required
- None
- User interaction
- Active
- Confidentiality (vulnerable system)
- High
- Integrity (vulnerable system)
- High
- Availability (vulnerable system)
- None
- Confidentiality (subsequent systems)
- Low
- Integrity (subsequent systems)
- Low
- Availability (subsequent systems)
- None
Weakness
CWE-444: Inconsistent Interpretation of HTTP Requests ('HTTP Request/Response Smuggling')
The product acts as an intermediary HTTP agent (such as a proxy or firewall) in the data flow between two entities such as a client and server, but it does not interpret malformed HTTP requests or responses in ways that are consistent with how the messages will be processed by those entities that are at the ultimate destination.
How to prevent it
- Implementation: Use a web server that employs a strict HTTP parsing procedure, such as Apache [REF-433].
- Implementation: Use only SSL communication.
- Implementation: Terminate the client session after each request.
- System Configuration: Turn all pages to non-cacheable.
References
Advisories
Packages
Other links
Timeline
- Published
- Last updated by the source
- Withdrawn
Related advisories
| Advisory | Severity | Why it's related |
|---|---|---|
| RUSTSEC-2026-0388 Pingora HTTP/2 :authority and Host header mismatch enables cache poisoning and host-based access control bypass | Not rated yet | Also affects pingora-core |
| RUSTSEC-2026-0389 Pingora HTTP/2 server memory exhaustion through unbounded default header-list and concurrent-stream limits | High | Also affects pingora-core |
| GHSA-xq2h-p299-vjwv Pingora vulnerable to HTTP Request Smuggling via Premature Upgrade | Critical | Also affects pingora-core |
| GHSA-hj7x-879w-vrp7 Pingora has HTTP Request Smuggling via HTTP/1.0 and Transfer-Encoding Misparsing | Critical | Also affects pingora-core |
| GHSA-393w-9x6h-8gc7 Pingora update for MadeYouReset HTTP/2 vulnerability | High | Also affects pingora-core |
| RUSTSEC-2025-0070 Pingora MadeYouReset HTTP/2 vulnerability | High | Also affects pingora-core |
| GHSA-93c7-7xqw-w357 Pingora has a Request Smuggling Vulnerability | Medium | Also affects pingora-core |
| EEF-CVE-2026-114216 Chunk extensions accept bare LF and CR, enabling request smuggling in Bandit | Not rated yet | Same weakness, CWE-444 |
MergeHarbor checks every repository's dependencies against this database, ranks what matters by exploitability and reachability, routes it to the owning team and opens the fix pull request.
Check your repos with MergeHarbor