A2A Java SDK vulnerabilities

A2A Java SDK from 1.3.0.Final before 1.3.2.Final: the AndroidA2AHttpClient synchronous POST path overrides the disabled-redirect setting with PostBuilder's followRedirects=true. JSONRPCTransport and RestTransport add interceptor-produced authentication headers and call synchronous post() without disabling redirects, disclosing a configured API key or token to another authority on redirect.

A2A Java SDK prior to 1.3.0.Final: the default InMemoryTaskStore configuration performs no authorization on task reads. The no-argument constructor sets authorizationProvider to null, and get(String taskId) returns the stored task without checking caller or owner. In a multi-caller deployment, a caller who knows another caller's task ID can retrieve task status, context ID, message history, and artifacts; default transport endpoints do not enforce authentication.

A2A Java SDK prior to 1.3.0.Final allows a malicious or compromised remote agent to cause the default JDK-based client to forward a configured API key to a third-party server. AuthInterceptor uses APIKeySecurityScheme.name() from the remote AgentCard as the HTTP header name without checking that the declared location is HEADER, and JdkA2AHttpClient uses followRedirects(NORMAL), so an agent-controlled cross-origin redirect forwards the credential-bearing header.

A2A Java SDK before 1.3.0.Final has a vulnerability in RestHandler.parseRequestBody that logs the entire JSON request body at SEVERE level when protobuf parsing fails. With push notifications enabled, this can expose tokens and authentication credentials in server logs.

A2A Java SDK before 1.3.0.Final has a vulnerability in BasePushNotificationSender that sends task data to a URL without destination validation, scheme restrictions, or redirect limits. An unauthenticated attacker can register an arbitrary destination, causing the server to send requests to internal or local resources.