# CVE-2026-44974: Parameter smuggling in @hapi/content header parser allows upload-filter bypass via duplicate parameters

> Attackers can bypass upload filename allowlists by exploiting inconsistent duplicate parameter handling in HTTP header parsing, potentially leading to remote code execution.

- **Severity:** High 7.7 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:N/VI:L/VA:N/SC:N/SI:H/SA:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 17 Jul 2026
- **Updated:** 21 Jul 2026
- **Also known as:** ECHO-366e-1401-9fd9, GHSA-36hh-x5p5-jgc8, MINI-2w83-5fqj-34jw, MINI-4r9w-7qh8-v7gh, MINI-79c9-fgvc-8q3m, MINI-8mp8-2ccg-jxvg, MINI-hc8f-5xg3-x5g2, MINI-hq48-qvv2-694f, MINI-hx22-jpph-q58v, MINI-j9f7-4vfv-wjm9, MINI-p2gv-352x-93f6, MINI-p3mj-3qp6-jj27, MINI-pf3v-5q6r-j3h3, MINI-q5r5-72p5-jfp2, MINI-vh79-hmf3-hhqg, MINI-vvgx-c5fw-h623, ROOT-APP-NPM-CVE-2026-44974

## What is CVE-2026-44974?

CVE-2026-44974 is a high-severity vulnerability in hapijs content, published on 17 Jul 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

@hapi/content provided HTTP Content-* headers parsing. Prior to 6.0.2, Content.disposition() retained the last occurrence of each duplicate parameter while Content.type() retained the first occurrence of duplicate charset and boundary parameters, creating a parameter-smuggling primitive when another component in the request-processing chain resolves duplicates the opposite way. This can allow an upload filename allowlist bypass in headers such as Content-Disposition: form-data; name="file"; filename="safe.txt"; filename="shell.php". This issue is fixed in version 6.0.2.

Weakness: CWE-436 (Interpretation Conflict)

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

2 open source packages ship an affected version, including @hapi/content.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `@hapi/content` | npm | All versions | 6.0.2 |
| `@hapi/content` | npm | All versions | 6.0.2 |

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

Upgrade @hapi/content to 6.0.2 or later.

## Is CVE-2026-44974 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-44974 is a high-severity vulnerability in hapijs content, published on 17 Jul 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2026-44974 in the wild and no public exploit code.

Affected packages and fixed versions:
- @hapi/content (npm): affected all versions; fixed in 6.0.2
- @hapi/content (npm): affected all versions; fixed in 6.0.2

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-44974/ (Markdown: https://insights.sbomify.com/CVE-2026-44974/index.md)
```

## Sources

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

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