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.