Java HTTP Client Libraries Insecure Redirect Credential Leak Vulnerabilities
Is it fixed? Not yet.
Ongoing since Nov 17, 15:17 UTC. First reported Nov 17, 15:17 UTC.
What happened
Multiple Java HTTP client transport components contain high-severity vulnerabilities involving insecure redirect handling. The Vert.x HTTP client transport copies headers verbatim on POST redirects without credential stripping or same-authority checks, while the core JDK HTTP client restricts redirect-neutralization solely to the POST path, leaving GET and DELETE requests vulnerable to credential leakage.
What caused it?
The Vert.x client hand-rolls a POST redirect follower copying headers verbatim without checks, and the core JDK client applies redirect-neutralization only to the POST path while leaving GET and DELETE methods exposed.
Source: tenable.com
No verified workaround yet
None of the linked reports describe a mitigation. This page updates when one appears.
Official fixTimeline
- Investigating(current)
- Workaround available(upcoming)
- Resolved(upcoming)
- First report on security advisory
core JDK HTTP client (a2a-java-sdk-http-client) applies the GHSA-9rhm redirect-neutralization only to the POST path.: CVE-2026-130626 (High)
Source
Evidence
2 reports · 2 CVEShow
- [1]CVEcore JDK HTTP client (a2a-java-sdk-http-client) applies the GHSA-9rhm redirect-neutralization only to the POST path.: CVE-2026-130626 (High)(opens security advisory in a new tab)
High severity. The core JDK HTTP client (a2a-java-sdk-http-client) applies the GHSA-9rhm redirect-neutralization only to the POST path. JdkGetBuilder.get(), JdkGetBuilder.getAsyncSSE(), and JdkDeleteBuilder.delete() call the injected httpClient directly, with no redirect gate. An application that supplies a redirect-capable HttpClient (Redirect.NORMAL/ALWAYS) — which is the SDK-documented way to enable POST redirects — silently follows cross-authority redirects on every credentialed GET/DELETE…
by Tenable 0upvotes 0comments94% match
- [2]CVE First reportVert.x HTTP client transport (a2a-java-sdk-http-client-vertx) hand-rolls a POST redirect follower that, when the documented PostBuilder.followRedirects(true) opt-in: CVE-2026-130627 (High)(opens security advisory in a new tab)
High severity. The Vert.x HTTP client transport (a2a-java-sdk-http-client-vertx) hand-rolls a POST redirect follower that, when the documented PostBuilder.followRedirects(true) opt-in is enabled, re-issues the redirected request with the full request header map copied verbatim and performs no credential stripping and no same-authority check. A malicious, compromised, or mistyped agent that returns a 30x response with an absolute cross-host Location causes the client to forward the standard…
by Tenable 0upvotes 0comments
FAQ
What happened in the Java issue?
Multiple Java HTTP client transport components contain high-severity vulnerabilities involving insecure redirect handling. The Vert.x HTTP client transport copies headers verbatim on POST redirects without credential stripping or same-authority checks, while the core JDK HTTP client restricts redirect-neutralization solely to the POST path, leaving GET and DELETE requests vulnerable to credential leakage.
What is affected by the Java issue?
Java. Also affected at the same time: Apache.
When did the Java issue start and end?
It started Nov 17, 15:17 UTC and is still ongoing (1 d 13 h so far). This page updates as it develops.
How do I get alerts for Java?
Subscribe to the Java RSS feed for every new Java incident, or connect an AI assistant to WhatBrokeToday over MCP and ask whether Java is down. Java feed
Where does this information come from?
WhatBrokeToday collects public status pages, developer community reports and security advisories, groups the ones about the same problem, and links every report under Evidence on this page. This one has 2 reports from 1 independent source.