@hapi/content provides HTTP Content-* header parsing. From 3.0.6 until 6.0.3, Content.disposition() uses an unanchored parameter-name expression in a global regular-expression scan, causing repeated failed matching over the remaining input when a Content-Disposition parameter contains a long token without an equals sign. The resulting quadratic processing can block the Node.js event loop before route handlers or validation when @hapi/pez parses multipart/form-data headers, including unauthenticated hapi routes with payload.multipart enabled, and also affects applications that pass untrusted headers directly to Content.disposition(). This issue is fixed in @hapi/content version 6.0.3.
References
Configurations
No configuration.
History
29 Oct 2026, 21:17
| Type | Values Removed | Values Added |
|---|---|---|
| New CVE |
Information
Published : 2026-10-29 21:17
Updated : 2026-10-30 19:39
NVD link : CVE-2026-119202
Mitre link : CVE-2026-119202
CVE.ORG link : CVE-2026-119202
JSON object : View
Products Affected
No product.
CWE
CWE-1333
Inefficient Regular Expression Complexity
