CVE-2026-48022

MEDIUMPre-NVD 6.56.5—
EchelonGraph scoreMEDIUM confidence

This medium-severity CVE scores 6.5 under a secondary CVSS source (NVD's own analysis pending). EPSS exploit probability: 0.2%, top 93% 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: epss, secondary
6.5EG
EchelonGraph verdictMonitorLow exploitation likelihood right now — keep watching.
  • Lower severity and no public exploit yet
CISA-KEV: Not listedEPSS PROB: 0.2%CVSS: 6.5Exploit: None knownExposed services: Not assessed

A fix is available — apply it.

@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.

CVSS v3
6.5
EG Score
6.5MEDIUMmedium confidence
EG Risk
29
EG Risk 29/100

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 computed
Severity65% × 45%
Exploitation0% × 40%
Automatability0% × 15%
EPSS PROB
0.2%
EPSS %ILE
6th
KEV
Not listed

Published

June 11, 2026

Last Modified

July 23, 2026

Advisory Details (3)

Auto-updated Jul 17, 2026
Patch available. Sources: github, github_pr, github_commit.
github_commit

commit b93323b63ad3 (hapijs/wreck)

Fix landed in hapijs/wreck commit b93323b63ad3 — awaiting tagged release

https://github.com/hapijs/wreck/commit/b93323b63ad3adb14d2b4019d77219182211641e
github_pr

fix: 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/313
githubMentions a patch (unverified)

Sensitive credential headers leak across cross-port and cross-scheme redirects · Advisory · hapijs/wreck · GitHub

https://github.com/hapijs/wreck/security/advisories/GHSA-x426-x7cc-3fpc

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 rangeFix by version rangeDependents
@hapi/wreck—
  • every version up to 18.1.2: fixed in 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 / 23× 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-10-10 20:00 UTCEPSS rescore
  2. 2026-10-09 20:07 UTCEPSS rescore
  3. 2026-10-08 17:12 UTCEPSS rescore
  4. 2026-10-07 23:48 UTCEPSS rescore
  5. 2026-10-06 15:18 UTCEPSS rescore
  6. 2026-10-05 17:43 UTCEPSS rescore
  7. 2026-10-04 23:22 UTCEPSS rescore
  8. 2026-10-03 14:25 UTCEPSS rescore
  9. 2026-10-03 08:39 UTCOSV refresh
  10. 2026-10-01 19:50 UTCEPSS rescore
  11. 2026-09-30 15:03 UTCEPSS rescore
  12. 2026-09-28 13:51 UTCEPSS rescore
  13. 2026-09-27 13:48 UTCEPSS rescore
  14. 2026-09-26 15:59 UTCEPSS rescore
  15. 2026-09-26 00:27 UTCEPSS rescore
  16. 2026-09-23 17:53 UTCEPSS rescore
  17. 2026-09-20 20:16 UTCEPSS rescore
  18. 2026-09-18 19:28 UTCEPSS rescore
  19. 2026-09-16 14:08 UTCEPSS rescore
  20. 2026-09-16 05:15 UTCEPSS rescore
  21. 2026-09-14 04:10 UTCEG score recompute
  22. 2026-09-13 16:47 UTCEPSS rescore
  23. 2026-09-11 14:53 UTCEPSS rescore
  24. 2026-09-10 09:35 UTCEPSS rescore
  25. 2026-09-08 22:01 UTCEPSS rescore
Show 68 more
  1. 2026-09-07 16:01 UTCEPSS rescore
  2. 2026-09-06 13:47 UTCEPSS rescore
  3. 2026-09-04 05:06 UTCEPSS rescore
  4. 2026-09-02 14:12 UTCEPSS rescore
  5. 2026-09-01 13:54 UTCEPSS rescore
  6. 2026-08-31 00:05 UTCEG score recompute
  7. 2026-08-30 19:17 UTCEPSS rescore
  8. 2026-08-30 01:22 UTCEPSS rescore
  9. 2026-08-28 21:41 UTCEPSS rescore
  10. 2026-08-27 14:25 UTCEPSS rescore
  11. 2026-08-26 14:46 UTCEPSS rescore
  12. 2026-08-25 13:49 UTCEPSS rescore
  13. 2026-08-25 00:05 UTCEG score recompute
  14. 2026-08-23 10:43 UTCEG score recompute
  15. 2026-08-21 23:49 UTCEPSS rescore
  16. 2026-08-21 19:33 UTCEG score recompute
  17. 2026-08-20 22:55 UTCEPSS rescore
  18. 2026-08-20 17:15 UTCEG score recompute
  19. 2026-08-19 17:04 UTCEPSS rescore
  20. 2026-08-19 14:54 UTCEG score recompute
  21. 2026-08-17 13:47 UTCEPSS rescore
  22. 2026-08-17 05:02 UTCEG score recompute
  23. 2026-08-16 14:56 UTCEPSS rescore
  24. 2026-08-16 02:46 UTCEG score recompute
  25. 2026-08-16 02:14 UTCEPSS rescore
  26. 2026-08-15 01:30 UTCEPSS rescore
  27. 2026-08-13 22:14 UTCEG score recompute
  28. 2026-08-13 22:00 UTCEPSS rescore
  29. 2026-08-12 14:36 UTCEG score recompute
  30. 2026-08-12 13:51 UTCEPSS rescore
  31. 2026-08-11 12:16 UTCEG score recompute
  32. 2026-08-11 00:00 UTCEPSS rescore
  33. 2026-08-10 10:00 UTCEG score recompute
  34. 2026-08-09 13:46 UTCEPSS rescore
  35. 2026-08-09 07:45 UTCEG score recompute
  36. 2026-08-08 16:37 UTCEPSS rescore
  37. 2026-08-07 03:13 UTCEG score recompute
  38. 2026-08-06 13:47 UTCEPSS rescore
  39. 2026-08-06 00:57 UTCEG score recompute
  40. 2026-08-05 19:17 UTCEPSS rescore
  41. 2026-08-04 22:41 UTCEG score recompute
  42. 2026-08-04 15:10 UTCEPSS rescore
  43. 2026-08-04 10:39 UTCEPSS rescore
  44. 2026-08-03 20:25 UTCEG score recompute
  45. 2026-08-03 10:36 UTCEPSS rescore
  46. 2026-08-02 18:09 UTCEG score recompute
  47. 2026-08-02 02:27 UTCEPSS rescore
  48. 2026-07-31 13:37 UTCEG score recompute
  49. 2026-07-30 16:28 UTCEPSS rescore
  50. 2026-07-30 09:41 UTCEG score recompute
  51. 2026-07-30 01:30 UTCEPSS rescore
  52. 2026-07-29 04:53 UTCEG score recompute
  53. 2026-07-28 15:37 UTCEPSS rescore
  54. 2026-07-27 08:05 UTCEG score recompute
  55. 2026-07-26 05:16 UTCEG score recompute
  56. 2026-07-25 14:18 UTCEPSS rescore
  57. 2026-07-24 14:18 UTCEPSS rescore
  58. 2026-07-23 14:18 UTCEPSS rescore
  59. 2026-07-23 03:18 UTCEG score recompute
  60. 2026-07-22 14:08 UTCEPSS rescore
  61. 2026-07-21 15:24 UTCEPSS rescore
  62. 2026-07-20 17:08 UTCEPSS rescore
  63. 2026-07-19 14:31 UTCEPSS rescore
  64. 2026-07-19 02:29 UTCEPSS rescore
  65. 2026-06-14 23:18 UTCEPSS rescore
  66. 2026-06-13 23:00 UTCEPSS rescore
  67. 2026-06-12 23:12 UTCEPSS rescore
  68. 2026-06-11 13:56 UTCEG score recompute

Related CVEs(same product + same CWE)

Same product

1 shown

npm:@hapi/wreck

Frequently asked(5)

What is CVE-2026-48022?
CVE-2026-48022 is a medium vulnerability published on June 11, 2026. @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…
When was CVE-2026-48022 disclosed?
CVE-2026-48022 was first published on June 11, 2026, with the most recent update on July 23, 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 0.2% probability of exploitation in the next 30 days (6th percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2026-48022?
CVE-2026-48022 has a CVSS base score of 6.5 (a secondary CVSS source that NVD displays; NVD's own analysis pending).
How do I remediate CVE-2026-48022?
A fix for CVE-2026-48022 is available: update to the fixed version the vendor names in its advisory. The vendor advisories EchelonGraph has for CVE-2026-48022 are linked in the Vendor Advisories panel on this page.

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.

Book a Demo →Browse All CVEs