CVSS 4.0
6.3 mediumCVSS:4.0/AV:N/AC:L/AT:P/PR:N/UI:N/VC:N/VI:L/VA:N/SC:N/SI:N/SA:NMedium (6.3) in typelevel http4s. EPSS 0.4% estimated probability of exploitation activity in the next 30 days. Fixed in org.http4s:http4s-ember-core_2.12 0.23.31.
CVSS:4.0/AV:N/AC:L/AT:P/PR:N/UI:N/VC:N/VI:L/VA:N/SC:N/SI:N/SA:NCVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:H/A:Norg.http4s:http4s-ember-core_2.12 (Maven): fixed in 0.23.31org.http4s:http4s-ember-core_2.13 (Maven): fixed in 0.23.31, 1.0.0-M45org.http4s:http4s-ember-core_3 (Maven): fixed in 0.23.31, 1.0.0-M45Explain CVE-2025-59822 for an engineer deciding whether to act. Use https://cve.bz/api/public/cves/CVE-2025-59822?via=ask-ai-copy and https://cve.bz/cve/CVE-2025-59822?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-2025-59822 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 NVD's CPE matches.
| Product | Affected |
|---|---|
| typelevel:http4s | before 0.23.31 |
| typelevel:http4s | 1.0.0:milestone1 |
| typelevel:http4s | 1.0.0:milestone10 |
| typelevel:http4s | 1.0.0:milestone11 |
| typelevel:http4s | 1.0.0:milestone12 |
| typelevel:http4s | 1.0.0:milestone13 |
| typelevel:http4s | 1.0.0:milestone14 |
| typelevel:http4s | 1.0.0:milestone15 |
| typelevel:http4s | 1.0.0:milestone16 |
| typelevel:http4s | 1.0.0:milestone17 |
| typelevel:http4s | 1.0.0:milestone18 |
| typelevel:http4s | 1.0.0:milestone19 |
| typelevel:http4s | 1.0.0:milestone2 |
| typelevel:http4s | 1.0.0:milestone20 |
| typelevel:http4s | 1.0.0:milestone21 |
| typelevel:http4s | 1.0.0:milestone22 |
| typelevel:http4s | 1.0.0:milestone23 |
| typelevel:http4s | 1.0.0:milestone24 |
| typelevel:http4s | 1.0.0:milestone25 |
| typelevel:http4s | 1.0.0:milestone26 |
| typelevel:http4s | 1.0.0:milestone27 |
| typelevel:http4s | 1.0.0:milestone28 |
| typelevel:http4s | 1.0.0:milestone29 |
| typelevel:http4s | 1.0.0:milestone3 |
| typelevel:http4s | 1.0.0:milestone30 |
| typelevel:http4s | 1.0.0:milestone31 |
| typelevel:http4s | 1.0.0:milestone32 |
| typelevel:http4s | 1.0.0:milestone33 |
| typelevel:http4s | 1.0.0:milestone34 |
| typelevel:http4s | 1.0.0:milestone35 |
| typelevel:http4s | 1.0.0:milestone36 |
| typelevel:http4s | 1.0.0:milestone37 |
| typelevel:http4s | 1.0.0:milestone38 |
| typelevel:http4s | 1.0.0:milestone39 |
| typelevel:http4s | 1.0.0:milestone4 |
| typelevel:http4s | 1.0.0:milestone40 |
| typelevel:http4s | 1.0.0:milestone41 |
| typelevel:http4s | 1.0.0:milestone42 |
| typelevel:http4s | 1.0.0:milestone43 |
| typelevel:http4s | 1.0.0:milestone44 |
| typelevel:http4s | 1.0.0:milestone5 |
| typelevel:http4s | 1.0.0:milestone6 |
| typelevel:http4s | 1.0.0:milestone7 |
| typelevel:http4s | 1.0.0:milestone8 |
| typelevel:http4s | 1.0.0:milestone9 |
| Advisory | Ecosystem | Package | Affected | Fixed in |
|---|---|---|---|---|
| GHSA-wcwh-7gfw-5wrr | Maven | org.http4s:http4s-ember-core_2.12 | <0.23.31 | 0.23.31 |
| GHSA-wcwh-7gfw-5wrr | Maven | org.http4s:http4s-ember-core_2.13 | <0.23.31 | 0.23.31 |
| GHSA-wcwh-7gfw-5wrr | Maven | org.http4s:http4s-ember-core_3 | <0.23.31 | 0.23.31 |
| GHSA-wcwh-7gfw-5wrr | Maven | org.http4s:http4s-ember-core_2.13 | >=1.0.0-M1 <1.0.0-M45 | 1.0.0-M45 |
| GHSA-wcwh-7gfw-5wrr | Maven | org.http4s:http4s-ember-core_3 | >=1.0.0-M1 <1.0.0-M45 | 1.0.0-M45 |
The attack patterns MITRE's CAPEC relates to this record's weaknesses, as MITRE names them. Credits.