Vulnerability in @hapi/wreck (CVE-2026-48022)
Summary
Vulnerability in @hapi/wreck (CVE-2026-48022). Confidential information can be exposed externally. Exploitable via beforeRedirect. Mitigation: upgrade to 18.1.2 or later.
Original description
The description as published by the source.
@hapi/wreck is an HTTP client utility. Prior to 18.1.2, Wreck strips credential headers including Authorization, Cookie, and Proxy-Authorization before following a cross-origin redirect, but the origin check compares hostnames only and ignores scheme and port, so credentials are forwarded intact across same-host port changes and HTTPS-to-HTTP downgrades, allowing a co-tenant on an adjacent port or a network-position attacker capable of forging a redirect to capture bearer tokens, session cookies, and proxy credentials and impersonate the victim against the upstream service. This issue is fixed in version 18.1.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-48022 has been found in @hapi/wreck.
Attackers can target a specific entry point like beforeRedirect over the network to misuse the product.
Confidential information can be exposed externally. CVSS score: 6.5/10.
What to do: upgrade @hapi/wreck to 18.1.2 or later.
If unsure, ask your IT team or search "@hapi/wreck CVE-2026-48022" on the vendor's site.
CVE-2026-48022 (@hapi/wreck) — CWE-319 / CVSS v3 6.5
Attack vector: remote (network-reachable) / unauthenticated
Attack surface: beforeRedirect
Patched: 18.1.2 — apply immediately
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-319) exists in @hapi/wreck. Attackers reach the vulnerable code path via beforeRedirect without authentication.
Check the vendor advisory for the affected versions of @hapi/wreck. Attack surface: beforeRedirect.
Severity: Medium (CVSS 6.5/10). Confidential information can be exposed externally.
Update to 18.1.2.
Until the patch is applied: disable the affected feature, apply WAF rules, or restrict access via network ACLs.
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 patch patch
Upgrade @hapi/wreck to 18.1.2ステージング環境で 18.1.2 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスを含めること。
-
3Post-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