CVE-2026-15075

HIGHNVD 7.57.5—
EchelonGraph scoreMEDIUM confidence

This high-severity CVE scores 7.5 under NVD CVSS v3. EPSS exploit probability: 0.2%, top 91% 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, nvd
Trending — 3 sources updated this week
7.5EG
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 0%CVSS: 7.5Exploit: None knownExposed: 0

A fix is available — apply it.

In Eclipse Vert.x versions up to and including 4.5.29 (4.x branch) and 5.1.4 (5.x branch), DefaultRedirectHandler (vertx-core) propagates all request headers as-is across cross-origin HTTP 30x redirects. Only Content-Length is stripped; no origin comparison (scheme, host, port) is performed before copying headers to the redirect target. As a result, credential headers, including Authorization, Cookie, Proxy-Authorization, and arbitrary custom headers such as X-API-Token, are forwarded to the redirect destination without the caller's knowledge.

An attacker who can cause a Vert.x HttpClient to issue a request that is redirected to an attacker-controlled host (for example, by supplying a URL to a webhook dispatcher, image proxy, or microservice URL fetcher) can capture bearer tokens, basic-auth credentials, session cookies, and API keys attached to the original request.

CVSS v3
7.5
EG Score
7.5(medium)
EG Risk
34(Track)
EG Risk 34/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 computed
Severity75% × 45%
Exploitation0% × 40%
Automatability0% × 15%
Action: Routine — remediate on your standard cadence.
EPSS PROB
0%
EPSS %ILE
9%
KEV
Not listed

Published

July 14, 2026

Last Modified

July 14, 2026

Advisory Details (1)

Auto-updated Jul 14, 2026
No patch confirmed yet.
generic

Credential headers forwarded on cross-origin HTTP redirect in Eclipse Vert.x HttpClient (#161) · Issues · Eclipse Projects Security / cve-assignment · GitLab

https://gitlab.eclipse.org/security/cve-assignment/-/work_items/161

Vendor Advisories for CVE-2026-15075(4)

These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.

Patch Availability(2)

Vendor / EcosystemFixed in / PatchReleasedSource
redhatvertx-core-logging2026-08-12redhat
redhatvertx-core2026-07-30redhat

Patches are aggregated from vendor advisories (Red Hat, Microsoft, Cisco, GitHub) and package ecosystems (OSV, GHSA). Multiple rows for the same upstream release have been deduplicated.

Weakness Classification(2)

MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.

Data Freshness Timeline

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

Showing the most recent 100 of 145 total refreshes for this CVE.

  1. 2026-08-30 05:25 UTCEG score recompute
  2. 2026-08-30 05:25 UTCVendor advisory
  3. 2026-08-30 01:22 UTCEPSS rescore
  4. 2026-08-28 21:41 UTCEPSS rescore
  5. 2026-08-28 02:29 UTCEG score recompute
  6. 2026-08-28 02:29 UTCVendor advisory
  7. 2026-08-27 14:25 UTCEPSS rescore
  8. 2026-08-27 13:55 UTCVendor advisory
  9. 2026-08-27 00:01 UTCEG score recompute
  10. 2026-08-27 00:01 UTCVendor advisory
  11. 2026-08-26 14:46 UTCEPSS rescore
  12. 2026-08-26 07:34 UTCVendor advisory
  13. 2026-08-25 19:14 UTCEG score recompute
  14. 2026-08-25 19:14 UTCVendor advisory
  15. 2026-08-25 13:48 UTCEPSS rescore
  16. 2026-08-25 07:01 UTCVendor advisory
  17. 2026-08-24 19:55 UTCEG score recompute
  18. 2026-08-24 19:55 UTCVendor advisory
  19. 2026-08-24 04:56 UTCVendor advisory
  20. 2026-08-23 17:51 UTCVendor advisory
  21. 2026-08-23 06:47 UTCEG score recompute
  22. 2026-08-23 06:47 UTCVendor advisory
  23. 2026-08-23 00:19 UTCEPSS rescore
  24. 2026-08-22 19:42 UTCVendor advisory
  25. 2026-08-22 08:37 UTCEG score recompute
Show 75 more
  1. 2026-08-22 08:37 UTCVendor advisory
  2. 2026-08-21 23:49 UTCEPSS rescore
  3. 2026-08-21 21:32 UTCVendor advisory
  4. 2026-08-21 10:27 UTCVendor advisory
  5. 2026-08-20 23:22 UTCEG score recompute
  6. 2026-08-20 23:22 UTCVendor advisory
  7. 2026-08-20 22:55 UTCEPSS rescore
  8. 2026-08-20 12:17 UTCVendor advisory
  9. 2026-08-20 00:37 UTCEG score recompute
  10. 2026-08-20 00:37 UTCVendor advisory
  11. 2026-08-19 17:03 UTCEPSS rescore
  12. 2026-08-19 09:27 UTCVendor advisory
  13. 2026-08-18 22:19 UTCEG score recompute
  14. 2026-08-18 22:19 UTCVendor advisory
  15. 2026-08-18 13:48 UTCEPSS rescore
  16. 2026-08-18 10:27 UTCVendor advisory
  17. 2026-08-17 21:53 UTCEG score recompute
  18. 2026-08-17 21:53 UTCVendor advisory
  19. 2026-08-17 13:47 UTCEPSS rescore
  20. 2026-08-17 06:36 UTCVendor advisory
  21. 2026-08-16 19:31 UTCEG score recompute
  22. 2026-08-16 19:31 UTCVendor advisory
  23. 2026-08-16 14:56 UTCEPSS rescore
  24. 2026-08-16 08:19 UTCEG score recompute
  25. 2026-08-16 08:19 UTCVendor advisory
  26. 2026-08-16 02:14 UTCEPSS rescore
  27. 2026-08-15 21:14 UTCVendor advisory
  28. 2026-08-15 10:09 UTCEG score recompute
  29. 2026-08-15 10:09 UTCVendor advisory
  30. 2026-08-15 01:30 UTCEPSS rescore
  31. 2026-08-14 23:04 UTCVendor advisory
  32. 2026-08-14 12:00 UTCVendor advisory
  33. 2026-08-14 00:55 UTCEG score recompute
  34. 2026-08-14 00:55 UTCVendor advisory
  35. 2026-08-13 22:00 UTCEPSS rescore
  36. 2026-08-13 13:50 UTCVendor advisory
  37. 2026-08-13 02:46 UTCVendor advisory
  38. 2026-08-12 15:41 UTCEG score recompute
  39. 2026-08-12 15:41 UTCVendor advisory
  40. 2026-08-12 13:50 UTCEPSS rescore
  41. 2026-08-12 04:36 UTCVendor advisory
  42. 2026-08-11 17:32 UTCEG score recompute
  43. 2026-08-11 17:32 UTCVendor advisory
  44. 2026-08-11 13:42 UTCEPSS rescore
  45. 2026-08-11 06:26 UTCEG score recompute
  46. 2026-08-11 06:26 UTCVendor advisory
  47. 2026-08-11 00:00 UTCEPSS rescore
  48. 2026-08-10 19:22 UTCVendor advisory
  49. 2026-08-10 08:17 UTCVendor advisory
  50. 2026-08-09 21:13 UTCEG score recompute
  51. 2026-08-09 21:13 UTCVendor advisory
  52. 2026-08-09 13:46 UTCEPSS rescore
  53. 2026-08-09 10:08 UTCVendor advisory
  54. 2026-08-08 23:04 UTCEG score recompute
  55. 2026-08-08 23:04 UTCVendor advisory
  56. 2026-08-08 16:37 UTCEPSS rescore
  57. 2026-08-08 11:59 UTCVendor advisory
  58. 2026-08-08 00:54 UTCEG score recompute
  59. 2026-08-08 00:54 UTCVendor advisory
  60. 2026-08-07 13:49 UTCVendor advisory
  61. 2026-08-07 02:44 UTCVendor advisory
  62. 2026-08-06 15:39 UTCEG score recompute
  63. 2026-08-06 15:39 UTCVendor advisory
  64. 2026-08-06 13:46 UTCEPSS rescore
  65. 2026-08-06 04:26 UTCEG score recompute
  66. 2026-08-06 04:26 UTCVendor advisory
  67. 2026-08-05 19:17 UTCEPSS rescore
  68. 2026-08-05 17:21 UTCVendor advisory
  69. 2026-08-05 06:16 UTCVendor advisory
  70. 2026-08-04 19:05 UTCEG score recompute
  71. 2026-08-04 19:05 UTCVendor advisory
  72. 2026-08-04 15:09 UTCEPSS rescore
  73. 2026-08-04 10:38 UTCEPSS rescore
  74. 2026-08-04 08:00 UTCVendor advisory
  75. 2026-08-03 20:00 UTCEG score recompute

Related CVEs(same vendor + same CWE)

Frequently asked(5)

What is CVE-2026-15075?
CVE-2026-15075 is a high vulnerability published on July 14, 2026. In Eclipse Vert.x versions up to and including 4.5.29 (4.x branch) and 5.1.4 (5.x branch), DefaultRedirectHandler (vertx-core) propagates all request headers as-is across cross-origin HTTP 30x redirects. Only Content-Length is stripped; no origin comparison (scheme, host, port) is performed before…
When was CVE-2026-15075 disclosed?
CVE-2026-15075 was first published in the National Vulnerability Database on July 14, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-15075 actively exploited?
CVE-2026-15075 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0% probability of exploitation in the next 30 days, which ranks it in the top 90.6% of all scored CVEs.
What is the CVSS score of CVE-2026-15075?
CVE-2026-15075 has a CVSS v3 base score of 7.5 (NVD).
How do I remediate CVE-2026-15075?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-15075, 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

Explore the affected products and dependency analysis for CVE-2026-15075

Explore →

Is Your Infrastructure Affected by CVE-2026-15075?

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

Start Free Scan →Browse All CVEs