@hapi/content: quadratic-time parsing of Content-Disposition parameters allows denial of service
CVE-2026-119202GHSA-8494-f6mr-cjpv
What to do
Partial vendor fix. Follow the primary source's mitigation guidance and check back for a fix.
This page has no inventory attached, so it cannot say whether you are affected. A vendor fix is not proof that your deployment is fixed.
Affected packages
npm @hapi/content
- Affected
- < 6.0.3
- Fixed in
- 6.0.3
npm content
- Affected
- >= 3.0.6, <= 4.0.6
- Fixed in
- no fixed version recorded
Sources
- GitHub Advisory Database and maintainer security advisories on GitHub
GitHub-reviewed advisory GHSA-8494-f6mr-cjpv lists affected ranges: npm @hapi/content >=0 =3.0.6 <=4.0.6
VerifiedObserved Structured GitHub Advisory Database record (type=reviewed) from the GitHub REST API.
- Open Source Vulnerabilities (OSV.dev), including the GitHub Advisory Database
OSV record GHSA-8494-f6mr-cjpv lists affected ranges: npm @hapi/content >=0 =3.0.6 <=4.0.6
VerifiedObserved Structured OSV record; GitHub-reviewed advisory.
Severity and exploitation
- Exploitation
- No confirmed exploitation recorded. Patch Next marks exploitation only from CISA KEV.
- CVSS
- 7.5 · CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H
- EPSS
- CVE-2026-119202: 0.41% estimated exploitation activity in the next 30 days; percentile 35.45 (FIRST EPSS, 2026-11-03). This is a model estimate, not proof of exploitation or customer exposure.
Source description
As published by the source; long descriptions are shortened.
Summary `Content.disposition()` takes quadratic time when a `Content-Disposition` parameter contains a long token without `=`. One unauthenticated multipart request can block the Node.js event loop for several minutes.
Details `Content.disposition()` reads the parameters with a global regular expression in `String.prototype.replace()`: ```js /([^\=\*\s]+)(\*)?\s*\=\s*(?:([^;'"\s]+\'[\w-]*\'[^;\s]+)|(?:\"([^"]*)\")|([^;\s]*))/g ``` The parameter name part `([^\=\*\s]+)` has no anchor. When a run of name characters has no `=` after it, the match attempt reads the full run and fails. The global scan then starts again at the next character and reads the remaining run again. The total time is proportional to the square of the run length. `@hapi/pez` calls `Content.disposition()` on the header of every part in a `multipart/form-data` body. In hapi, this occurs on each route with `payload.multipart` enabled, before the route handler and before any validation. The only size limit is…
Dates and revisions
- Published by the source
- Last modified by the source
- Source last checked
- Revision 2 · amended ·
Amended from osv record GHSA-8494-f6mr-cjpv
- Revision 1 · created ·
Published from ghsa record GHSA-8494-f6mr-cjpv
Agent brief
Preview the exact text before you copy it. Commands are read-only suggestions; review them before running anything.
# Patch Next advisory brief: CVE-2026-119202 Advisory: @hapi/content: quadratic-time parsing of Content-Disposition parameters allows denial of service IDs: CVE-2026-119202, GHSA-8494-f6mr-cjpv Record: https://patchnext.com/advisories/cve-2026-119202 (revision 2, source checked 31 Oct 2026, 06:00 UTC) Inventory: none attached. This brief comes from a public page and does not say whether any deployment is affected. Severity: High (CVSS 7.5) Exploitation: no confirmed exploitation recorded. Patch Next confirms exploitation only from CISA KEV. Vendor response: Partial vendor fix; fixed versions by package: @hapi/content 6.0.3. A vendor fix does not mean a deployment is fixed. ## Affected components - npm @hapi/content: affected < 6.0.3; fixed in 6.0.3 - npm content: affected >= 3.0.6, <= 4.0.6 ## Suggested inspection (read-only) - `npm ls @hapi/content --all`: lists every installed copy and version, including transitive ones. Run in the project root after `npm ci`. - `npm ls content --all`: lists every installed copy and version, including transitive ones. Run in the project root after `npm ci`. ## Supported action No complete vendor fix is recorded. Follow the primary source's mitigation guidance and check this record again before closing anything. ## Required regression checks - Run the test suite and a production build. - Exercise the features that depend on @hapi/content, content. - Repeat the inspection and confirm that only fixed versions remain installed. ## Rollback considerations - Keep the previous lockfile and deployment artifact. Rolling back reinstates the vulnerable version, so apply any documented mitigation while you fix forward. ## Unresolved questions - Which deployments run an affected version? - Exploitation status can change. Check again before lowering the priority. - Mark the work resolved only after the fixed version is verified in production. ## Sources - Verified: https://github.com/advisories/GHSA-8494-f6mr-cjpv (GitHub-reviewed advisory GHSA-8494-f6mr-cjpv lists affected ranges: npm @hapi/content >=0 =3.0.6 <=4.0.6) - Verified: https://osv.dev/vulnerability/GHSA-8494-f6mr-cjpv (OSV record GHSA-8494-f6mr-cjpv lists affected ranges: npm @hapi/content >=0 =3.0.6 <=4.0.6) Commands are suggestions: review each one before running it.
Loading voting…