CVE-2026-111765
HIGHDescription
A2A Java SDK is the official Java SDK for the Agent2Agent (A2A) Protocol. Starting in version 1.3.0.Final and prior to version 1.3.2.Final, the AndroidA2AHttpClient synchronous POST path overrides the disabled-redirect setting in AndroidA2AHttpClient.createConnection() with the PostBuilder default followRedirects value of true, leaving a residual of the earlier credential-redirect fix. JSONRPCTransport and RestTransport add interceptor-produced authentication headers and call synchronous post() without disabling redirects. AuthInterceptor permits X-API-Key, API-Key, X-Auth-Token, and X-Authentication headers; Android's repackaged OkHttp strips Authorization on cross-authority redirects but retains these nonstandard headers, disclosing a complete configured API key or token to another authority. The additional exposure applies when redirect or front-door behavior is compromised separately from the credential-handling component, or those components operate in different trust domains; a completely malicious initial origin already receives the credential on the first request. Autonomous clients require no human action, while user-invoked workflows can require interaction. Explicit followRedirects(false) prevents the redirected request. The demonstrated impact is credential disclosure, not subsequent credential use, integrity or availability impact, code execution, or host compromise. This issue is fixed in version 1.3.2.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 52% of all known CVEs.
References
Related Vulnerabilities
Other CWE-522 vulnerabilities, ordered by exploit likelihood. View all
| CVE | Severity | CVSS | EPSS | Exploited | Fix |
|---|---|---|---|---|---|
| CVE-2019-17662 | Critical | 9.8 | 97% | - | - |
| CVE-2020-29583 | Critical | 9.8 | 90% | KEV | - |
| CVE-2021-30116 | Critical | 10.0 | 86% | KEV + Ransom | Fix |
| CVE-2024-44000 | Critical | 9.8 | 82% | - | Fix |
| CVE-2018-9160 | Critical | 9.8 | 76% | - | - |
| CVE-2017-9248 | Critical | 9.8 | 75% | KEV | Fix |
Common questions
How do I fix CVE-2026-111765?
No published fix for CVE-2026-111765 has been found yet. Check the linked vendor advisories for guidance as it becomes available.
Is CVE-2026-111765 being actively exploited?
Not that we know of. CVE-2026-111765 is not in the CISA Known Exploited Vulnerabilities catalog. Its EPSS score of 0.68% is the estimated probability that it will be exploited in the next 30 days. That is higher than 52% of all scored CVEs.
How severe is CVE-2026-111765?
CVE-2026-111765 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-111765
Markdown
[](https://tridentstack.com/cve/CVE-2026-111765)HTML
<a href="https://tridentstack.com/cve/CVE-2026-111765"><img src="https://tridentstack.com/cve/badge/CVE-2026-111765.svg" alt="CVE-2026-111765"></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-22.