CVE-2026-119202

@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.

CVSS 3.1

7.5CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H

CWE

CWE-1333

Published

2026-10-29

Modified

2026-10-29

Record from

the NVD, synced 2026-10-29

References

• https://github.com/hapijs/content/commit/0993851dc7234976a3fce3a7c31662b213c940fd
• https://github.com/hapijs/content/releases/tag/v6.0.3
• https://github.com/hapijs/content/security/advisories/GHSA-8494-f6mr-cjpv

Check your stackJSON