CVE-2026-48022

MEDIUMPre-NVD 6.56.5
EchelonGraph scoreLOW confidence

This medium-severity CVE scores 6.5 under the CNA's CVSS (NVD's own analysis pending). EPSS exploit probability: 0.0%, top 99% 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).

Triggered by: NVD CVSS baseline
Sources: cna:github_m, epss
6.5
EchelonGraph verdictMonitorLow exploitation likelihood right now — keep watching.
  • Lower severity and no public exploit yet
CISA-KEV: Not listedEPSS: 0%CVSS: 6.5Exploit: NoneExposed: 0

No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.

@hapi/wreck: Sensitive credential headers leak across cross-port and cross-scheme redirects

Impact

Wreck strips credential headers (Authorization, Cookie, Proxy-Authorization) before following a cross-origin redirect, but the origin check compares hostnames only and ignores scheme and port. As a result, 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. The fix replaces the hostname comparison with a full-origin comparison (scheme, host, and port), aligning the behavior with the WHATWG Fetch same-origin definition used by browsers.

Patches

Upgrade to >= 18.1.2.

Workarounds

  • Set redirects: 0 (default) and handle redirects manually with a strict origin check.
  • Use the beforeRedirect hook to inspect the redirect target and abort or strip sensitive headers before the follow-on request.

CVSS v3
6.5
EG Score
6.5(low)
EPSS
1.2%
KEV
Not listed

Published

June 11, 2026

Last Modified

June 11, 2026

Vendor 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)
PackageVulnerable rangeFixed inDependents
@hapi/wreck—18.1.2—

Data Freshness Timeline

(refreshed 7× in last 7d / 27× 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.

  1. 2026-07-07 03:12 UTCEG score recompute
  2. 2026-07-05 21:39 UTCEG score recompute
  3. 2026-07-04 19:16 UTCEG score recompute
  4. 2026-07-03 15:51 UTCEG score recompute
  5. 2026-07-02 13:34 UTCEG score recompute
  6. 2026-07-01 11:17 UTCEG score recompute
  7. 2026-06-30 09:01 UTCEG score recompute
  8. 2026-06-29 06:44 UTCEG score recompute
  9. 2026-06-28 03:35 UTCEG score recompute
  10. 2026-06-27 01:19 UTCEG score recompute
  11. 2026-06-25 23:03 UTCEG score recompute
  12. 2026-06-24 20:47 UTCEG score recompute
  13. 2026-06-23 15:25 UTCEG score recompute
  14. 2026-06-22 13:09 UTCEG score recompute
  15. 2026-06-21 10:43 UTCEG score recompute
  16. 2026-06-20 08:23 UTCEG score recompute
  17. 2026-06-19 06:06 UTCEG score recompute
  18. 2026-06-18 03:36 UTCEG score recompute
  19. 2026-06-17 01:19 UTCEG score recompute
  20. 2026-06-15 23:04 UTCEG score recompute
  21. 2026-06-14 23:18 UTCEPSS rescore
  22. 2026-06-14 20:47 UTCEG score recompute
  23. 2026-06-13 23:00 UTCEPSS rescore
  24. 2026-06-13 18:32 UTCEG score recompute
  25. 2026-06-12 23:12 UTCEPSS rescore
Show 2 more
  1. 2026-06-12 16:13 UTCEG score recompute
  2. 2026-06-11 13:56 UTCEG score recompute

Frequently asked(5)

What is CVE-2026-48022?
CVE-2026-48022 is a medium vulnerability published on June 11, 2026. @hapi/wreck: Sensitive credential headers leak across cross-port and cross-scheme redirects Impact Wreck strips credential headers (Authorization, Cookie, Proxy-Authorization) before following a cross-origin redirect, but the origin check compares hostnames only and ignores scheme and port. As a…
When was CVE-2026-48022 disclosed?
CVE-2026-48022 was first published in the National Vulnerability Database on June 11, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-48022 actively exploited?
CVE-2026-48022 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 1.2% percentile likelihood of exploitation in the next 30 days — higher percentiles indicate greater predicted risk.
What is the CVSS score of CVE-2026-48022?
CVE-2026-48022 has a CVSS v4.0 base score of 6.5 (CNA self-assessment; NVD's own analysis pending). The EG score is currently aggregating — additional source signals are being incorporated as they become available..
How do I remediate CVE-2026-48022?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-48022, EchelonGraph cross-links them in the Vendor Advisories panel below — those typically contain the canonical remediation steps, fixed version numbers, and any vendor-specific mitigations.

Dependency Blast Radius

See which npm, PyPI, Go, and Maven packages are affected by CVE-2026-48022

Explore →

Is Your Infrastructure Affected by CVE-2026-48022?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.

Start Free Scan →Browse All CVEs