@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.
CVE-2026-48022
This medium-severity CVE scores 6.5 under a secondary CVSS source (NVD's own analysis pending). EPSS exploit probability: 0.1%, top 98% of all CVEs by exploit prediction. GitHub Security Advisory data not yet ingested — confidence will rise once GHSA publishes (typical lag: hours to days for open-source ecosystem CVEs; never for infrastructure-only CVEs).
- Lower severity and no public exploit yet
No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.
- CVSS v3
- 6.5
- EG Score
- 6.5(medium)
- EG Risk
- 29(Track)EG Risk 29/100SSVC: Track
EG Risk is EchelonGraph's 0–100 priority score: it fuses intrinsic severity with real-world exploitation and automatability so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner. Distinct from the 0–10 EG Score (severity).
How it’s computedSeverity65% × 45%Exploitation0% × 40%Automatability0% × 15%Action: Routine — remediate on your standard cadence. - EPSS
- 2.5%
- KEV
- Not listed
Published
June 11, 2026
Last Modified
July 23, 2026
Advisory Details (3)
Auto-updated Jul 17, 2026commit b93323b63ad3 (hapijs/wreck)
Fix landed in hapijs/wreck commit b93323b63ad3 — awaiting tagged release
https://github.com/hapijs/wreck/commit/b93323b63ad3adb14d2b4019d77219182211641efix: cross-origin redirect should also remove sensitive headers
Fix merged in hapijs/wreck PR #313 on 2026-05-20 — awaiting tagged release
https://github.com/hapijs/wreck/pull/313Sensitive credential headers leak across cross-port and cross-scheme redirects · Advisory · hapijs/wreck · GitHub
https://github.com/hapijs/wreck/security/advisories/GHSA-x426-x7cc-3fpcVendor Advisories for CVE-2026-48022(1)
These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.
Affected Packages
(1 across 1 ecosystem)
npm(1)
| Package | Vulnerable range | Fixed in | Dependents |
|---|---|---|---|
| @hapi/wreck | — | 18.1.2 | — |
Weakness Classification(3)
MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.
Data Freshness Timeline
(refreshed 7× in last 7d / 7× in last 30d)
Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. Most recent first.
- 2026-07-23 14:18 UTCEPSS rescore
- 2026-07-23 03:18 UTCEG score recompute
- 2026-07-22 14:08 UTCEPSS rescore
- 2026-07-21 15:24 UTCEPSS rescore
- 2026-07-20 17:08 UTCEPSS rescore
- 2026-07-19 14:31 UTCEPSS rescore
- 2026-07-19 02:29 UTCEPSS rescore
- 2026-06-14 23:18 UTCEPSS rescore
- 2026-06-13 23:00 UTCEPSS rescore
- 2026-06-12 23:12 UTCEPSS rescore
- 2026-06-11 13:56 UTCEG score recompute
Frequently asked(5)
What is CVE-2026-48022?
When was CVE-2026-48022 disclosed?
Is CVE-2026-48022 actively exploited?
What is the CVSS score of CVE-2026-48022?
How do I remediate CVE-2026-48022?
Dependency Blast Radius
See which npm, PyPI, Go, and Maven packages are affected by CVE-2026-48022
Is Your Infrastructure Affected by CVE-2026-48022?
EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.