CVSS 3.1
7.4 highCVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:NHigh (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.
CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:Norg.http4s:blaze-http_2.13 (Maven): fixed in 0.23.18, 1.0.0-M42org.http4s:blaze-http_2.12 (Maven): fixed in 0.23.18org.http4s:blaze-http_3 (Maven): fixed in 0.23.18, 1.0.0-M42Explain 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.
From the CNA's record in the CVE List.
| Product | Affected |
|---|---|
| http4s blaze | < 0.23.18 |
| http4s blaze | >= 1.0.0-M1, < 1.0.0-M42 |
| Advisory | Ecosystem | Package | Affected | Fixed in |
|---|---|---|---|---|
| GHSA-46q4-43ph-c6fr | Maven | org.http4s:blaze-http_2.13 | <0.23.18 | 0.23.18 |
| GHSA-46q4-43ph-c6fr | Maven | org.http4s:blaze-http_2.12 | <0.23.18 | 0.23.18 |
| GHSA-46q4-43ph-c6fr | Maven | org.http4s:blaze-http_3 | <0.23.18 | 0.23.18 |
| GHSA-46q4-43ph-c6fr | Maven | org.http4s:blaze-http_3 | >=1.0.0-M1 <1.0.0-M42 | 1.0.0-M42 |
| GHSA-46q4-43ph-c6fr | Maven | org.http4s:blaze-http_2.13 | >=1.0.0-M1 <1.0.0-M42 | 1.0.0-M42 |
The attack patterns MITRE's CAPEC relates to this record's weaknesses, as MITRE names them. Credits.