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.
Original description
The description as published by the source.
@hapi/wreck is an HTTP client utility. Prior to 18.1.1, when @hapi/wreck follows a 3xx redirect to a different hostname, only the Authorization and Cookie headers are stripped, and the standard credential header Proxy-Authorization is forwarded intact to the redirect target, potentially exposing forward-proxy credentials to a host outside the original trust boundary when redirects are enabled through the redirects option or Wreck.defaults({ redirects: ... }). This issue is fixed in version 18.1.1.
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-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.
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.
Information disclosure (CWE-200) exists in @hapi/wreck. Attackers reach the vulnerable code path via Authorization.
Check the vendor advisory for the affected versions of @hapi/wreck. Attack surface: Authorization / Cookie / false / beforeRedirect.
Severity: ?. Risk of unauthorized operations or information disclosure.
Update to 18.1.1.
Workaround: - Leave redirects at its default (false) — applications that never enable redirect following are not affected.
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
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 し、稼働しているサービス・バージョンを把握する。 -
2Apply 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. を実施。回避策の副作用 (機能低下) を確認した上で。 -
3Apply patch patch
Upgrade @hapi/wreck to 18.1.1ステージング環境で 18.1.1 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスを含めること。
-
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
- patch github.com
- web github.com
- web github.com
- web github.com