Vulnerability in Http4s Blaze
CVE-2026-73494
blaze is a Scala library for building asynchronous pipelines, with a focus on network IO. Prior to 0.23.18 and from 1.0.0-M1 until 1.0.0-M42, five HTTP/1.1 conformance laxities in the hand-written Java parser under http/src/main/java/org/http4s/blaze/http/parser/ can cause blaze to derive a different request boundary than a stricter fronting intermediary. A default BlazeServerBuilder accepts invalid or valueless header field names that violate tchar syntax, obsolete folded field lines (obs-fold), unsupported Transfer-Encoding values, duplicate Content-Length fields, and requests containing both Transfer-Encoding and Content-Length. If a lenient or legacy proxy forwards the malformed bytes but interprets them differently, the disagreement can permit front-end authorization bypass, response-queue poisoning on pooled backend connections, or cache poisoning. Exploitation requires a pair of disagreeing parsers; no non-default blaze configuration is required. The affected checks are enforced in BodyAndHeaderParser and Http1ServerParser. This issue is fixed in versions 0.23.18 and 1.0.0-M42.
Vulnerability class: HTTP Request Smuggling
Published · last modified .
CVSS v3 metric
CVSS v3 base score 7.4 (High). Vector: CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:N.
EPSS exploit prediction
EPSS: 0.006 (50.0th percentile), scored .
Very low probability of exploitation in the next 30 days; routine patching cadence is appropriate. 50th percentile — 50.0% of CVEs in the catalogue have a lower EPSS than this one. How to read EPSS.
EPSS over last 30 days · oldest: 0.006 · newest: 0.006 · change: 0.000
Affected products
- Http4s Blaze — versions < 0.23.18, >= 1.0.0-M1, < 1.0.0-M42
- Org.http4s Blaze-Http 2.13 — versions < 0.23.18, >= 1.0.0-M1, < 1.0.0-M42
- Org.http4s Blaze-Http 3 — versions < 0.23.18, >= 1.0.0-M1, < 1.0.0-M42
- Org.http4s Http4s-Blaze-Server 2.13 — versions < 0.23.18
Weakness classification (CWE)
References
- github.com/http4s/blaze/security/advisories/GHSA-mhvj-jhpq-885v
- github.com/http4s/blaze/commit/3f7c022e306631b006dcb43a1d7f65c0d1966f17
- github.com/http4s/blaze/commit/4eec2007806aa9acfefb00ebb636ddc39a147a96
- github.com/http4s/blaze/commit/927b67753a78c13c4445dac9307f511f5c4878c3
- github.com/http4s/blaze/commit/a54bc9cd31758335c7f24e29763622fd03fcf734
- github.com/http4s/blaze/commit/c47d9675f87603f11b32a11d503626bdf9be5c7a
- github.com/http4s/blaze/commit/e871ebb1d27f50c98fd56988526ce42d0fee74d6
- github.com/http4s/blaze/releases/tag/v0.23.18
- github.com/http4s/blaze/releases/tag/v1.0.0-M42
Frequently asked questions
- What is CVE-2026-73494?
- CVE-2026-73494 is a high-severity vulnerability in Http4s Blaze, classified under Inconsistent Interpretation of HTTP Requests (HTTP Request/Response Smuggling). CVSS score: 7.4/10. Published 2026-09-14.
- How severe is CVE-2026-73494?
- High severity. CVSS v3 base score is 7.4 out of 10.