CVE-2025-59822: Http4s vulnerable to HTTP Request Smuggling due to improper handling of HTTP trailer section
Noroxi assessment
Priority: Monitor (action score 25/100)
- The sources we track (CISA KEV, Exploit-DB, Metasploit, Nuclei, GitHub) show no public exploit code or exploitation in the wild.
- Probability of exploitation in the next 30 days: 0.37% (FIRST EPSS).
- Anyone who can reach it over the internet can trigger it. No account or password is required. No user action is required. No special conditions are required; it is repeatable.
- Fixed version: org.http4s:http4s-ember-core_2.12 (Maven) 0.23.31; org.http4s:http4s-ember-core_2.13 (Maven) 1.0.0-M45, 0.23.31; org.http4s:http4s-ember-core_3 (Maven) 1.0.0-M45, 0.23.31.
Low priority for now. Upgrade to org.http4s:http4s-ember-core_2.12 (Maven) 0.23.31; org.http4s:http4s-ember-core_2.13 (Maven) 1.0.0-M45, 0.23.31; org.http4s:http4s-ember-core_3 (Maven) 1.0.0-M45, 0.23.31 or later.
Generated automatically from the record's data: CVSS (NVD and CNA), CISA KEV and SSVC, FIRST EPSS, exploit sources, fixed versions. How we calculate it
Primary sources: NVD · CVE.org · FIRST EPSS
Http4s is a Scala interface for HTTP services. In versions from 1.0.0-M1 to before 1.0.0-M45 and before 0.23.31, http4s is vulnerable to HTTP Request Smuggling due to improper handling of HTTP trailer section. This vulnerability could enable attackers to bypass front-end servers security controls, launch targeted attacks against active users, and poison web caches. A pre-requisite for exploitation involves the web application being deployed behind a reverse-proxy that forwards trailer headers. This issue has been patched in versions 1.0.0-M45 and 0.23.31.
- Published
- Sep 23, 2025
- Updated
- Oct 19, 2026
- EPSS
- 0.3% · 31th percentile
- CWE
- CWE-444
Report tools
Action score
25
Monitor
Low priority for now.
- CVSS
- 25 / 40 · 6.3 / 10
- CISA KEV
- 0 / 30 · Not listed
- EPSS
- 0 / 30 · 0.3%
CISA SSVC decision
- Exploitation
- proof of concept
- Automatable
- no
- Technical impact
- partial
Vulnrichment: CISA's decision-tree inputs.
CNA vs NVD score
- NVD
- —
- CNA · GitHub_M
- 6.3
- NVD has not scored this yet; the score shown is the CNA’s.
CVSS:4.0/AV:N/AC:L/AT:P/PR:N/UI:N/VC:N/VI:L/VA:N/SC:N/SI:N/SA:N
The score given by the assigning authority versus NVD’s independent score. A gap means the severity is contested.
Get told when this record changes
- Not in KEV: no record of exploitation in the wild
- No public exploit code on record
- A fix has been released
If any of these changes, we'll tell you in the daily email digest.
Running WordPress? Scan your site free with WP Lens
Noroxi analysis
What does it mean in your environment?
The assessment above is generated automatically from the record's data; it doesn't know your environment. Our team verifies on your systems whether this vulnerability is actually exploitable and which mitigation is enough.
We use this product, ask for helpAffected systems
Is your version affected?
Pick the product and type the version you run. It's compared with this record's version ranges in your browser; the version isn't sent anywhere.
| Vendor | Product | CPE |
|---|---|---|
| typelevel | http4s | cpe:2.3:a:typelevel:http4s |
Affected versions
NVD version ranges (for catalog products). Add the product to your stack with a version and matching uses these.
- typelevel http4sbefore 0.23.31
- typelevel http4s1.0.0
Versions reported by the vendor
Affected version ranges reported by the assigning authority (GitHub_M). Independent of NVD's CPE analysis and usually ahead of it.
http4s http4s
- < 0.23.31, >= 1.0.0-M1, < 1.0.0-M45affected
Package-level exposure
OSV and GitHub Advisory data: ecosystem, package and range. SBOM matching uses this table.
| Ecosystem | Package | Affected range | Fix |
|---|---|---|---|
| Maven | org.http4s:http4s-ember-core_2.12 | before 0.23.31 | 0.23.31 |
| Maven | org.http4s:http4s-ember-core_2.13 | from 1.0.0-M1 · before 1.0.0-M45 | 1.0.0-M45 |
| Maven | org.http4s:http4s-ember-core_2.13 | before 0.23.31 | 0.23.31 |
| Maven | org.http4s:http4s-ember-core_3 | from 1.0.0-M1 · before 1.0.0-M45 | 1.0.0-M45 |
| Maven | org.http4s:http4s-ember-core_3 | before 0.23.31 | 0.23.31 |
Same product
typelevel: all recordsOther highest-scoring records for the same primary product.
- CVE-2021-39185Default CORS config allows any origin with credentials36Monitor
- CVE-2020-5280Local file inclusion vulnerability in http4s32Monitor
- CVE-2021-21294Unbounded connection acceptance in http4s-blaze-server31Monitor
Published before and after this one in the same product
- ← EarlierCVE-2021-32643May 27, 2021 · StaticFile.fromUrl can leak presence of a directory23Monitor
- ← EarlierCVE-2021-41084Sep 21, 2021 · Response Splitting from unsanitized headers in http4s18Monitor
- ← EarlierCVE-2023-22465Jan 4, 2023 · Http4s has fatal error parsing User-Agent and Server headers21Monitor
Remediation
Which version to upgrade to
Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.
| Product / package | Fixed version | Source |
|---|---|---|
| Maven:org.http4s:http4s-ember-core_2.12 | 0.23.31 | Package registry (OSV) |
| Maven:org.http4s:http4s-ember-core_2.13 | 0.23.31 | Package registry (OSV) |
| Maven:org.http4s:http4s-ember-core_2.13 | 1.0.0-M45 | Package registry (OSV) |
| Maven:org.http4s:http4s-ember-core_3 | 0.23.31 | Package registry (OSV) |
| Maven:org.http4s:http4s-ember-core_3 | 1.0.0-M45 | Package registry (OSV) |
Exploit status
No known public exploit
No public exploit has been observed yet. That doesn't mean you're safe, only that the bar is a little higher.
Research context
For pentesters and researchers: attack profile, score disagreement, timeline, patch commits, credits, variant and chain candidates, bug bounty scope. All derived from existing data; no exploit code.
Timeline
From publication to today: proof of concept, Metasploit module, CISA KEV and fix record. Dates are as reported by the sources.
No dated events beyond publication.
No history yet (it accumulates with the daily EPSS job).
Patch and commit links
Commit, PR and diff links among the references. A starting point for patch-diffing and variant hunting; fixes, not exploits.
Credits
All researchersFinders, reporters and analysts named in the CNA record. Click a name for that researcher’s other records.
No credits in the CNA record.
Variant candidates
Same product, same weakness class, within 18 months. If the patch missed the root cause, the sibling bug is here.
No nightly-computed relations.
Chain candidates
An authentication bypass and a privilege-requiring bug in the same product, published close together: combined they may become an unauthenticated path.
—
Bug bounty scope
No known public program.
Source: bounty-targets-data (public HackerOne, Bugcrowd, Intigriti, YesWeHack listings).
Technical details
Attack conditions
- Anyone who can reach it over the internet can trigger it.
- No account or password is required.
- No user action is required.
- No special conditions are required; it is repeatable.
If successful
- Confidentiality
- Integrity
- Availability
- Attack vector
- Network
- Attack complexity
- Low
- Privileges required
- None
- User interaction
- None
- Scope
- X
Weakness class (CWE)
CWE-444 · Inconsistent Interpretation of HTTP Requests ('HTTP Request/Response Smuggling')CVSS vector
CVSS:4.0/AV:N/AC:L/AT:P/PR:N/UI:N/VC:N/VI:L/VA:N/SC:N/SI:N/SA:N/E:X/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:X
nvd-secondary
Attack context
MITRE CAPEC attack patterns and ATT&CK techniques for this weakness class (CWE). A starting point for detection rules and threat hunting.
Attack patterns (CAPEC)
ATT&CK techniques
—
Change log
- Fix✗ → ✓
For records you follow, these changes also arrive as notifications. →
References
Vendor advisories and official records. Exploit/PoC links are deliberately left out.