Authorization bypass via inconsistent HTTP request boundaries
Published Sep 14, 2026 · Updated Sep 14, 2026
HTTP request smuggling in http4s Blaze before 0.23.18 and 1.0.0-M1 through 1.0.0-M41 allows remote attackers to bypass front-end controls. BodyAndHeaderParser and Http1ServerParser accept invalid header names, obsolete folding, unsupported transfer codings, duplicate Content-Length fields, and requests carrying both Transfer-Encoding and Content-Length, producing boundaries that differ from stricter intermediaries. Exploitation requires a lenient or legacy fronting proxy that forwards the malformed request and parses its boundary differently; a default BlazeServerBuilder is exposed.
Summary
What happened
HTTP request smuggling in http4s Blaze before 0.23.18 and 1.0.0-M1 through 1.0.0-M41 allows remote attackers to bypass front-end controls. BodyAndHeaderParser and Http1ServerParser accept invalid header names, obsolete folding, unsupported transfer codings, duplicate Content-Length fields, and requests carrying both Transfer-Encoding and Content-Length, producing boundaries that differ from stricter intermediaries. Exploitation requires a lenient or legacy fronting proxy that forwards the malformed request and parses its boundary differently; a default BlazeServerBuilder is exposed.
The record
- CVE
- CVE-2026-73494
- Published
- Sep 14, 2026
- Updated
- Sep 14, 2026
- Vendor
- http4s
- Product
- http4s-blaze-server
- Classifications
- CWE-444, T1190
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Sep 14, 2026CVE publishedPublication date reported by the CVE source.
- Sep 14, 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.23.18
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