CVE-2026-130626

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

Published Nov 17, 2026 CVSS 3.1 · 7.5 High EPSS n/a KEV · Not listed
Description
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.

Analysis

AI-generated

Technical impact

The vulnerability arises inside the a2a Java SDK HTTP client, where GET and DELETE requests can silently follow cross‑authority redirects when an application supplies a JDK HttpClient that permits redirects. The core JDK client removes the standard Authorization header but forwards four allow‑listed custom credential headers—X-API-Key, API-Key, X-Auth-Token, and X-Authentication—to the redirect target. This means that an attacker can host a destination service to which the client redirects, thereby capturing those header values and potentially compromising downstream APIs that rely on those keys. The issue is limited to credentialed GET and DELETE requests and does not affect other HTTP methods or streaming requests. The exposed data represents a security breach that can lead to unauthorized access to cloud or internal APIs and increased attack surface.

Affected Systems

Affecting the a2a-java SDK HTTP client versions prior to 1.5.0.Final. The bug surfaces when an application configures the SDK’s underlying JDK HttpClient with Redirect.NORMAL or Redirect.ALWAYS, the documented approach to enable POST redirects. The vulnerable functions include JdkGetBuilder.get(), JdkGetBuilder.getAsyncSSE(), and JdkDeleteBuilder.delete().

Risk and Exploitability

The CVSS score is 7.5, indicating a high‑severity flaw. Exploitation requires the application to use a redirect‑capable HttpClient for GET or DELETE operations, a common configuration for applications that use the SDK. While the EPSS score is not available, the vulnerability is not currently catalogued in CISA KEV, suggesting limited widespread exploitation reports. Nevertheless, given the potential to exfiltrate API credentials and the lack of automatic redirect mitigation for GET and DELETE, organizations should treat this as a high‑risk issue.

Remediation

Vendor Solution

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.


Vendor Workaround

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


OpenCVE Recommended Actions

  • Upgrade the a2a Java SDK to version 1.5.0.Final or later.
  • On older SDK versions configure any supplied JDK HttpClient with HttpClient.Redirect.NEVER to stop automatic redirect following for GET and DELETE requests.
  • Review and audit outbound requests to ensure that custom credential headers (X‑API‑Key, API‑Key, X‑Auth‑Token, X‑Authentication) are not sent to untrusted third‑party endpoints, and consider restricting or stripping these headers server‑side if they are not required.

Generated by OpenCVE AI on November 17, 2026 at 15:24 UTC.

Tracking

Sign in to view the affected projects.

Advisories

No advisories available
History
Type Values Removed Values Added
Description 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.
Title JDK HTTP client GET/DELETE follow cross-authority redirects with injected client, leaking API-key headers (POST-only gap)
Weaknesses CWE-522
References
Metrics cvssV3_1

{'score': 7.5, 'vector': 'CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N'}

Subscriptions

No data.

Weaknesses
  • CWE-522

    Insufficiently Protected Credentials

Sources

Status
PUBLISHED
Assigner
redhat-cnalr
Published
Updated
Nov 17, 2026, 6:05 PM
Reserved
Nov 17, 2026, 2:10 PM
Status
Received
Published
Nov 17, 2026, 3:17 PM
Modified
Nov 17, 2026, 3:17 PM