{"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-111761 exists.","fix":"Upgrade org.a2aproject.sdk:a2a-java-sdk-server-common to 1.3.0.Final or later.","what":"CVE-2026-111761 is a medium-severity vulnerability in a2aproject a2a-java, published on 20 Oct 2026."},"fix_prompt":"Check this codebase for CVE-2026-111761 and fix it if it is affected.\n\nWhat it is: CVE-2026-111761 is a medium-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-111761 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-111761/ (Markdown: https://insights.sbomify.com/CVE-2026-111761/index.md)","id":"CVE-2026-111761","markdown":"https://insights.sbomify.com/CVE-2026-111761/index.md","name":"CVE-2026-111761","record":{"aliases":["GHSA-q78c-5jjq-57g8"],"analysis":null,"analysis_generated_by":null,"assigner":"GitHub_M","cpe":[],"cvss":{"score":5.8,"severity":"medium","source":"cna","vector":"CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:N/I:L/A:N","version":"3.1"},"cwes":[{"id":"CWE-918","name":"Server-Side Request Forgery"}],"description":"A2A Java SDK is the official Java SDK for the Agent2Agent (A2A) Protocol. Prior to 1.3.0.Final, BasePushNotificationSender in server-common sends task data to the URL in TaskPushNotificationConfig without destination validation, scheme restrictions, or bounds on redirects. InMemoryPushNotificationConfigStore.setInfo stores the URL verbatim, and onCreateTaskPushNotificationConfig does not validate the destination. In the default deployment with push notifications enabled, an unauthenticated caller can register a destination through an inline SendMessage configuration or CreateTaskPushNotificationConfig for an existing task, causing task status and artifact updates to send requests from the server's network position to loopback, private, link-local cloud-metadata, IPv6 unique-local, unspecified, or multicast destinations where routing permits. JdkA2AHttpClient and VertxA2AHttpClient follow redirects, allowing a webhook redirect to bypass creation-time destination checks and convert a POST into a GET; hostname-only checks also do not prevent DNS rebinding. Direct POST delivery can push attacker-influenced task data into internal services, whereas a redirected POST-to-GET request drops the body. The sender discards the fetched response and does not expose delivery success or failure, so the demonstrated behavior does not provide response read-back. No credentials or user interaction are required. 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 Server-Side Request Forgery (SSRF) in push-notification delivery","id":"CVE-2026-111761","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: Push notification credentials logged in cleartext on protobuf parse failure","id":"CVE-2026-111762"},"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-q78c-5jjq-57g8"},{"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-q78c-5jjq-57g8"}],"prev":{"headline":"markdown-it: Quadratic complexity in smartquotes with unmatched closing quotes","id":"CVE-2026-111759"},"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-22","vendors":["a2aproject"]},"summary":null,"url":"https://insights.sbomify.com/CVE-2026-111761/"}