Security fix · CVE-2026-111762
A2A Java SDK is the official Java SDK for the Agent2Agent (A2A) Protocol.
Published Oct 20, 2026 · catalog updated Oct 20, 2026 · A2A Java SDK is
Last checked Nov 4, 2026. A connected source was read within the last 7 days.
Check if you run it
No confirmed exploitation is on record for CVE-2026-111762. EPSS is 0.17%. Act only if a listed version of A2A Java SDK is is installed.
Gaps on this record
- The stored product name is a package slug. The name on this page is taken from the title (A2A Java SDK is).
- No vendor fix or required action is stored. Compare the linked advisory before you change production.
- Severity
- Medium5.7
- Known exploitation
- Not in CISA/VulnCheck KEV
- EPSS
- 0.17%
- Remediation
- Version ranges on file
- Affected products
- Maven org.a2aproject.sdk:a2a-java-sdk-transport-rest · maven org.a2aproject.sdk:a2a-java-sdk-transport-rest
### *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.** in **What.** The method logs the entire JSON request body at level when throws . This method is called from (line 377), where the body contains client-supplied push notification bearer tokens (field ) and authentication credentials (field ). These secrets are written to server log files in full. **Exploit scenario.** A client creates a push notification configuration by POSTing to with a body containing . The extra field causes to throw . The entire body including and 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: . **Verification.** 3/3 lens verifiers confirmed.
Are you affected?
Enter the version you run. The result uses only the ranges stored on this record.
The check returns affected, not affected, or incomplete. It does not guess a version that is missing from the record.
- Maven org.a2aproject.sdk:a2a-java-sdk-transport-rest0 → 1.3.0.Final
- maven org.a2aproject.sdk:a2a-java-sdk-transport-rest< 1.3.0.Final
How to fix CVE-2026-111762
Upgrade
CVE-2026-111762 lists a fix boundary at 1.3.0.Final. Compare the installed build with that boundary before you change production.
Version check
Affected < 1.3.0.Final
Advisory
Open the cve_org record and follow its fix.
Official advisories
What to do
Three questions, each answered from this record only. Confirm the vendor advisory before you patch.
Should you patch?
No confirmed exploitation is on record for CVE-2026-111762. EPSS is 0.17%. Act only if a listed version of A2A Java SDK is is installed.
Which versions are affected?
Compare what you have installed with 0 → 1.3.0.Final, < 1.3.0.Final. Compare the installed version with the linked vendor advisory before you change production.
What should an analyst verify?
CWE-532: Insertion of Sensitive Information into Log File. EPSS 0.17%. There is no CISA KEV listing. No Exploit-DB or Metasploit reference is linked. Use the source links for the original advisory.
Code
The project this record applies to. Exploit listings stay in References.
Timeline
Detection, updates, and resolution for this record.
Oct 20, 2026 · NIST NVD
Detected
A2A Java SDK is the official Java SDK for the Agent2Agent (A2A) Protocol. Prior to 1.3.0.Final, RestHandler.parseRequestBody in 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 , whose token and authentication.credenti
Oct 20, 2026 · NIST NVD
Updated
A2A Java SDK is the official Java SDK for the Agent2Agent (A2A) Protocol. Prior to 1.3.0.Final, RestHandler.parseRequestBody in 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 , whose token and authentication.credenti
Oct 20, 2026 · GitHub Advisory Database
Fix available
org.a2aproject.sdk:a2a-java-sdk-transport-rest fixed in 1.3.0.Final
Oct 20, 2026 · GitHub Advisory Database
Fix available
org.a2aproject.sdk:a2a-java-sdk-transport-rest fixed in 1.3.0.Final
Oct 20, 2026 · GitHub Advisory Database
Updated
### *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.** in **What.** The method logs the
Sources
- CVE.orgVulnerability recordCVE-2026-111762
Official CVE identifier
cve.org - FIRST EPSSExploitation probabilityCVE-2026-111762
30-day exploitation probability 0.17%
first.org - GitHub Advisory DatabasePackage advisoryGHSA-x32g-jvvm-4725
GitHub Advisory Database record mirrored by OSV.
github.com - NIST NVDVulnerability recordCVE-2026-111762
A2A Java SDK is the official Java SDK for the Agent2Agent (A2A) Protocol. Prior to 1.3.0.Final, RestHandler.parseRequestBody in logs the entire JSON request body at SEVERE level when JsonFor
nvd.nist.gov - OpenSSF OSV / OSV ScannerPackage advisoryGHSA-x32g-jvvm-4725
A2A Java SDK: Push notification credentials logged in cleartext on protobuf parse failure
osv.dev
References
Freshness
Last verified in this catalog Nov 4, 2026. Significant claims (KEV, EPSS, CVSS, affected ranges) come from the source rows above — open the original publisher for the authoritative advisory.
- GitHub Advisory DatabaseOct 23, 2026
- OpenSSF OSV / OSV ScannerOct 23, 2026
- FIRST EPSSOct 23, 2026
- CVE.orgOct 21, 2026
- NIST NVDOct 21, 2026