CVE-2026-73494Not yet in NVD's feed. The description, CVSS and CWE below come from the CVE Numbering Authority's own record, not from NVD analyst review. NVD's own page for this identifier may not exist yet.
Published yesterday. NVD backfills CPE data for days or weeks after publication, and OSV and the exploit indexes lag too. Scope and status here may change.
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.
CWE-444
No public exploit
Nothing published shows this CVE being exploited, which is not the same as ruling it out.
CVSS E:U
In RASP's scope with an upstream fix path, but nobody has published a working exploit. That is a statement about what has been published, not a finding that the defect is unreachable or unimportant.
| Decided by | no-exploit-published : A published working exploit for this candidate, not only a proof of concept, a forecast, or nothing at all |
|---|---|
| Finding | This CVE is not listed in CISA KEV, CISA Vulnrichment records no active exploitation, and no reviewed exploit catalogue carries an entry for it. Nobody has published something a stranger can run, 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/3f7c022e306631b006dcb43a1d7f65c0d1966f17 : a commit: the change itself |
CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:N
1 metric
VRT selects the newest version's highest entry and
publishes it as cvssScore, newest rather than largest because scores are not comparable
across versions, and highest rather than first because the first entry is frequently a CNA placeholder
scoring 0.0 over NVD's own analysis.
| Version | Score | Band | Vector | Assigner | Type | |
|---|---|---|---|---|---|---|
| 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 |
GitHub_M | Primary | published |
| Package Coordinate | Introduced | Fixed | Last affected |
|---|---|---|---|
org.http4s:http4s-blaze-server_2.13 |
0 | 0.23.18 |
unbounded |
org.http4s:blaze-http_2.13 |
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 |
| Source | Vendor | Product | Scheme | Affected Versions |
|---|---|---|---|---|
| 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 |
| osv | org.http4s | http4s-blaze-server_2.13 | generic | < 0.23.18 |
| Published | 2026-09-14 | By the CVE Program. |
|---|---|---|
| NVD record modified | 2026-09-14 | NVD's own last-modified date for this record. |