CVE-2026-111762: A2A Java SDK: Push notification credentials logged in cleartext on protobuf parse failure
Impact. Push notification bearer tokens and authentication credentials submitted by clients are written to server log files in cleartext. Any operator, log aggregation system, or attacker with log access can read these secrets and use them to authenticate to the client's push notification endpoints, potentially sending forged task status updates.
Where. transport/rest/src/main/java/org/a2aproject/sdk/transport/rest/handler/RestHandler.java:676 in parseRequestBody
What. The parseRequestBody method logs the entire JSON request body at SEVERE level when JsonFormat.parser().merge() throws InvalidProtocolBufferException. This method is called from createTaskPushNotificationConfiguration (line 377), where the body contains client-supplied push notification bearer tokens (field token) and authentication credentials (field authentication.credentials). These secrets are written to server log files in full.
Exploit scenario. A client creates a push notification configuration by POSTing to /v1/tenants/{tenant}/tasks/{taskId}/pushNotificationConfigs with a body containing {"url": "https://client.example.com/webhook", "token": "secret-bearer-token", "authentication": {"scheme": "Bearer", "credentials": "oauth-access-token"}, "extraField": "value"}. The extra field causes JsonFormat.parser().merge() to throw InvalidProtocolBufferException. The entire body including secret-bearer-token and oauth-access-token is logged at SEVERE level. An attacker with log access retrieves the cleartext credentials.
Preconditions. - Attacker must have access to server log files (centralized logging, log aggregation, shared infrastructure, or insider access) - Push notification capability must be enabled - A request body must fail protobuf deserialization while being valid JSON (unknown fields with strict parsing, schema mismatches)
Fix. Do not log the raw request body. Log only a sanitized summary — body length and content type, not content. Replace the log call with something like: log.log(Level.SEVERE, "Error parsing JSON request body (length={0})", body != null ? body.length() : 0).
Verification. 3/3 lens verifiers confirmed.
Other sources
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.
— MITRE
Affected Software
Remediation
Recommended actions to resolve this vulnerability, in priority order.
- Upgrade
Upgrade
maven/org.a2aproject.sdk:a2a-java-sdk-transport-restto a version that resolves this vulnerability.Fixed in 1.3.0.Final - Upgrade
Upgrade
A2A Java SDKto a version that resolves this vulnerability.Fixed in 1.3.0.Final