@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.
CVE-2026-44974
HIGHPre-NVD 7.77.7—Trending — 3 sources updated this week
EchelonGraph scoreMEDIUM confidence
This high-severity CVE scores 7.7 under a secondary CVSS source (NVD's own analysis pending). EPSS exploit probability: 0.3%, top 73% of all CVEs by exploit prediction. GitHub Security Advisory data not yet ingested — confidence will rise once GHSA publishes (typical lag: hours to days for open-source ecosystem CVEs; never for infrastructure-only CVEs).
Triggered by: NVD CVSS baseline
Sources: epss, secondary
7.7
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
- High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS: 0%CVSS: 7.7Exploit: NoneExposed: 0
No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.
- CVSS v3
- 7.7
- EG Score
- 7.7(medium)
- EG Risk
- 50(Track)EG Risk 50/100SSVC: Track
EG Risk is EchelonGraph's 0–100 priority score: it fuses intrinsic severity with real-world exploitation and automatability so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner. Distinct from the 0–10 EG Score (severity).
How it’s computedSeverity77% × 45%Exploitation0% × 40%Automatability100% × 15%Action: Routine — remediate on your standard cadence. - EPSS
- 26.8%
- KEV
- Not listed
Published
May 27, 2026
Last Modified
July 21, 2026
Advisory Details (2)
Auto-updated Jul 17, 2026Patch available. Sources: github_commit, github.
github Patch Available
Parameter smuggling in @hapi/content header parser allows upload-filter bypass via duplicate parameters · Advisory · hapijs/content · GitHub
Affected: 6.0.2.
https://github.com/hapijs/content/security/advisories/GHSA-36hh-x5p5-jgc8github_commit
commit 3850079550c1 (hapijs/content)
Fix landed in hapijs/content commit 3850079550c1 — awaiting tagged release
https://github.com/hapijs/content/commit/3850079550c191d25e3643dc82a6d61144db8c2fVendor Advisories for CVE-2026-44974(1)
These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.
Affected Packages
(1 across 1 ecosystem)
npm(1)
| Package | Vulnerable range | Fixed in | Dependents |
|---|---|---|---|
| @hapi/content | — | 6.0.2 | — |
Weakness Classification(1)
MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.
Data Freshness Timeline
(refreshed 8× in last 7d / 8× in last 30d)
Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. Most recent first.
- 2026-07-23 03:15 UTCEG score recompute
- 2026-07-22 14:08 UTCEPSS rescore
- 2026-07-21 15:24 UTCEPSS rescore
- 2026-07-20 17:08 UTCEPSS rescore
- 2026-07-19 14:31 UTCEPSS rescore
- 2026-07-19 02:29 UTCEPSS rescore
- 2026-07-17 20:15 UTCEG score recompute▲ 7.70
- 2026-07-17 20:14 UTCMITRE cvelistV5CVSS v3 → 7.7 · CVSS v4 → 7.7
- 2026-06-14 23:18 UTCEPSS rescore
- 2026-06-13 23:00 UTCEPSS rescore
- 2026-06-12 23:12 UTCEPSS rescore
- 2026-05-27 01:14 UTCEG score recompute
Related CVEs(same CWE)
Same CWE
10 shownCWE-436
- CVE-2023-24813EG 10.0CRITICAL
- CVE-2025-25292EG 9.8EPSS 99%CRITICAL
- CVE-2025-25291EG 9.8EPSS 97%CRITICAL
- CVE-2021-45327EG 9.8CRITICAL
- CVE-2021-40870EG 9.8 KEVEPSS 100%CRITICAL
- CVE-2020-10180EG 9.8CRITICAL
- CVE-2019-19589EG 9.8CRITICAL
- CVE-2026-14198EG 9.1CRITICAL
- CVE-2024-38428EG 9.1CRITICAL
- CVE-2019-18792EG 9.1CRITICAL
Frequently asked(5)
What is CVE-2026-44974?
CVE-2026-44974 is a high vulnerability published on May 27, 2026. @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…
When was CVE-2026-44974 disclosed?
CVE-2026-44974 was first published in the National Vulnerability Database on May 27, 2026, with the most recent update on July 21, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-44974 actively exploited?
CVE-2026-44974 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 26.8% percentile likelihood of exploitation in the next 30 days — higher percentiles indicate greater predicted risk.
What is the CVSS score of CVE-2026-44974?
CVE-2026-44974 has a CVSS v3 base score of 7.7 (NVD).
How do I remediate CVE-2026-44974?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-44974, EchelonGraph cross-links them in the Vendor Advisories panel below — those typically contain the canonical remediation steps, fixed version numbers, and any vendor-specific mitigations.
Dependency Blast Radius
See which npm, PyPI, Go, and Maven packages are affected by CVE-2026-44974
Is Your Infrastructure Affected by CVE-2026-44974?
EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.