CVE-2026-130626
A2A Java JDK redirects could disclose custom API-key headers
a2a-java · A2A Java SDK JDK HTTP client
First documented disclosure · Review checkpoint
Summary
Some authenticated requests could follow an agent’s redirect and disclose custom credential headers.
Severity and exploitation evidence
High · 7.5/10 · CVSS 3.1. Severity source.
Exploitation not established: Malicious exploitation status remains unverified in the reviewed sources.
Technical severity is not a measure of observed attacks or of risk to your deployment. Attempts, demonstrations, and successful compromise retain the qualifications in the source.
How the weakness works
GET, DELETE and streaming paths bypassed the redirect hardening applied to POST requests.
Conditions required
The application supplies a JDK client configured to follow redirects and sends a custom credential header.
Potential impact
Custom API keys can be forwarded to another host selected by a redirect.
Affected versions and configurations
1.3.0.Final through 1.4.0.Final.
Fix and mitigation status
1.5.0.Final.
Practical next steps
Upgrade to 1.5.0.Final or later. Until upgraded, supply a JDK client with redirects disabled.
Operating lesson
Apply credential-stripping rules to every transport method.
Evidence and limits
Original disclosure 2026-11-09. The CVE Program published this record 2026-11-17. The CNA identifies an incomplete earlier redirect fix. The exposed data in this variant is custom credential headers.
Sources
- redhat-cnalr CVE authority record
Primary source ·
- A2A Java SDK JDK HTTP client original advisory
Primary source ·
- ENISA EUVD-2026-127024
Primary source ·