@hapi/content: Regular Expression Denial of Service (ReDoS) in HTTP header parsing
Published Apr 6, 2026 · Updated Oct 23, 2026 · Also known as GHSA-jg4p-7fhp-p32p
Original summary
Normalized public record · Updated Oct 23, 2026
@hapi/content: Regular Expression Denial of Service (ReDoS) in HTTP header parsing
Publisher and source text is retained separately from QFinch interpretation.
QFinch assessment
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 has been fixed in v6.0.1.
Potential impact
Denial of Service. An unauthenticated remote attacker can cause a Node.js process to become unresponsive by sending a single HTTP request with a maliciously crafted header value.
Evidence: public source recordsAffected products
| Affected package, product or range | Fix status |
|---|---|
| Consult the referenced vendor advisory for affected versions. | Consult source advisory |
Matching a version is only one part of assessing exposure. QFinch has not assessed your environment on this public page.
Remediation
Apply the vendor-supported fixed release or mitigation, then verify the affected component is no longer reachable.
- Confirm the affected product and reachable code path exist in your environment.
- Apply the vendor-supported patch or mitigation from the primary advisory.
- Rescan the exact deployed revision and retain verification evidence.
Evidence coverage
- SSVC priority
- MEDIUM
- Confidence
- 10%
- Aliases
- GHSA-jg4p-7fhp-p32p
Scores appear only when corresponding evidence exists. Missing data is never interpreted as zero risk.
Sources and record history
Record history
Published Apr 6, 2026 · Last refreshed Oct 23, 2026