Disclaimer: This content was generated using AI. While we strive for accuracy, please verify critical information with official sources.
Sources: National Vulnerability Database, CISA KEV, Exploit-DB
CVE-2026-111763 Overview
CVE-2026-111763 is a credential exposure vulnerability [CWE-522] in the A2A Java SDK, the official Java SDK for the Agent2Agent (A2A) Protocol. Versions prior to 1.3.0.Final allow a malicious or compromised remote agent to coerce the default JDK-based client into forwarding a configured API key to a third-party server. The flaw resides in AuthInterceptor.intercept, which uses APIKeySecurityScheme.name() from the remote AgentCard directly as the HTTP header name carrying the credential, without validating the declared location. Because JdkA2AHttpClient uses followRedirects(NORMAL), agent-controlled cross-origin redirects forward the custom credential-bearing header even when the standard Authorization header is stripped.
Critical Impact
Attackers controlling a remote AgentCard and redirect response can exfiltrate API keys from client applications using the A2A Java SDK's default JDK client.
Affected Products
- A2A Java SDK versions prior to 1.3.0.Final
- A2A Java SDK compat-0.3 module (AuthInterceptor_v0_3)
- Applications using JdkA2AHttpClient with CredentialService-configured API keys
Discovery Timeline
- 2026-10-20 - CVE-2026-111763 published to NVD
- 2026-10-21 - Last updated in NVD database
Technical Details for CVE-2026-111763
Vulnerability Analysis
The vulnerability stems from unsafe handling of remote agent metadata when attaching API key credentials to outbound HTTP requests. When a client application configures credentials through CredentialService, the AuthInterceptor.intercept method in client/transport/spi/src/main/java/org/a2aproject/sdk/client/transport/spi/interceptors/auth/AuthInterceptor.java reads APIKeySecurityScheme.name() from the remote AgentCard and uses that value directly as an HTTP header name. The interceptor does not verify that the declared in location equals HEADER, so an attacker-controlled AgentCard can nominate arbitrary header names.
This logic is compounded by HTTP redirect behavior. JdkA2AHttpClient configures the underlying Java HttpClient with followRedirects(NORMAL), which permits cross-origin redirects. While standard Authorization headers are commonly stripped by HTTP clients during redirects, custom headers added by the interceptor are not, so the credential travels with the request to any destination the malicious agent specifies.
Root Cause
The root cause is missing input validation [CWE-522] on AgentCard-supplied security scheme metadata. The SDK treats the remote agent as a trusted source of header-naming information and fails to apply an allowlist, type check, or redirect-aware header stripping policy.
Attack Vector
Exploitation requires: configured API key credentials for the agent's security scheme, and attacker control over the agent's AgentCard and HTTP redirect response. No additional client privileges are required. The attacker publishes an AgentCard with a crafted APIKeySecurityScheme.name() value, then responds to client requests with a cross-origin redirect to an attacker-controlled server. The client reissues the request to the attacker's endpoint carrying the custom credential header.
import java.util.List;
import java.util.Locale;
import java.util.Map;
+import java.util.Set;
import org.a2aproject.sdk.client.transport.spi.interceptors.ClientCallContext;
import org.a2aproject.sdk.client.transport.spi.interceptors.ClientCallInterceptor;
Source: GitHub Commit 2a36530 — the patch introduces a Set-based allowlist to constrain which headers are forwarded and enforces that the declared security scheme location is HEADER before attaching the credential.
Detection Methods for CVE-2026-111763
Indicators of Compromise
- Outbound HTTP requests from A2A client hosts to unexpected domains carrying non-standard headers whose names mirror attacker-controlled strings.
- HTTP 3xx redirect responses from configured A2A agent endpoints that redirect to external or untrusted origins.
- AgentCard responses containing APIKeySecurityScheme entries with unusual or policy-violating header names.
Detection Strategies
- Instrument the JVM HTTP client with request logging to capture header names applied by AuthInterceptor and cross-reference against expected security scheme values.
- Compare the APIKeySecurityScheme.name() and in fields from retrieved AgentCard objects against a known-good configuration baseline.
- Inspect network telemetry for correlation between A2A agent requests and subsequent cross-origin redirects to domains outside the configured agent list.
Monitoring Recommendations
- Centralize egress logs from hosts running A2A Java SDK workloads and alert on redirect chains ending at untrusted autonomous system numbers (ASNs).
- Track dependency versions of a2a-java across build pipelines and flag any artifact resolving to a version below 1.3.0.Final.
- Monitor outbound TLS SNI from service accounts configured with CredentialService API keys for unexpected destinations.
How to Mitigate CVE-2026-111763
Immediate Actions Required
- Upgrade the A2A Java SDK to version 1.3.0.Final or later across all client applications and build dependencies.
- Rotate any API keys that were configured through CredentialService and used with vulnerable SDK versions.
- Audit configured A2A agent endpoints and remove any whose AgentCards resolve from untrusted sources.
Patch Information
The fix is included in A2A Java SDK release v1.3.0.Final. The code change is tracked in Pull Request #1097 and commit 2a36530. Full context is published in GHSA-4fpj-g9jf-9rgg and GHSA-9rhm-2h4x-jwmx. The patch validates the APIKeySecurityScheme location, restricts header names via an allowlist, and prevents credential-bearing headers from being replayed across redirects.
Workarounds
- Disable automatic redirect following on the underlying HttpClient by replacing followRedirects(NORMAL) with followRedirects(NEVER) where feasible.
- Restrict CredentialService usage to agents whose AgentCards are pinned and verified out of band.
- Deploy an egress proxy that strips non-allowlisted custom headers on cross-origin redirects originating from A2A client workloads.
# Update Maven dependency to the patched version
mvn versions:use-dep-version \
-Dincludes=org.a2aproject:a2a-java-sdk-client \
-DdepVersion=1.3.0.Final \
-DforceVersion=true
Disclaimer: This content was generated using AI. While we strive for accuracy, please verify critical information with official sources.
Sources: National Vulnerability Database, CISA KEV, Exploit-DB

