{"answers":{"affected":"2 open source packages ship an affected version, including org.a2aproject.sdk:a2a-java-sdk-transport-rest.","exploited":"There is no known exploitation of CVE-2026-111762 in the wild and no public exploit code.","fix":"Upgrade org.a2aproject.sdk:a2a-java-sdk-transport-rest to 1.3.0.Final or later.","what":"CVE-2026-111762 is a medium-severity vulnerability in a2aproject a2a-java, published on 20 Oct 2026."},"fix_prompt":"Check this codebase for CVE-2026-111762 and fix it if it is affected.\n\nWhat it is: CVE-2026-111762 is a medium-severity vulnerability in a2aproject a2a-java, published on 20 Oct 2026. \nExploitation: There is no known exploitation of CVE-2026-111762 in the wild and no public exploit code.\n\nAffected packages and fixed versions:\n- org.a2aproject.sdk:a2a-java-sdk-transport-rest (Maven): affected all versions; fixed in 1.3.0.Final\n- org.a2aproject.sdk:a2a-java-sdk-transport-rest (Maven): affected all versions; fixed in 1.3.0.Final\n\nTask:\n1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.\n2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.\n3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.\n4. Run the tests and summarise what changed and why.\n5. If nothing in the project is affected, say so and change nothing.\n\nReference: https://insights.sbomify.com/CVE-2026-111762/ (Markdown: https://insights.sbomify.com/CVE-2026-111762/index.md)","id":"CVE-2026-111762","markdown":"https://insights.sbomify.com/CVE-2026-111762/index.md","name":"CVE-2026-111762","record":{"aliases":["GHSA-x32g-jvvm-4725"],"analysis":null,"analysis_generated_by":null,"assigner":"GitHub_M","cpe":[],"cvss":{"score":5.7,"severity":"medium","source":"cna","vector":"CVSS:4.0/AV:L/AC:L/AT:P/PR:L/UI:N/VC:H/VI:N/VA:N/SC:N/SI:N/SA:N","version":"4.0"},"cwes":[{"id":"CWE-532","name":"Insertion of Sensitive Information into Log File"}],"description":"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.","ecosystems":["Maven"],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"none_known"},"has_fix":true,"headline":"A2A Java SDK: Push notification credentials logged in cleartext on protobuf parse failure","id":"CVE-2026-111762","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":"Maven","product":null,"products":[],"type":null,"year":"2026"},"n_packages":2,"n_references":3,"next":{"headline":"A2A Java SDK send client credentials under server-controlled HTTP header name, enabling leakage via redirect","id":"CVE-2026-111763"},"packages":[{"ecosystem":"Maven","fixed":["1.3.0.Final"],"introduced":["0"],"last_affected":[],"package":"org.a2aproject.sdk:a2a-java-sdk-transport-rest","purl":null,"source":"GHSA-x32g-jvvm-4725"},{"ecosystem":"Maven","fixed":["1.3.0.Final"],"introduced":["0"],"last_affected":[],"package":"org.a2aproject.sdk:a2a-java-sdk-transport-rest","purl":"pkg:maven/org.a2aproject.sdk/a2a-java-sdk-transport-rest","source":"GHSA-x32g-jvvm-4725"}],"prev":{"headline":"A2A Java SDK has Server-Side Request Forgery (SSRF) in push-notification delivery","id":"CVE-2026-111761"},"products":["a2a-java"],"published":"2026-10-20","related":[],"sources":[{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"},{"class":"attribution","licence":"CC BY 4.0","name":"GitHub Advisory Database","prefix":"GHSA"},{"class":"attribution","licence":"CWE Terms of Use","name":"CWE (MITRE)"},{"class":"attribution","licence":"FIRST CVSS licence","name":"CVSS (FIRST)"}],"ssvc":{"automatable":"no","exploitation":"none","technical_impact":"partial"},"state":"PUBLISHED","updated":"2026-10-28","vendors":["a2aproject"]},"summary":null,"url":"https://insights.sbomify.com/CVE-2026-111762/"}