← Back
CVE-2026-44974
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.
AI summary snake-internal / snake-material-v2
A vulnerability tracked as **CVE-2026-44974** has been found in @hapi/content.
Risk of unauthorized operations or information disclosure. CVSS score: ?/10.
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.
❓ What is the problem
**A vulnerability** (CWE-436) exists in @hapi/content.
📍 Affected scope
@hapi/content — .
🔥 Severity
Severity: ?. Risk of unauthorized operations or information disclosure
🔧 How to fix
Update to **6.0.2**.
🛡️ Workaround
Workaround: Pre or post validate headers looking for duplicates.
🔍 Detection
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 (7 steps)
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 し、稼働しているサービス・バージョンを把握する。
-
5Apply temporary workaround mitigate
Pre or post validate headers looking for duplicates.パッチが適用されるまでの応急処置として、Pre or post validate headers looking for duplicates. を実施。回避策の副作用 (機能低下) を確認した上で。
-
6Apply patch patch
Upgrade @hapi/content to 6.0.2ステージング環境で 6.0.2 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスと、Step 3 で見つけた異常検知の続報チェックを含めること。
-
7Post-deployment verification verify
Confirm patched version is live in productionパッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番では Step 3 と同じログクエリでアラート再発が無いか継続監視。
Affected packages
npm
@hapi/content
[{"type":"SEMVER","events":[{"introduced":"0"},{"fixed":"6.0.2"}]}]