# CVE-2026-111765: A2A Java SDK: Android synchronous POST forwards credentials across authorities after incomplete redirect fix


- **Severity:** High 7.5 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N`)
- **Exploited in the wild:** Not known
- **Fix available:** Yes
- **Published:** 20 Oct 2026
- **Updated:** 22 Oct 2026
- **Also known as:** GHSA-4fpj-g9jf-9rgg

## What is CVE-2026-111765?

CVE-2026-111765 is a high-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. 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.

Weakness: CWE-522 (Insufficiently Protected Credentials)

## Which versions are affected by CVE-2026-111765?

2 open source packages ship an affected version, including org.a2aproject.sdk:a2a-java-sdk-http-client-android.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `org.a2aproject.sdk:a2a-java-sdk-http-client-android` | Maven | From 1.3.0.Final | 1.3.2.Final |
| `org.a2aproject.sdk:a2a-java-sdk-http-client-android` | Maven | From 1.3.0.Final | 1.3.2.Final |

## How do I fix CVE-2026-111765?

Upgrade org.a2aproject.sdk:a2a-java-sdk-http-client-android to 1.3.2.Final or later.

## Is CVE-2026-111765 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-111765 exists.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-111765 and fix it if it is affected.

What it is: CVE-2026-111765 is a high-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-111765 exists.

Affected packages and fixed versions:
- org.a2aproject.sdk:a2a-java-sdk-http-client-android (Maven): affected from 1.3.0.Final; fixed in 1.3.2.Final
- org.a2aproject.sdk:a2a-java-sdk-http-client-android (Maven): affected from 1.3.0.Final; fixed in 1.3.2.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-111765/ (Markdown: https://insights.sbomify.com/CVE-2026-111765/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-111765
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-111765
- OSV: https://osv.dev/vulnerability/CVE-2026-111765

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-111765/
Summaries are generated and may contain mistakes; the official description above is the record.