Vulnerabilities in pkg:maven/org.http4s/blaze-http_2.12
PACKAGECVE-2026-73495 is a HIGH (CVSS 7.4) chunked-body trailer fields promoted into vulnerability (CWE-444: Inconsistent Interpretation of HTTP Requests ('HTTP Request/Response Smuggling')) affecting blaze libraries in the Maven ecosystem. The issue involves chunked-body trailer fields promoted into request.headers in blaze-server (front-end header-sanitization bypass). Remediation is available by upgrading affected packages to version 0.23.18, 1.0.0-M42.
pkg:maven/org.http4s/blaze-http_2.12
Vulnerability advisories affecting package pkg:maven/org.http4s/blaze-http_2.12. Select an advisory below to view technical details or fixes.
| Advisory ID | CVE / NVD | Severity | Summary |
|---|---|---|---|
| GHSA-46q4-43ph-c6fr | CVE-2026-73495 | HIGH | blaze: Chunked-body trailer fields promoted into Request.headers in blaze-server (front-end header-sanitization bypass) |
CVE-2026-73495 at a Glance
Security Impact
CVSS: 7.4
The security impact metrics below are parsed directly from the CVSS v3.1 vector string (CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:N).
How to Fix CVE-2026-73495
To remediate this vulnerability, upgrade all affected blaze dependencies to a patched release. Both direct and transitive dependencies should be checked, as frameworks or security libraries may pull in vulnerable versions transitively.
<dependency>
<groupId>org.http4s</groupId>
<artifactId>blaze-http_2.13</artifactId>
<version>0.23.18</version>
</dependency>
<dependency>
<groupId>org.http4s</groupId>
<artifactId>blaze-http_2.12</artifactId>
<version>0.23.18</version>
</dependency>
<dependency>
<groupId>org.http4s</groupId>
<artifactId>blaze-http_3</artifactId>
<version>0.23.18</version>
</dependency>
<dependency>
<groupId>org.http4s</groupId>
<artifactId>blaze-http_3</artifactId>
<version>1.0.0-M42</version>
</dependency>
<dependency>
<groupId>org.http4s</groupId>
<artifactId>blaze-http_2.13</artifactId>
<version>1.0.0-M42</version>
</dependency>
Run the following command in your project directory to verify that all resolved dependencies use the patched release:
mvn dependency:tree -Dincludes=org.http4s
How to Check if You Are Affected
To determine whether your Java application is affected by CVE-2026-73495, inspect your build dependencies using the Maven Dependency Plugin:
mvn dependency:tree -Dincludes=org.http4s
Analyze the terminal output to locate any version of blaze in your dependency tree. If any resolved version matches the vulnerable ranges listed in the table below (for example, versions earlier than 0.23.18), your application is affected.
Note: The mvn dependency:tree -Dincludes=org.http4s command inspects the resolved dependency graph declared in your project's POM files; it does not perform automated security scanning or inspect runtime dynamic classpaths. Always verify runtime container classpaths and shaded JARs.
Technical Details
Vulnerability Mechanism & Technical Analysis
This vulnerability is classified under CWE-444: Inconsistent Interpretation of HTTP Requests ('HTTP Request/Response Smuggling'), where the product acts as an intermediary http agent (such as a proxy or firewall) in the data flow between two entities such as a client and server, but it does not interpret malformed http requests or responses in ways that are consistent with how the messages will be processed by those entities that are at the ultimate destination. In blaze, software state validation or input boundaries are circumvented during processing. Review the official source advisory statement below for specific affected components, classes, and reproduction details.
Source Advisory Statement
CVE-2026-73495 Affected blaze Versions
5 component(s)| Product / Package | Ecosystem | Affected Versions | Fixed Version |
|---|---|---|---|
|
org.http4s:blaze-http_2.13
|
Maven |
< 0.23.18
|
0.23.18
|
|
org.http4s:blaze-http_2.12
|
Maven |
< 0.23.18
|
0.23.18
|
|
org.http4s:blaze-http_3
|
Maven |
< 0.23.18
|
0.23.18
|
|
org.http4s:blaze-http_3
|
Maven |
≥ 1.0.0-M1
< 1.0.0-M42
|
1.0.0-M42
|
|
org.http4s:blaze-http_2.13
|
Maven |
≥ 1.0.0-M1
< 1.0.0-M42
|
1.0.0-M42
|
References
Frequently Asked Questions
What is CVE-2026-73495?
Which blaze versions are affected?
What version fixes CVE-2026-73495?
Is blaze-http_2.13 affected?
Is blaze-http_2.12 affected?
What is the CVSS score of CVE-2026-73495?
What CWE is associated with CVE-2026-73495?
How can I check Maven dependencies for CVE-2026-73495?
Machine-readable OSV JSON
OSV v1.5 Schema
{
"schema_version" : "1.4.0",
"id" : "GHSA-46q4-43ph-c6fr",
"modified" : "2026-08-12T21:12:00Z",
"published" : "2026-07-24T22:26:48Z",
"aliases" : [ "CVE-2026-73495" ],
"summary" : "blaze: Chunked-body trailer fields promoted into Request.headers in blaze-server (front-end header-sanitization bypass)",
"details" : "### Summary\n 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/values (e.g. `X-Forwarded-For`, internal-auth headers) that a fronting proxy sanitized from the request-header section, bypassing header-based trust decisions in the application.\n\n ### Impact\n Any http4s application using `BlazeServerBuilder` over HTTP/1.1 whose routes or middleware trust proxy-set headers (e.g., `X-Forwarded-For`, `X-Real-IP`, `X-Forwarded-Host`, org-internal auth headers) is affected. Where a fronting proxy strips/normalizes those headers but forwards chunked bodies with trailers intact, an attacker can spoof client IP for allow-lists/rate-limits/audit, forge the `https` scheme, or inject internal-auth headers. A promoted `Connection: close` trailer is also honored, allowing attacker-controlled termination of pooled backend connections.\n\n ### Workarounds\n Deploy behind a proxy that removes trailer fields (or rejects requests that use trailers) before forwarding; until patched, avoid trust decisions based on headers that a proxy is relied upon to sanitize.",
"severity" : [ {
"type" : "CVSS_V3",
"score" : "CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:N"
} ],
"affected" : [ {
"package" : {
"ecosystem" : "Maven",
"name" : "org.http4s:blaze-http_2.13"
},
"ranges" : [ {
"type" : "ECOSYSTEM",
"events" : [ {
"introduced" : "0"
}, {
"fixed" : "0.23.18"
} ]
} ],
"database_specific" : {
"last_known_affected_version_range" : "<= 0.23.17"
}
}, {
"package" : {
"ecosystem" : "Maven",
"name" : "org.http4s:blaze-http_2.12"
},
"ranges" : [ {
"type" : "ECOSYSTEM",
"events" : [ {
"introduced" : "0"
}, {
"fixed" : "0.23.18"
} ]
} ],
"database_specific" : {
"last_known_affected_version_range" : "<= 0.23.17"
}
}, {
"package" : {
"ecosystem" : "Maven",
"name" : "org.http4s:blaze-http_3"
},
"ranges" : [ {
"type" : "ECOSYSTEM",
"events" : [ {
"introduced" : "0"
}, {
"fixed" : "0.23.18"
} ]
} ],
"database_specific" : {
"last_known_affected_version_range" : "<= 0.23.17"
}
}, {
"package" : {
"ecosystem" : "Maven",
"name" : "org.http4s:blaze-http_3"
},
"ranges" : [ {
"type" : "ECOSYSTEM",
"events" : [ {
"introduced" : "1.0.0-M1"
}, {
"fixed" : "1.0.0-M42"
} ]
} ]
}, {
"package" : {
"ecosystem" : "Maven",
"name" : "org.http4s:blaze-http_2.13"
},
"ranges" : [ {
"type" : "ECOSYSTEM",
"events" : [ {
"introduced" : "1.0.0-M1"
}, {
"fixed" : "1.0.0-M42"
} ]
} ],
"database_specific" : {
"last_known_affected_version_range" : "<= 1.0.0-M41"
}
} ],
"references" : [ {
"type" : "WEB",
"url" : "https://github.com/http4s/blaze/security/advisories/GHSA-46q4-43ph-c6fr"
}, {
"type" : "WEB",
"url" : "https://github.com/http4s/blaze/commit/ef3e666c146cfc16cb6603f1fc3c464daab4a24f"
}, {
"type" : "PACKAGE",
"url" : "https://github.com/http4s/blaze"
}, {
"type" : "WEB",
"url" : "https://github.com/http4s/blaze/releases/tag/v0.23.18"
}, {
"type" : "WEB",
"url" : "https://github.com/http4s/blaze/releases/tag/v1.0.0-M42"
} ],
"database_specific" : {
"cwe_ids" : [ "CWE-444" ],
"severity" : "HIGH",
"github_reviewed" : true,
"github_reviewed_at" : "2026-07-24T22:26:48Z",
"nvd_published_at" : null
}
}