{"answers":{"affected":"2 open source packages ship an affected version, including org.a2aproject.sdk:a2a-java-sdk-server-common.","exploited":"It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-111764 exists.","fix":"Upgrade org.a2aproject.sdk:a2a-java-sdk-server-common to 1.3.0.Final or later.","what":"CVE-2026-111764 is a high-severity vulnerability in a2aproject a2a-java, published on 20 Oct 2026."},"fix_prompt":"Check this codebase for CVE-2026-111764 and fix it if it is affected.\n\nWhat it is: CVE-2026-111764 is a high-severity vulnerability in a2aproject a2a-java, published on 20 Oct 2026. \nExploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-111764 exists.\n\nAffected packages and fixed versions:\n- org.a2aproject.sdk:a2a-java-sdk-server-common (Maven): affected all versions; fixed in 1.3.0.Final\n- org.a2aproject.sdk:a2a-java-sdk-server-common (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-111764/ (Markdown: https://insights.sbomify.com/CVE-2026-111764/index.md)","id":"CVE-2026-111764","markdown":"https://insights.sbomify.com/CVE-2026-111764/index.md","name":"CVE-2026-111764","record":{"aliases":["GHSA-qw47-mcm5-934w"],"analysis":null,"analysis_generated_by":null,"assigner":"GitHub_M","cpe":[],"cvss":{"score":7.5,"severity":"high","source":"cna","vector":"CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N","version":"3.1"},"cwes":[{"id":"CWE-862","name":"Missing Authorization"},{"id":"CWE-1188","name":"Initialization of a Resource with an Insecure Default"}],"description":"A2A Java SDK is the official Java SDK for the Agent2Agent (A2A) Protocol. Prior to 1.3.0.Final, the default InMemoryTaskStore configuration performs no authorization on task reads: the no-argument constructor sets authorizationProvider to null, and InMemoryTaskStore.get(String taskId) returns the stored task without checking the caller or owner. Authorization depends on supplying a TaskAuthorizationProvider and routing requests through AuthorizationRequestHandlerDecorator, whether installed through CDI or explicitly by the application. Default store wiring and manually constructed DefaultRequestHandler.builder().build() handlers, including integrations such as Spring, leave task reads unprotected when no effective authorization-provider and decorator check is installed. In a multi-caller deployment using the default configuration, a caller who knows or guesses another caller's task ID can retrieve the task status, context ID, message history, and artifacts. The default/reference transport endpoints do not enforce authentication, so the task-read disclosure is reachable by an unauthenticated caller rather than requiring a privileged account. 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":"weaponised"},"has_fix":true,"headline":"A2A Java SDK has a fail-open default task authorization","id":"CVE-2026-111764","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":"Maven","product":null,"products":[],"type":null,"year":"2026"},"n_packages":2,"n_references":4,"next":{"headline":"A2A Java SDK: Android synchronous POST forwards credentials across authorities after incomplete redirect fix","id":"CVE-2026-111765"},"packages":[{"ecosystem":"Maven","fixed":["1.3.0.Final"],"introduced":["0"],"last_affected":[],"package":"org.a2aproject.sdk:a2a-java-sdk-server-common","purl":null,"source":"GHSA-qw47-mcm5-934w"},{"ecosystem":"Maven","fixed":["1.3.0.Final"],"introduced":["0"],"last_affected":[],"package":"org.a2aproject.sdk:a2a-java-sdk-server-common","purl":"pkg:maven/org.a2aproject.sdk/a2a-java-sdk-server-common","source":"GHSA-qw47-mcm5-934w"}],"prev":{"headline":"A2A Java SDK send client credentials under server-controlled HTTP header name, enabling leakage via redirect","id":"CVE-2026-111763"},"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":"yes","exploitation":"poc","technical_impact":"partial"},"state":"PUBLISHED","updated":"2026-10-20","vendors":["a2aproject"]},"summary":null,"url":"https://insights.sbomify.com/CVE-2026-111764/"}