@hapi/content 6.0.1 before 6.0.3 ReDoS via Content.disposition() Parameter Parsing
- Published
- Last modified
- Where the record stands: published, rejected by its publisher, or superseded by another id.What do these mean? →
- published
- Whether CISA lists it in its Known Exploited Vulnerabilities catalog: proof that attackers are using it.What do these mean? →
- Not listed in CISA KEV
- Fix
- Fixed in 6.0.3, 6.0.1
- Whether working attack code is public (Exploit-DB, Metasploit, Nuclei or GitHub). Public code makes attacks easier.What do these mean? →
- None on Exploit-DB, Metasploit or GitHub
- Exploitation: none
- Automatable: yes
- Technical impact: partial
Summary
The @hapi/content JavaScript library, used for parsing Content-Disposition headers in Node.js applications, is affected by this vulnerability. An unauthenticated remote attacker could send a crafted multipart upload that causes the server to hang on excessive processing, making the application unresponsive to other users.
Summarized by anthropic/claude-haiku-5.5. Verify details against the original sources.
Read the original description
@hapi/content from 6.0.1 before 6.0.3 contains a regular expression denial of service vulnerability in Content.disposition() caused by an incomplete fix for CVE-2026-35213. Unauthenticated remote attackers can send multipart uploads with a long Content-Disposition parameter lacking an equals sign, triggering quadratic backtracking that blocks the event loop.
Timeline
- CVE published
- First seen by cve.now
- CISA SSVC assessment
Exploitation: none · Automatable: yes · Technical impact: partial
- Record last updated
Affected versions
- hapijs @hapi/content
From 6.0.1 · fixed in 6.0.3
- @hapi/contentnpm
fixed in 6.0.1