CVE-2021-41084: Response Splitting from unsanitized headers in http4s
Noroxi assessment
Priority: Monitor (action score 18/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: 1.2% (FIRST EPSS); higher than 69.5% of all records.
- Anyone who can reach it over the internet can trigger it. No account or password is required. A user must open a link or visit a page. No special conditions are required; it is repeatable.
- Fixed version: org.http4s:http4s-client_2.12 (Maven) 0.22.5, 0.23.4, 0.21.29; org.http4s:http4s-client_2.13 (Maven) 0.22.5, 0.23.4, 0.21.29; org.http4s:http4s-client_3 (Maven) 0.22.5, 0.23.4, 0.21.29.
- Severity is disputed: the assigning authority (CNA) scores it 8.7, NVD 4.7.
Low priority for now. Upgrade to org.http4s:http4s-client_2.12 (Maven) 0.22.5, 0.23.4, 0.21.29; org.http4s:http4s-client_2.13 (Maven) 0.22.5, 0.23.4, 0.21.29; org.http4s:http4s-client_3 (Maven) 0.22.5, 0.23.4, 0.21.29 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 an open source scala interface for HTTP. In affected versions http4s is vulnerable to response-splitting or request-splitting attacks when untrusted user input is used to create any of the following fields: Header names (`Header.name`å), Header values (`Header.value`), Status reason phrases (`Status.reason`), URI paths (`Uri.Path`), URI authority registered names (`URI.RegName`) (through 0.21). This issue has been resolved in versions 0.21.30, 0.22.5, 0.23.4, and 1.0.0-M27 perform the following. As a matter of practice http4s services and client applications should sanitize any user input in the aforementioned fields before returning a request or response to the backend. The carriage return, newline, and null characters are the most threatening.
- Published
- Sep 21, 2021
- Updated
- Jun 17, 2026
- EPSS
- 1.2% · 69th percentile
- CWE
- CWE-918
Report tools
Action score
18
Low priority for now.
- CVSS
- 18 / 40 · 4.7 / 10
- CISA KEV
- 0 / 30 · Not listed
- EPSS
- 0 / 30 · 1.2%
CNA vs NVD score
- NVD
- 4.7
- CNA · GitHub_M
- 8.7
- 4.0 point gap
CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:C/C:H/I:H/A: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.
Is your version affected? Check itNoroxi 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 |
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.21.28, >= 0.22.0, < 0.22.5, >= 0.23.0, < 0.23.4, >= 1.0.0-M1, < 1.0.0-M27affected
Affected versions · NVD (4)
NVD version ranges (for catalog products). Add the product to your stack with a version and matching uses these.
- typelevel http4sbefore 0.21.29
- typelevel http4s0.22.0 and later · before 0.22.5
- typelevel http4s0.23.0 and later · before 0.23.4
- typelevel http4s1.0.0
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-client_2.12 | from 0.22.0 · before 0.22.5 | 0.22.5 |
| Maven | org.http4s:http4s-client_2.12 | from 0.23.0 · before 0.23.4 | 0.23.4 |
| Maven | org.http4s:http4s-client_2.12 | before 0.21.29 | 0.21.29 |
| Maven | org.http4s:http4s-client_2.13 | from 0.22.0 · before 0.22.5 | 0.22.5 |
| Maven | org.http4s:http4s-client_2.13 | from 0.23.0 · before 0.23.4 | 0.23.4 |
| Maven | org.http4s:http4s-client_2.13 | before 0.21.29 | 0.21.29 |
| Maven | org.http4s:http4s-client_3 | from 0.22.0 · before 0.22.5 | 0.22.5 |
| Maven | org.http4s:http4s-client_3 | from 0.23.0 · before 0.23.4 | 0.23.4 |
| Maven | org.http4s:http4s-client_3 | before 0.21.29 | 0.21.29 |
| Maven | org.http4s:http4s-server_2.10 | up to and including 0.21.28 | — |
| Maven | org.http4s:http4s-server_2.11 | up to and including 0.21.28 | — |
| Maven | org.http4s:http4s-server_2.12 | from 0.22.0 · before 0.22.5 | 0.22.5 |
| Maven | org.http4s:http4s-server_2.12 | from 0.23.0 · before 0.23.4 | 0.23.4 |
| Maven | org.http4s:http4s-server_2.12 | before 0.21.29 | 0.21.29 |
| Maven | org.http4s:http4s-server_2.13 | from 0.22.0 · before 0.22.5 | 0.22.5 |
| Maven | org.http4s:http4s-server_2.13 | from 0.23.0 · before 0.23.4 | 0.23.4 |
| Maven | org.http4s:http4s-server_2.13 | before 0.21.29 | 0.21.29 |
| Maven | org.http4s:http4s-server_2.13.0-M5 | up to and including 0.21.28 | — |
| Maven | org.http4s:http4s-server_3 | from 0.22.0 · before 0.22.5 | 0.22.5 |
| Maven | org.http4s:http4s-server_3 | from 0.23.0 · before 0.23.4 | 0.23.4 |
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
- Later →CVE-2023-22465Jan 4, 2023 · Http4s has fatal error parsing User-Agent and Server headers21Monitor
- Later →CVE-2025-59822Sep 23, 2025 · Http4s vulnerable to HTTP Request Smuggling due to improper handling of HTTP trailer section25Monitor
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-client_2.12 | 0.21.29 | Package registry (OSV) |
| Maven:org.http4s:http4s-client_2.12 | 0.22.5 | Package registry (OSV) |
| Maven:org.http4s:http4s-client_2.12 | 0.23.4 | Package registry (OSV) |
| Maven:org.http4s:http4s-client_2.13 | 0.21.29 | Package registry (OSV) |
| Maven:org.http4s:http4s-client_2.13 | 0.22.5 | Package registry (OSV) |
| Maven:org.http4s:http4s-client_2.13 | 0.23.4 | Package registry (OSV) |
| Maven:org.http4s:http4s-client_3 | 0.21.29 | Package registry (OSV) |
| Maven:org.http4s:http4s-client_3 | 0.22.5 | Package registry (OSV) |
| Maven:org.http4s:http4s-client_3 | 0.23.4 | Package registry (OSV) |
| Maven:org.http4s:http4s-server_2.12 | 0.21.29 | Package registry (OSV) |
| Maven:org.http4s:http4s-server_2.12 | 0.22.5 | Package registry (OSV) |
| Maven:org.http4s:http4s-server_2.12 | 0.23.4 | Package registry (OSV) |
| Maven:org.http4s:http4s-server_2.13 | 0.21.29 | Package registry (OSV) |
| Maven:org.http4s:http4s-server_2.13 | 0.22.5 | Package registry (OSV) |
| Maven:org.http4s:http4s-server_2.13 | 0.23.4 | Package registry (OSV) |
| Maven:org.http4s:http4s-server_3 | 0.22.5 | Package registry (OSV) |
| Maven:org.http4s:http4s-server_3 | 0.23.4 | 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.
Patch and commit links
Commit, PR and diff links among the references. A starting point for patch-diffing and variant hunting; fixes, not exploits.
Not on record for this CVE: EPSS history · researcher credit · variant or chain candidate · public bounty program.
Technical details
Attack conditions
- Anyone who can reach it over the internet can trigger it.
- No account or password is required.
- A user must open a link or visit a page.
- No special conditions are required; it is repeatable.
If successful
- Confidentiality
- none
- Integrity
- low · data or configuration can be modified
- Availability
- none
Impact can extend beyond the vulnerable component (scope changes).
- Attack vector
- Network
- Attack complexity
- Low
- Privileges required
- None
- User interaction
- Required
- Scope
- Changed
- Confidentiality impact
- None
- Integrity impact
- Low
- Availability impact
- None
Weakness class (CWE)
CWE-918 · Server-Side Request Forgery (SSRF)CVSS vector
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:N/I:L/A:N
nvd-primary
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 (1)
- Fix✗ → ✓
For records you follow, these changes also arrive as notifications. →
References
Show all references (2 more)Show less
Vendor advisories and official records. Exploit/PoC links are deliberately left out.