CVE-2026-35213
Content Project Content ≤ 6.0.1
Raw vector
CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:N/VI:N/VA:H/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:XCVSS and EPSS are reproduced from their sources (NVD, FIRST EPSS). EPSS scores by FIRST (EPSS SIG), generated by Empirical Security. Risk Priority is our own derived reading, not an NVD score.
Summary
CVE-2026-35213 is a high-severity Inefficient Regular Expression Complexity (CWE-1333) vulnerability in Content Project Content. Its CVSS base score is 8.7 (High).
Operationally, exploitation aligns with the MITRE ATT&CK technique Endpoint Denial of Service (T1499); ranked at the 47th percentile by exploit likelihood (below the median); it is not currently listed in the CISA KEV catalog.
The strongest mitigations our analysis identified map to SA-11 (Developer Testing and Evaluation) and SA-15 (Development Process, Standards, and Tools) — see the control section below for these in your framework.
Deeper analysis AI-assisted summary
Synthesised by an AI model from the NVD description and linked references — a reading aid, not an authoritative source.
@hapi/content is a Node.js library that parses HTTP Content-* headers including Content-Type and Content-Disposition. All versions through 6.0.0 contain three regular expressions that are vulnerable to catastrophic backtracking, enabling a Regular Expression Denial of Service (ReDoS) condition when attacker-supplied header values are processed. The flaw is tracked as CWE-1333 and carries a CVSS 4.0 score of 8.7.
An unauthenticated remote attacker can trigger the vulnerability simply by sending a single HTTP request containing a crafted Content-Type or Content-Disposition header. Successful exploitation causes the event loop to block, resulting in denial of service for the affected Node.js process while leaving confidentiality and integrity untouched.
The project’s security advisory GHSA-jg4p-7fhp-p32p and the associated pull request #38 state that the issue is resolved in version 6.0.1; users are advised to upgrade immediately and to validate that no pinned older releases remain in production dependency trees.
EPSS for the CVE rose from a low baseline of 0.0042 to a peak of 0.0121, indicating that exploitation interest increased after public disclosure. No reports of in-the-wild exploitation have been observed to date.
EU & UK References
- 🇪🇺 ENISA EUVD: EUVD-2026-19477
Vulnerability Data
@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…
more
catastrophic backtracking. This vulnerability is fixed in 6.0.1.
- CWE(s)
Related Threats
MITRE ATT&CK Enterprise Techniques
CVEs Like This One
Affected Assets
Mitigating Controls
Mitigating Controls (NIST 800-53 r5) AI
Developer testing and evaluation can discover inefficient regex patterns via performance or static analysis.
Development standards and tools can require safe regex construction and forbid known exponential patterns.
Denial-of-service protections limit resource exhaustion caused by expensive regex evaluation.
Input validation can constrain data that would otherwise trigger worst-case regex complexity.
Mitigating Controls (NIST CSF 2.0) AI
Derived directly from the weakness types (CWEs) cited in the NVD entry via our AI-authored CWE→CSF cross-walk (authority under review) — links open the control.
Mitigating Controls (ISO/IEC 27001:2022 Annex A) AI
Derived directly from the weakness types (CWEs) cited in the NVD entry via our AI-authored CWE→ISO cross-walk (authority under review) — links open the control.
Security testing can detect and reject regex patterns with exponential worst-case complexity.
Secure coding standards explicitly prohibit or limit the use of inefficient regular expressions.