CVE-2026-119202
@hapi/content provides HTTP Content-* header parsing. From 3.0.6 …
@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.
What to do now
- Check your exposureFind out whether the affected software runs anywhere in your environment, including systems of suppliers.
- UpdateInstall the version in which the vendor fixed the vulnerability. The references lead to the advisory.
- Limit access until thenIf you cannot update at once, take the system off the internet or restrict who can reach it.
References
- github.com/hapijs/content/commit/0993851dc7234976a3fce3a7c31662b213c940fd
- github.com/hapijs/content/releases/tag/v6.0.3
- github.com/hapijs/content/security/advisories/GHSA-8494-f6mr-cjpv
- nvd.nist.gov/vuln/detail/CVE-2026-119202
- github.com/advisories/GHSA-8494-f6mr-cjpv
- nvd.nist.gov/vuln/detail/CVE-2026-119202
- cve.org/CVERecord?id=CVE-2026-119202
Data: CVE list and the NVD. This product uses data from the NVD API but is not endorsed or certified by the NVD.