Medium, CVSS 5.7MavenAmendedPublished
A2A Java SDK: Push notification credentials logged in cleartext on protobuf parse failure
CVE-2026-111762 · GHSA-x32g-jvvm-4725
- Affected
- Maven org.a2aproject.sdk:a2a-java-sdk-transport-rest < 1.3.0.Final
- Fixed in
- 1.3.0.Final· Vendor fix available
- Issue
- 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…
Recommended action: Upgrade to 1.3.0.Final or later, then redeploy and verify.A vendor fix does not resolve your finding until you verify it in your own systems.