Request smuggling via unvalidated request metadata
Published May 11, 2026 · Updated May 11, 2026
HTTP request smuggling in HTTP::Tiny before 0.093 allows remote attackers to inject headers and upstream requests via crafted input. The write_request_header and write_header_lines methods serialize unvalidated method, URI, Host-derived URL data, and control header values into HTTP/1.1 requests. Reachability requires an application to pass attacker-controlled input, such as a webhook URL, and permits altered requests at the upstream server.
Summary
What happened
HTTP request smuggling in HTTP::Tiny before 0.093 allows remote attackers to inject headers and upstream requests via crafted input. The write_request_header and write_header_lines methods serialize unvalidated method, URI, Host-derived URL data, and control header values into HTTP/1.1 requests. Reachability requires an application to pass attacker-controlled input, such as a webhook URL, and permits altered requests at the upstream server.
The record
- CVE
- CVE-2026-7010
- Published
- May 11, 2026
- Updated
- May 11, 2026
- Vendor
- Graham Knop
- Product
- HTTP::Tiny
- Classifications
- CWE-113, T1190
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- May 11, 2026CVE publishedPublication date reported by the CVE source.
- May 11, 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 <0.093
What conditions does exploitation require?
What is affected?
Published CVSS scores
CVSS describes severity. EPSS estimates exploitation probability.
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
No public exploit references are available in this record.
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