CVSS 3.1
6.8 mediumCVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:C/C:N/I:H/A:NMedium (6.8) in http4s http4s. EPSS 0.4% estimated probability of exploitation activity in the next 30 days. Fixed in org.http4s:http4s-client_2.12 0.23.35.
CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:C/C:N/I:H/A:Norg.http4s:http4s-client_2.12 (Maven): fixed in 0.23.35org.http4s:http4s-client_2.13 (Maven): fixed in 0.23.35, 1.0.0-M47org.http4s:http4s-client_3 (Maven): fixed in 1.0.0-M47, 0.23.35Explain CVE-2026-69214 for an engineer deciding whether to act. Use https://cve.bz/api/public/cves/CVE-2026-69214?via=ask-ai-copy and https://cve.bz/cve/CVE-2026-69214?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-69214 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 | < 0.23.35 |
| http4s | >= 1.0.0-M1, < 1.0.0-M47 |
| Advisory | Ecosystem | Package | Affected | Fixed in |
|---|---|---|---|---|
| GHSA-wv64-j4fq-5f9x | Maven | org.http4s:http4s-client_2.12 | <0.23.35 | 0.23.35 |
| GHSA-wv64-j4fq-5f9x | Maven | org.http4s:http4s-client_2.13 | <0.23.35 | 0.23.35 |
| GHSA-wv64-j4fq-5f9x | Maven | org.http4s:http4s-client_2.13 | >=1.0.0-M1 <1.0.0-M47 | 1.0.0-M47 |
| GHSA-wv64-j4fq-5f9x | Maven | org.http4s:http4s-client_3 | >=1.0.0-M1 <1.0.0-M47 | 1.0.0-M47 |
| GHSA-wv64-j4fq-5f9x | Maven | org.http4s:http4s-client_3 | <0.23.35 | 0.23.35 |
The attack patterns MITRE's CAPEC relates to this record's weaknesses, as MITRE names them. Credits.