cve.bz

CVE-2026-73494 HTTP Request Smuggling

7.4 highEPSS 0.6%Fix available

High (7.4). EPSS 0.6% estimated probability of exploitation activity in the next 30 days. Fixed in org.http4s:http4s-blaze-server_2.13 0.23.18.

On this page
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.

Severity

CVSS 3.1

7.4 high
CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:N
EPSS
0.6% (unchanged from 0.6% a week ago; 0.6% 30 days ago) estimated probability of exploitation activity in the next 30 days; 51st percentile. Scored 2026-11-17. A forecast for this CVE across the internet, not for your own systems.
CISA's assessment (SSVC)
Exploitation: none · Automatable: no · Technical impact: total, assessed 2026-09-14. From CISA's Vulnrichment in the CVE List: whether it is exploited, whether exploiting it can be automated, and how much control it gives.
CWE
CWE-444 Inconsistent Interpretation of HTTP Requests (HTTP Request Smuggling)
OWASP Top 10
A06:2025 Insecure Design
Published
Modified
NVD analysis
Deferred: the NVD does not plan to analyze it
Record from
the NVD, synced

Fix and patched versions

  • org.http4s:http4s-blaze-server_2.13 (Maven): fixed in 0.23.18
  • org.http4s:blaze-http_2.13 (Maven): fixed in 0.23.18, 1.0.0-M42
  • org.http4s:blaze-http_3 (Maven): fixed in 0.23.18, 1.0.0-M42

Ask an AI about this CVE

Show the promptExplain CVE-2026-73494 for an engineer deciding whether to act. Use https://cve.bz/api/public/cves/CVE-2026-73494?via=ask-ai-copy and https://cve.bz/cve/CVE-2026-73494?via=ask-ai-copy as the source of truth: what is affected and which versions fix it, whether it is in CISA KEV, public exploits, and its EPSS (an internet-wide 30-day estimate of exploitation activity, not a forecast for my systems). If they give no fixed versions, use the CVE record https://cveawg.mitre.org/api/cve/CVE-2026-73494 or the vendor advisory, not third-party mirrors. Tell me how to check whether I am affected and how to verify a fix. Cite the sources and say where they are uncertain.

Opens a third-party assistant; its answer is its own, not cve.bz's. The prompt holds only this CVE's id and public links.

Affected

Versions

From the CNA's record in the CVE List.

ProductAffected
http4s blaze< 0.23.18
http4s blaze>= 1.0.0-M1, < 1.0.0-M42
org.http4s blaze-http_2.13< 0.23.18
org.http4s blaze-http_2.13>= 1.0.0-M1, < 1.0.0-M42
org.http4s blaze-http_3< 0.23.18
org.http4s blaze-http_3>= 1.0.0-M1, < 1.0.0-M42
org.http4s http4s-blaze-server_2.13< 0.23.18

Packages (OSV)

AdvisoryEcosystemPackageAffectedFixed in
GHSA-mhvj-jhpq-885vMavenorg.http4s:http4s-blaze-server_2.13<0.23.180.23.18
GHSA-mhvj-jhpq-885vMavenorg.http4s:blaze-http_2.13<0.23.180.23.18
GHSA-mhvj-jhpq-885vMavenorg.http4s:blaze-http_3<0.23.180.23.18
GHSA-mhvj-jhpq-885vMavenorg.http4s:blaze-http_3>=1.0.0-M1 <1.0.0-M421.0.0-M42
GHSA-mhvj-jhpq-885vMavenorg.http4s:blaze-http_2.13>=1.0.0-M1 <1.0.0-M421.0.0-M42

Attack patterns (CAPEC)

  • CAPEC-33 HTTP Request Smuggling Likelihood: Medium · Severity: High
  • CAPEC-273 HTTP Response Smuggling Likelihood: Medium · Severity: High

The attack patterns MITRE's CAPEC relates to this record's weaknesses, as MITRE names them. Credits.

References

Check your stackJSON