A2A Java SDK has Server-Side Request Forgery (SSRF) in push-notification delivery
CVE-2026-111761GHSA-q78c-5jjq-57g8
What to do
Vendor fix available. Upgrade each affected package to the fixed version on its release line (org.a2aproject.sdk:a2a-java-sdk-server-common 1.3.0.Final), redeploy, then verify what is actually installed.
This page has no inventory attached, so it cannot say whether you are affected. A vendor fix is not proof that your deployment is fixed.
Affected packages
Maven org.a2aproject.sdk:a2a-java-sdk-server-common
- Affected
- < 1.3.0.Final
- Fixed in
- 1.3.0.Final
Sources
- Open Source Vulnerabilities (OSV.dev), including the GitHub Advisory Database
OSV record GHSA-q78c-5jjq-57g8 lists affected ranges: Maven org.a2aproject.sdk:a2a-java-sdk-server-common >=0 <1.3.0.Final (fixed)
VerifiedObserved Structured OSV record; GitHub-reviewed advisory.
- GitHub Advisory Database and maintainer security advisories on GitHub
GitHub-reviewed advisory GHSA-q78c-5jjq-57g8 lists affected ranges: Maven org.a2aproject.sdk:a2a-java-sdk-server-common >=0 <1.3.0.Final
VerifiedObserved Structured GitHub Advisory Database record (type=reviewed) from the GitHub REST API.
Severity and exploitation
- Exploitation
- No confirmed exploitation recorded. Patch Next marks exploitation only from CISA KEV.
- CVSS
- 5.8 · CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:N/I:L/A:N
- EPSS
- CVE-2026-111761: 0.59% estimated exploitation activity in the next 30 days; percentile 48.05 (FIRST EPSS, 2026-11-03). This is a model estimate, not proof of exploitation or customer exposure.
Source description
As published by the source; long descriptions are shortened.
--- - Ecosystem: Maven - Affected package: org.a2aproject.sdk:a2a-java-sdk-server-common (push-notification delivery) - Affected versions: <= 1.2.0.Final (and 1.2.1.Final-SNAPSHOT on main prior to the fix) - Patched version: (the release that carries the fix) - CWE: CWE-918 (Server-Side Request Forgery) - Severity: High - CVSS v3.1: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:N/I:L/A:N (5.8, Moderate) --- Summary An unauthenticated attacker can coerce the a2a-java server into issuing HTTP requests to arbitrary internal and cloud-metadata endpoints from the server's own network position — a Server-Side Request Forgery reachable in the default deployment with no credentials, no user interaction, and a single request. The behaviour is the shipped default, not a misconfiguration. Details BasePushNotificationSender (in server-common) POSTs task data to the URL stored on a task's TaskPushNotificationConfig with no validation of the destination: no block on loopback, RFC1918, link-local…
Dates and revisions
- Published by the source
- Last modified by the source
- Source last checked
- Revision 2 · amended ·
Amended from ghsa record GHSA-q78c-5jjq-57g8
- Revision 1 · created ·
Published from osv record GHSA-q78c-5jjq-57g8
Agent brief
Preview the exact text before you copy it. Commands are read-only suggestions; review them before running anything.
# Patch Next advisory brief: CVE-2026-111761 Advisory: A2A Java SDK has Server-Side Request Forgery (SSRF) in push-notification delivery IDs: CVE-2026-111761, GHSA-q78c-5jjq-57g8 Record: https://patchnext.com/advisories/cve-2026-111761 (revision 2, source checked 26 Oct 2026, 16:58 UTC) Inventory: none attached. This brief comes from a public page and does not say whether any deployment is affected. Severity: Medium (CVSS 5.8) Exploitation: no confirmed exploitation recorded. Patch Next confirms exploitation only from CISA KEV. Vendor response: Vendor fix available; fixed versions by package: org.a2aproject.sdk:a2a-java-sdk-server-common 1.3.0.Final. A vendor fix does not mean a deployment is fixed. ## Affected components - Maven org.a2aproject.sdk:a2a-java-sdk-server-common: affected < 1.3.0.Final; fixed in 1.3.0.Final ## Suggested inspection (read-only) - Maven org.a2aproject.sdk:a2a-java-sdk-server-common: check the installed version with your package manager. ## Supported action Upgrade each affected component to a fixed version on its release line. For a transitive dependency, upgrade the parent package or add an override or constraint, then regenerate the lockfile. Redeploy every environment that ran an affected version. ## Required regression checks - Run the test suite and a production build. - Exercise the features that depend on org.a2aproject.sdk:a2a-java-sdk-server-common. - Repeat the inspection and confirm that only fixed versions remain installed. ## Rollback considerations - Keep the previous lockfile and deployment artifact. Rolling back reinstates the vulnerable version, so apply any documented mitigation while you fix forward. ## Unresolved questions - Which deployments run an affected version? - Exploitation status can change. Check again before lowering the priority. - Mark the work resolved only after the fixed version is verified in production. ## Sources - Verified: https://osv.dev/vulnerability/GHSA-q78c-5jjq-57g8 (OSV record GHSA-q78c-5jjq-57g8 lists affected ranges: Maven org.a2aproject.sdk:a2a-java-sdk-server-common >=0 <1.3.0.Final (fixed)) - Verified: https://github.com/advisories/GHSA-q78c-5jjq-57g8 (GitHub-reviewed advisory GHSA-q78c-5jjq-57g8 lists affected ranges: Maven org.a2aproject.sdk:a2a-java-sdk-server-common >=0 <1.3.0.Final) Commands are suggestions: review each one before running it.
Loading voting…