Skip to main content
VulnerabilityPublished

CVE-2026-119202: hapijs content · ReDoS

Affects hapijs contentSource CVE Database V5

0
Compare

Not known to be exploited · CVSS 7.5 High : upgrade to 6.0.3 soon.

Data as of 29 Oct 2026, 21:14 UTC

CVSS 3.1 base score
7.5High
How severe the flaw is on the 0–10 CVSS scale.

Thin evidence

One scorer or none
CVSS scores by source
CNA (GitHub_M)CVSS 3.17.5
Patch
Available – fixed in 6.0.3
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 29 Oct 2026

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponized: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq Mirage: no evidence on record.

    No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 29 Oct 2026.

What to do

Upgrade hapijs content to 6.0.3.

Affected software

ProductAffectedFixed in
hapijscontentAffected
  • <6.0.3
Fixed in
  • 6.0.3

AI-suggested

Upgrade @hapi/content to version 6.0.3 or later where this issue is fixed. Until then, avoid passing untrusted Content-Disposition headers to Content.disposition() and disable payload.multipart on unauthenticated routes if possible.

Description

@hapi/content versions from 3.0.6 up to but not including 6.0.3 contain a vulnerability in the Content.disposition() function where an inefficient regular expression causes excessive processing time. This can lead to blocking of the Node.js event loop when parsing multipart/form-data headers, affecting unauthenticated routes with payload.multipart enabled and any application passing untrusted headers to this function. The issue is resolved in version 6.0.3.

References

Community reviews

Loading reviews…