CVE-2026-111762
MediumCVSS 5.7Summary
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.
Risk Assessment
An attacker with access to logs could obtain sensitive credentials and use them to send forged task status updates to the client's push notification endpoint.
Recommendation
Update A2A Java SDK to version 1.3.0.Final or later.
Other vulnerabilities in A2A Java SDK
See all- CVE-2026-111765High
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.
- CVE-2026-111764High
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.
- CVE-2026-111763Medium
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.
- CVE-2026-111761Medium
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.
Original NVD description (English source)
A2A Java SDK is the official Java SDK for the Agent2Agent (A2A) Protocol. Prior to 1.3.0.Final, RestHandler.parseRequestBody in `transport/rest/src/main/java/org/a2aproject/sdk/transport/rest/handler/RestHandler.java` logs the entire JSON request body at SEVERE level when JsonFormat.parser().merge() throws InvalidProtocolBufferException. With push notifications enabled, createTaskPushNotificationConfiguration reaches this parser for requests to `/v1/tenants/{tenant}/tasks/{taskId}/pushNotificationConfigs`, whose token and authentication.credentials fields can contain bearer tokens and authentication credentials for client push endpoints. A valid JSON body that fails protobuf deserialization, including an unknown field under strict parsing or a schema mismatch, causes those secrets to be written to the server logs in cleartext. An attacker with access to the server logs or a log aggregation system can retrieve the credentials and potentially use the credentials to send forged task status updates to the client's push notification endpoint. This issue is fixed in version 1.3.0.Final.
Vulnerability data from NVD (NIST) · CISA KEV · EPSS