CVE-2026-130626 PUBLISHED

JDK HTTP client GET/DELETE follow cross-authority redirects with injected client, leaking API-key headers (POST-only gap)

Assigner: redhat-cnalr
Reserved: 17.11.2026 Published: 17.11.2026 Updated: 17.11.2026

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 request. The JDK strips Authorization cross-origin, but forwards the four allowlisted custom credential headers (X-API-Key, API-Key, X-Auth-Token, X-Authentication) to the attacker-controlled authority. This is an incomplete-fix variant of GHSA-9rhm: the fix hardened the default client and added a POST-only two-step opt-in, but never covered GET/DELETE.

Metrics

CVSS Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N
CVSS Score: 7.5

Product Status

Vendor a2a-java
Product a2a-java-sdk-http-client
Versions Default: unaffected
  • affected from 1.3.0.Final to 1.4.0.Final (incl.)

Workarounds

On affected versions, supply a JDK HttpClient configured with HttpClient.Redirect.NEVER to prevent automatic redirect following.

Solutions

Upgrade to 1.5.0.Final or later. PR #1257 routes JDK GET, DELETE, and SSE requests through a client with native redirects disabled. Synchronous GET redirects are handled explicitly by the SDK using the shared RedirectHeaderPolicy; streaming requests do not follow redirects. The reporter reviewed the proposed fix and confirmed that it addresses the reported issue.

Credits

  • manus-use reporter

References

Problem Types

  • CWE-522 CWE