Advisory Database
  • Advisories
  • Dependency Scanning
  1. maven
  2. ›
  3. org.a2aproject.sdk/a2a-java-sdk-transport-rest
  4. ›
  5. CVE-2026-111762

CVE-2026-111762: A2A Java SDK: Push notification credentials logged in cleartext on protobuf parse failure

October 20, 2026

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.

References

  • github.com/a2aproject/a2a-java/commit/88827105fee0daaac0d883a4a68eb644571d7230
  • github.com/a2aproject/a2a-java/releases/tag/v1.3.0.Final
  • github.com/a2aproject/a2a-java/security/advisories/GHSA-x32g-jvvm-4725
  • github.com/advisories/GHSA-x32g-jvvm-4725
  • nvd.nist.gov/vuln/detail/CVE-2026-111762

Code Behaviors & Features

Detect and mitigate CVE-2026-111762 with GitLab Dependency Scanning

Secure your software supply chain by verifying that all open source dependencies used in your projects contain no disclosed vulnerabilities. Dependency Scanning using SBOM also detects vulnerabilities from proprietary advisories that this site does not include. Learn more about Dependency Scanning using SBOM →

Affected versions

All versions before 1.3.0

Fixed versions

  • 1.3.0

Solution

Upgrade to version 1.3.0 or above.

Impact 5.5 MEDIUM

CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N

Learn more about CVSS

Weakness

  • CWE-532: Insertion of Sensitive Information into Log File

Source file

maven/org.a2aproject.sdk/a2a-java-sdk-transport-rest/CVE-2026-111762.yml

Spotted a mistake? Edit the file on GitLab.

  • Site Repo
  • About GitLab
  • Terms
  • Privacy Statement
  • Contact

Page generated Sun, 08 Nov 2026 00:16:10 +0000.