WaratekVRT Sign in

CVE-2026-73495

Severity7.4 High CVSS 3.1
Fixed in0.23.18, 1.0.0-M42
WeaknessCWE-444
Published12 Aug 2026
Updated24 Oct 2026

Description

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.

Exploitation status

No public exploit

No exploit has been reported in the sources we check.

  • CISA KEV not listed
  • VulnCheck KEV not listed
  • CISA Vulnrichment exploitation: none
  • Indexed PoC none indexed
  • EPSS 0.48% chance in 30 days

Waratek protection

No exploit published

Within Waratek scope. In the sources we check, nobody has published exploit code for this CVE or reported it being exploited.

A public code fix exists: http4s/blaze ef3e666.

  • Protection none
  • Action unverified
  • Review automated Upstream data
  • Record active
Decided by Exploit code for this candidate, published in a reviewed catalogue or a GitHub repository with 5 or more stars, or in use per CISA or VulnCheck; not only a CISA verdict, a forecast, or nothing at all
Finding This CVE is not listed in CISA KEV or VulnCheck KEV, CISA Vulnrichment records no active exploitation, no reviewed exploit catalogue carries an entry for it, and no GitHub PoC repository for it has 5 or more stars. Nobody has published exploit code worth tracing, so it is not a candidate for a rule ahead of the ones where somebody has; an upstream fix path does exist, so the remediation half of the candidacy still holds. This is a statement about what has been published, not about whether the defect is reachable or serious.
Candidate fix https://github.com/http4s/blaze/commit/ef3e666c146cfc16cb6603f1fc3c464daab4a24f : a commit: the change itself

Affected software and releases

Maven packages

Affected and fixed versions, from OSV.dev
PackageIntroducedFixedLast affected
org.http4s:blaze-http_2.13 0 0.23.18 unbounded
org.http4s:blaze-http_2.12 0 0.23.18 unbounded
org.http4s:blaze-http_3 0 0.23.18 unbounded
org.http4s:blaze-http_3 1.0.0-M1 1.0.0-M42 unbounded
org.http4s:blaze-http_2.13 1.0.0-M1 1.0.0-M42 unbounded

Products and versions

3 products, 5 version entries
SourceVendorProductSchemeAffected versions
osv org.http4s blaze-http_2.12 generic < 0.23.18
osv org.http4s blaze-http_2.13 generic < 0.23.18 · ≥ 1.0.0 and < 1.0.0
osv org.http4s blaze-http_3 generic < 0.23.18 · ≥ 1.0.0 and < 1.0.0

References

URLTags
https://github.com/http4s/blaze/commit/ef3e666c146cfc16cb6603f1fc3c464daab4a24f commit
https://github.com/http4s/blaze/security/advisories/GHSA-46q4-43ph-c6fr WEB
https://github.com/http4s/blaze PACKAGE
https://github.com/http4s/blaze/releases/tag/v0.23.18 WEB
https://github.com/http4s/blaze/releases/tag/v1.0.0-M42 WEB

Timeline

Published2026-08-12By the CVE Program.
NVD record modified2026-10-24NVD's own last-modified date for this record.