# CVE-2026-119202: @hapi/content: quadratic-time parsing of Content-Disposition parameters allows denial of service


- **Severity:** High 7.5 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H`)
- **Exploited in the wild:** Not known
- **Fix available:** No
- **Published:** 29 Oct 2026
- **Updated:** 29 Oct 2026

## What is CVE-2026-119202?

CVE-2026-119202 is a high-severity vulnerability in hapijs content, published on 29 Oct 2026. 

### Official description

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

Weakness: CWE-1333 (Inefficient Regular Expression Complexity)

## Which versions are affected by CVE-2026-119202?


## How do I fix CVE-2026-119202?

No fix has been published for CVE-2026-119202 yet. Limit exposure of the affected software until one is available.

## Is CVE-2026-119202 being exploited?

There is no known exploitation of CVE-2026-119202 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-119202 and fix it if it is affected.

What it is: CVE-2026-119202 is a high-severity vulnerability in hapijs content, published on 29 Oct 2026. 
Exploitation: There is no known exploitation of CVE-2026-119202 in the wild and no public exploit code.

Affected product: hapijs content. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-119202/ (Markdown: https://insights.sbomify.com/CVE-2026-119202/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-119202
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-119202
- OSV: https://osv.dev/vulnerability/CVE-2026-119202

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-119202/
Summaries are generated and may contain mistakes; the official description above is the record.