← Back
CVE-2026-44979
Information Disclosure in @hapi/wreck (CVE-2026-44979)
Summary
vulnerability in @hapi/wreck (CVE-2026-44979). Risk of unauthorized operations or information disclosure. Exploitable via ``Authorization``. Mitigation: upgrade to `18.1.1` or later.
AI summary snake-internal / snake-material-v2
A vulnerability tracked as **CVE-2026-44979** has been found in @hapi/wreck.
Attackers can target a specific entry point like ``Authorization`` over the network to misuse the product.
Risk of unauthorized operations or information disclosure. CVSS score: ?/10.
What to do: upgrade @hapi/wreck to **18.1.1** or later.
If unsure, ask your IT team or search "@hapi/wreck CVE-2026-44979" on the vendor's site.
CVE-2026-44979 (@hapi/wreck) — CWE-200 /
Attack surface: `Authorization` / `Cookie` / `false` / `beforeRedirect`
Patched: `18.1.1` — apply immediately
Workaround: - Leave redirects at its default (`false`) — applications that never enable redirect following are not affected.
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
**information disclosure** (CWE-200) exists in @hapi/wreck. Attackers reach the vulnerable code path via ``Authorization`` without authentication.
📍 Affected scope
@hapi/wreck — . Attack surface: `Authorization` / `Cookie` / `false` / `beforeRedirect`.
🔥 Severity
Severity: ?. Risk of unauthorized operations or information disclosure
🔧 How to fix
Update to **18.1.1**.
🛡️ Workaround
Workaround: - Leave redirects at its default (`false`) — applications that never enable redirect following are not affected.
🔍 Detection
Search webserver/proxy logs for unusual request patterns matching this CVE's known IOCs. Run `grep -r '@hapi/wreck' .` 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/wreck' . | grep -v node_modulesリポジトリと本番環境の依存ファイル (package-lock.json / requirements.txt / go.sum / Gemfile.lock 等) で `@hapi/wreck` を grep し、稼働しているサービス・バージョンを把握する。
-
5Apply temporary workaround mitigate
- Leave redirects at its default (`false`) — applications that never enable redirect following are not affected.パッチが適用されるまでの応急処置として、- Leave redirects at its default (`false`) — applications that never enable redirect following are not affected. を実施。回避策の副作用 (機能低下) を確認した上で。
-
6Apply patch patch
Upgrade @hapi/wreck to 18.1.1ステージング環境で 18.1.1 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスと、Step 3 で見つけた異常検知の続報チェックを含めること。
-
7Post-deployment verification verify
Confirm patched version is live in productionパッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番では Step 3 と同じログクエリでアラート再発が無いか継続監視。
Affected packages
npm
@hapi/wreck
[{"type":"SEMVER","events":[{"introduced":"0"},{"fixed":"18.1.1"}]}]