Cross-client response poisoning via Upgrade body forwarding
Published Jun 28, 2026 · Updated Jun 28, 2026
HTTP request smuggling in nghttp2 nghttpx through 1.69.0 allows remote attackers to poison cross-client response queues. The HTTP/1.1 frontend forwarding path accepts Upgrade requests with Content-Length, re-adds hop-by-hop Upgrade and Connection headers, and streams the body to a reusable HTTP/1.1 backend connection. Exploitation requires an Upgrade-aware backend that leaves the body bytes to be parsed as another request, enabling attacker-selected responses to be delivered to subsequent clients.
Summary
What happened
HTTP request smuggling in nghttp2 nghttpx through 1.69.0 allows remote attackers to poison cross-client response queues. The HTTP/1.1 frontend forwarding path accepts Upgrade requests with Content-Length, re-adds hop-by-hop Upgrade and Connection headers, and streams the body to a reusable HTTP/1.1 backend connection. Exploitation requires an Upgrade-aware backend that leaves the body bytes to be parsed as another request, enabling attacker-selected responses to be delivered to subsequent clients.
The record
- CVE
- CVE-2026-58055
- Published
- Jun 28, 2026
- Updated
- Jun 28, 2026
- Vendor
- nghttp2
- Product
- nghttp2
- Classifications
- CWE-444, T1190
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Jun 28, 2026CVE publishedPublication date reported by the CVE source.
- Jun 28, 2026Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=0 <=1.69.0
What conditions does exploitation require?
What is affected?
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Weakness, pattern, technique
Public exploit references
- nghttp2 nghttpx Upgrade queue-poison proof of conceptproof of concept · demonstrated
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo