CVE-2026-111764
HIGHDescription
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.
How to fix
No published remediation has been found for this vulnerability's affected products yet.
Mitigation guidance may be in the linked vendor advisories in the References section below.
TridentStack Control tracks known vulnerabilities across your Windows, macOS, and Linux fleet and shows the fix as soon as one is published. See how it works
CVSS v3 Vector
Exploitability
Impact
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N
Exploit Intelligence
Moderate risk: more likely to be exploited than 48% of all known CVEs.
References
Related Vulnerabilities
Other CWE-862 (Missing Authorization) vulnerabilities, ordered by exploit likelihood. View all
| CVE | Severity | CVSS | EPSS | Exploited | Fix |
|---|---|---|---|---|---|
| CVE-2021-39226 | Critical | 9.8 | 100% | KEV | Fix |
| CVE-2022-0543 | Critical | 10.0 | 99% | KEV | Fix |
| CVE-2021-21978 | Critical | 9.8 | 99% | - | Fix |
| CVE-2023-52163 | High | 8.8 | 97% | KEV | - |
| CVE-2022-1329 | High | 8.8 | 93% | - | - |
| CVE-2023-6875 | Critical | 9.8 | 90% | - | - |
Common questions
How do I fix CVE-2026-111764?
No published fix for CVE-2026-111764 has been found yet. Check the linked vendor advisories for guidance as it becomes available.
Is CVE-2026-111764 being actively exploited?
Not that we know of. CVE-2026-111764 is not in the CISA Known Exploited Vulnerabilities catalog. Its EPSS score of 0.60% is the estimated probability that it will be exploited in the next 30 days. That is higher than 48% of all scored CVEs.
How severe is CVE-2026-111764?
CVE-2026-111764 has a CVSS v3 base score of 7.5, rated high. CVSS rates the technical impact if the vulnerability is exploited, not how likely that is, so weigh it alongside the exploit-prediction score when you decide what to patch first.
Embed a live status badge for CVE-2026-111764
Markdown
[](https://tridentstack.com/cve/CVE-2026-111764)HTML
<a href="https://tridentstack.com/cve/CVE-2026-111764"><img src="https://tridentstack.com/cve/badge/CVE-2026-111764.svg" alt="CVE-2026-111764"></a>Find and fix vulnerabilities across your fleet
TridentStack Control continuously scans your Windows, macOS, and Linux fleet for known vulnerabilities, prioritizes them by severity and active exploitation, and patches them automatically.
This product uses NVD data but is not endorsed or certified by the NVD. EPSS scores courtesy of FIRST.org (https://www.first.org/epss). Source: CISA KEV Catalog. Data as of 2026-10-20.