CVE-2026-35213: @hapi/content provided HTTP Content-* headers parsing
CVE-2026-35213 is a high-severity flaw (CVSS 7.5) affecting content. Below: why it ranks where it does, which versions are affected, what to do, and the exact commands.
@hapi/content provided HTTP Content-* headers parsing. All versions of @hapi/content through 6.0.0 are vulnerable to Regular Expression Denial of Service (ReDoS) via crafted HTTP header values. Three regular expressions used to parse Content-Type and Content-Disposition headers contain patterns susceptible to catastrophic backtracking. This vulnerability is fixed in 6.0.1.
Why this priority
- High severity
- Remotely exploitable, no login, no user action
A fixed release or distro patch exists.
Risk facts
| CVSS score | 7.5 (High) |
| Attack vector | Network (remote) |
| Attack complexity | Low |
| Privileges needed | None |
| User interaction | None |
| EPSS exploit chance | 0.3% (top 75%) |
| CISA exploited list | No |
| Weakness | CWE-1333 |
| Published | 2026-04-06 |
| Last modified | 2026-07-24 |
Last updated 2026-07-24 · Sources: CVE Program, NVD, CISA KEV, EPSS and vendor advisories · How we score
Am I affected?
Timeline
- Published CVE record published
- Updated Record last modified
Scores and fixes here are computed automatically from those and other public sources. Confirm with the vendor advisory before changing production systems.
Quick answers
How do I fix CVE-2026-35213?
content: upgrade to 6.0.1. Exact commands for each OS are on this page.
Is CVE-2026-35213 being exploited?
CVE-2026-35213 is not on the CISA Known Exploited Vulnerabilities list at the time of the last update. Check again, as this can change.
What does CVE-2026-35213 affect?
CVE-2026-35213 affects content. Severity is high (CVSS 7.5). @hapi/content provided HTTP Content-* headers parsing. All versions of @hapi/content through 6.0.0 are vulnerable to Regular Expression Denial of Service (ReDoS) via crafted HTTP header values. Three regular expressions used to parse Conten
How urgent is CVE-2026-35213?
Priority 38/100. High severity; Remotely exploitable, no login, no user action