# CVE-2026-111761: A2A Java SDK has Server-Side Request Forgery (SSRF) in push-notification delivery - **Severity:** Medium 5.8 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:N/I:L/A:N`) - **Exploited in the wild:** Not known - **Fix available:** Yes - **Published:** 20 Oct 2026 - **Updated:** 22 Oct 2026 - **Also known as:** GHSA-q78c-5jjq-57g8 ## What is CVE-2026-111761? CVE-2026-111761 is a medium-severity vulnerability in a2aproject a2a-java, published on 20 Oct 2026. ### Official 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. Weakness: CWE-918 (Server-Side Request Forgery) ## Which versions are affected by CVE-2026-111761? 2 open source packages ship an affected version, including org.a2aproject.sdk:a2a-java-sdk-server-common. | Package | Ecosystem | Affected | Fixed in | | --- | --- | --- | --- | | `org.a2aproject.sdk:a2a-java-sdk-server-common` | Maven | All versions | 1.3.0.Final | | `org.a2aproject.sdk:a2a-java-sdk-server-common` | Maven | All versions | 1.3.0.Final | ## How do I fix CVE-2026-111761? Upgrade org.a2aproject.sdk:a2a-java-sdk-server-common to 1.3.0.Final or later. ## Is CVE-2026-111761 being exploited? It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-111761 exists. ## Fix prompt for AI coding agents ```text Check this codebase for CVE-2026-111761 and fix it if it is affected. What it is: CVE-2026-111761 is a medium-severity vulnerability in a2aproject a2a-java, published on 20 Oct 2026. Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-111761 exists. Affected packages and fixed versions: - org.a2aproject.sdk:a2a-java-sdk-server-common (Maven): affected all versions; fixed in 1.3.0.Final - org.a2aproject.sdk:a2a-java-sdk-server-common (Maven): affected all versions; fixed in 1.3.0.Final Task: 1. 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. 2. 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. 3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead. 4. Run the tests and summarise what changed and why. 5. If nothing in the project is affected, say so and change nothing. Reference: https://insights.sbomify.com/CVE-2026-111761/ (Markdown: https://insights.sbomify.com/CVE-2026-111761/index.md) ``` ## Sources - CVE record: https://www.cve.org/CVERecord?id=CVE-2026-111761 - NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-111761 - OSV: https://osv.dev/vulnerability/CVE-2026-111761 --- From sbomify Insights: https://insights.sbomify.com/CVE-2026-111761/ Summaries are generated and may contain mistakes; the official description above is the record.