Vulnerability in @hapi/content (CVE-2026-44974)
Summary
Vulnerability in @hapi/content (CVE-2026-44974). Risk of unauthorized operations or information disclosure. Mitigation: upgrade to 6.0.2 or later.
Original description
The description as published by the source.
@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.
Source: GitHub Security Advisories (Global) NVD GitHub Advisory
Auto-generated summary
Assembled by SecPulse from the source data (CVSS, CWE, affected versions) using templates — no AI involved. Check the original description and references below for exact details.
A vulnerability tracked as CVE-2026-44974 has been found in @hapi/content.
Risk of unauthorized operations or information disclosure.
What to do: upgrade @hapi/content to 6.0.2 or later.
If unsure, ask your IT team or search "@hapi/content CVE-2026-44974" on the vendor's site.
CVE-2026-44974 (@hapi/content) — CWE-436
Patched: 6.0.2 — apply immediately
Workaround: Pre or post validate headers looking for duplicates.
Plan: 1) Audit SBOM/dependencies, 2) Stage→prod upgrade, 3) Add WAF/proxy monitoring on affected endpoints, 4) Hunt IOCs in logs.
Refs: see the GHSA / vendor advisory / patched release linked on this page.
A vulnerability (CWE-436) exists in @hapi/content.
Check the vendor advisory for the affected versions of @hapi/content.
Severity: ?. Risk of unauthorized operations or information disclosure.
Update to 6.0.2.
Workaround: Pre or post validate headers looking for duplicates.
Search webserver/proxy logs for unusual request patterns matching this CVE's known IOCs. Run grep -r '@hapi/content' . against your dependency files (package-lock.json, requirements.txt, go.sum) to find affected services.
Response actions
Concrete steps and command examples for SOC/SRE teams to execute in order
-
1Identify exposure identify
grep -r '@hapi/content' . | grep -v node_modulesリポジトリと本番環境の依存ファイル (package-lock.json / requirements.txt / go.sum / Gemfile.lock 等) で
@hapi/contentを grep し、稼働しているサービス・バージョンを把握する。 -
2Apply temporary workaround mitigate
Pre or post validate headers looking for duplicates.パッチが適用されるまでの応急処置として、Pre or post validate headers looking for duplicates. を実施。回避策の副作用 (機能低下) を確認した上で。
-
3Apply patch patch
Upgrade @hapi/content to 6.0.2ステージング環境で 6.0.2 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスを含めること。
-
4Post-deployment verification verify
Confirm patched version is live in productionパッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番ではアクセスログ・WAF でアラート再発が無いか継続監視。
Affected packages
References
- advisory github.com
- advisory github.com
- advisory nvd.nist.gov
- package github.com
- patch github.com
- web github.com