CVE-2026-130626
7.5HighPublished 17 Nov 2026 · NVD status: Received · AI triage by gemini-3.1-flash-lite
High
0CVSS v3.110
- Attack vector
- Network
- Complexity
- Low
- Privileges
- None
- User action
- None
- Impact
- High impact on confidentiality
- Weakness
- CWE-522
What an attacker gets
Remote attackers can steal sensitive API credentials by triggering cross-authority redirects on GET or DELETE requests. This requires an application to use a redirect-capable HttpClient.
Root cause
The SDK fails to apply redirect neutralization to GET and DELETE methods, allowing credential headers to be forwarded to attacker-controlled domains.
Affected versions
a2a-java-sdk-http-client versions prior to the patch associated with GHSA-f72f-v52v-99g2.
CVSS v3.1 · CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N
Fix & remediation
Upgrade to the latest version of a2a-java-sdk-http-client. Until patched, configure your HttpClient to use Redirect.NEVER to disable all automatic redirects.
$ mvn dependency:list | grep a2a-java-sdk-http-clientAI-suggested. Run it in staging first and check it against the vendor advisory. Why?
NVD description
The core JDK HTTP client (a2a-java-sdk-http-client) applies the GHSA-9rhm redirect-neutralization only to the POST path. JdkGetBuilder.get(), JdkGetBuilder.getAsyncSSE(), and JdkDeleteBuilder.delete() call the injected httpClient directly, with no redirect gate. An application that supplies a redirect-capable HttpClient (Redirect.NORMAL/ALWAYS) — which is the SDK-documented way to enable POST redirects — silently follows cross-authority redirects on every credentialed GET/DELETE request. The JDK strips Authorization cross-origin, but forwards the four allowlisted custom credential headers (X-API-Key, API-Key, X-Auth-Token, X-Authentication) to the attacker-controlled authority. This is an incomplete-fix variant of GHSA-9rhm: the fix hardened the default client and added a POST-only two-step opt-in, but never covered GET/DELETE.