cve.bz

CVE-2026-73495 http4s blaze: HTTP Request Smuggling

7.4 highEPSS 0.5%Fix available

High (7.4) in http4s blaze. EPSS 0.5% estimated probability of exploitation activity in the next 30 days. Fixed in org.http4s:blaze-http_2.13 0.23.18, 1.0.0-M42.

On this page
blaze is a Scala library for building asynchronous pipelines, with a focus on network IO. Prior to 0.23.18 and 1.0.0-M42, blaze-server can merge HTTP/1.1 chunked-body trailer fields into Request.headers. Because trailer fields are attacker-controlled, an unauthenticated remote client can inject arbitrary header names and values, including X-Forwarded-For and internal authorization headers, that a fronting proxy sanitized from the request-header section, bypassing header-based trust decisions in the application. Any http4s application using BlazeServerBuilder over HTTP/1.1 whose routes or middleware trust proxy-set headers, including X-Forwarded-For, X-Real-IP, and X-Forwarded-Host, is affected. If a fronting proxy strips or normalizes those headers but forwards chunked bodies with trailers intact, an attacker can spoof client IP for allow-lists, rate limits, or auditing, forge the https scheme, or inject internal authorization headers. A promoted Connection: close trailer is also honored, allowing attacker-controlled termination of pooled backend connections. 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.5% (unchanged from 0.5% a week ago; 0.5% 30 days ago) estimated probability of exploitation activity in the next 30 days; 42nd 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-08-13. 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:blaze-http_2.13 (Maven): fixed in 0.23.18, 1.0.0-M42
  • org.http4s:blaze-http_2.12 (Maven): fixed in 0.23.18
  • 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-73495 for an engineer deciding whether to act. Use https://cve.bz/api/public/cves/CVE-2026-73495?via=ask-ai-copy and https://cve.bz/cve/CVE-2026-73495?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-73495 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

Packages (OSV)

AdvisoryEcosystemPackageAffectedFixed in
GHSA-46q4-43ph-c6frMavenorg.http4s:blaze-http_2.13<0.23.180.23.18
GHSA-46q4-43ph-c6frMavenorg.http4s:blaze-http_2.12<0.23.180.23.18
GHSA-46q4-43ph-c6frMavenorg.http4s:blaze-http_3<0.23.180.23.18
GHSA-46q4-43ph-c6frMavenorg.http4s:blaze-http_3>=1.0.0-M1 <1.0.0-M421.0.0-M42
GHSA-46q4-43ph-c6frMavenorg.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