@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.
{
"cna_assigner": "GitHub_M",
"cwe_ids": [
"CWE-1333"
],
"osv_generated_from": "https://github.com/CVEProject/cvelistV5/tree/main/cves/2026/119xxx/CVE-2026-119202.json"
}{
"extracted_events": [
{
"range": [
{
"introduced": "0"
},
{
"fixed": "6.0.3"
}
],
"source": "AFFECTED_FIELD",
"strategy": "StringRangeExpression"
},
{
"range": [
{
"fixed": "0993851dc7234976a3fce3a7c31662b213c940fd"
}
],
"source": "REFERENCES_COMMIT"
},
{
"original_tag": "v6.0.3",
"range": [
{
"fixed": "06f8c9f8bb38251781f89c348ae7760e49ca1f25"
}
],
"source": "REFERENCES_TAG"
}
]
}