CVE-2026-15075: Infoleak
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.
Affected Software
Event History
Frequently Asked Questions
What is the severity of CVE-2026-15075?
CVE-2026-15075 has a risk rating of 70, indicating a moderate severity level.
What specific versions of Eclipse Vert.x are affected by CVE-2026-15075?
CVE-2026-15075 affects Eclipse Vert.x versions up to and including 4.5.29 in the 4.x branch and 5.1.4 in the 5.x branch.
How do I mitigate CVE-2026-15075 in my application?
To mitigate CVE-2026-15075, ensure you upgrade to a patched version of Eclipse Vert.x that addresses this vulnerability.
What is the impact of CVE-2026-15075 on application security?
CVE-2026-15075 can lead to information leaks due to the propagation of all request headers during cross-origin HTTP redirects.
Is CVE-2026-15075 related to any specific type of security issue?
Yes, CVE-2026-15075 is categorized under the CWE classification of Information Leak.