← Back
CVE-2026-48022
medium
CVSS 6.5
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.
AI summary snake-internal / snake-material-v2
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.
❓ What is the problem
**A vulnerability** (CWE-319) exists in @hapi/wreck. Attackers reach the vulnerable code path via ``beforeRedirect`` without authentication.
📍 Affected scope
@hapi/wreck — . Attack surface: `beforeRedirect`.
🔥 Severity
Severity: Medium (CVSS 6.5/10). Confidential information can be exposed externally
🔧 How to fix
Update to **18.1.2**.
🛡️ Workaround
Until the patch is applied: disable the affected feature, apply WAF rules, or restrict access via network ACLs.
🔍 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 し、稼働しているサービス・バージョンを把握する。
-
6Apply patch patch
Upgrade @hapi/wreck to 18.1.2ステージング環境で 18.1.2 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスと、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.2"}]}]