CVE
a2a-java-sdk-http-client credential leak via redirects in JDK HTTP client
Affects a2a-java-sdk-http-client 1.3.0.Final through 1.4.0.Final when the application supplies a redirect-capable JDK HttpClient. No vendor rating is given. Fixed in 1.5.0.Final.
Written by a model from the sources below. Verify against them.
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N
- Exploited
- Proof of concept public, per CISA
- Fix
- Fixed in 1.5.0.Final
- Who is exposed
- Specific setups only
Do first: Check whether your setup matches what the bug needs. The application supplies a redirect-capable JDK HttpClient (Redirect.NORMAL or Redirect.ALWAYS) to the SDK, the documented way to enable POST redirects. Affected versions are 1.3.0.Final through 1.4.0.Final of the a2a-java-sdk-http-client package. The redirect is followed on credentialed GET and DELETE requests.
- Last modified
- Whether it needs action now or is a reference record, by fixed rules, with why. Last checked is when cve.now last re-read it.What do these mean? →
- Reference
- Last checked
- A 0-100 score for how much a CVE matters across the industry: exploitation, exposure, how widely the software is used, severity and whether a fix exists.What do these mean? →
- 38/100 · provisional
- How many real-world setups can hit the bug, from the vendor's advisory and CISA data. It does not know your setup.What do these mean? →
- Specific setups only
- Whether working attack code is public (Exploit-DB, Metasploit, Nuclei or GitHub). Public code makes attacks easier.What do these mean? →
- None on Exploit-DB, Metasploit or GitHub
- Exploitation: poc
- Automatable: yes
- Technical impact: partial
Summary
The a2a-java-sdk-http-client library lets a remote attacker, without logging in or any user action, capture API-key and token headers such as X-API-Key and X-Auth-Token. This happens when an application supplies an HTTP client that follows redirects, because GET and DELETE requests then follow cross-authority redirects to an attacker-controlled host and send those headers along.
Original 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.
Who should check
Teams running a2a-java 1.3.0.Final through 1.4.0.Final with the JDK HTTP client module, where an application injects a redirect-capable HttpClient into the transport.
Not fixed by: The POST-only redirect fix from v1.3.2.Final did not cover GET and DELETE requests.
“>= 1.3.0.Final, <= 1.4.0.Final”
cve.now Index
- Exploitation15/40CISA rates a proof of concept as public
- Exposure15/25Specific setups only, CISA rates it automatable
- Reach?/20Unknown. No tracked technology or package matched
- Severity7.5/10CVSS 7.5
- No patch0/5No signal
What would change the score
- Would score about 73 if added to CISA KEV
- Would score about 68 if CISA's SSVC rates exploitation active
What to do
Check whether your setup matches what the bug needs.
The application supplies a redirect-capable JDK HttpClient (Redirect.NORMAL or Redirect.ALWAYS) to the SDK, the documented way to enable POST redirects. Affected versions are 1.3.0.Final through 1.4.0.Final of the a2a-java-sdk-http-client package. The redirect is followed on credentialed GET and DELETE requests.Upgrade to a fixed version: 1.5.0.Final.
Workaround: Supply a JDK HttpClient configured with HttpClient.Redirect.NEVER to prevent automatic redirect following.
Check your systems with an agent
Paste this into a coding or ops agent. It checks your systems read-only and reports a table per asset.
Check whether my systems are affected by CVE-2026-130626 (JDK HTTP client GET/DELETE follow cross-authority redirects with injected client, leaking API-key headers (POST-only gap)), using the cve.now data below.
Rules: work read-only. Do not run exploit code, proof-of-concept scripts or scanners that send attack payloads, and do not change any configuration, package, image or deployment. Report findings only.
What cve.now has for CVE-2026-130626 (entry last updated 2026-11-17):
Affected:
- a2a-java a2a-java-sdk-http-client: from 1.3.0.Final, through 1.4.0.Final
Fixed versions: 1.5.0.Final.
Conditions (all must be true for the bug to be hit):
- The application supplies a redirect-capable JDK HttpClient (Redirect.NORMAL or Redirect.ALWAYS) to the SDK, the documented way to enable POST redirects. (source: https://github.com/a2aproject/a2a-java/security/advisories/GHSA-f72f-v52v-99g2)
- Affected versions are 1.3.0.Final through 1.4.0.Final of the a2a-java-sdk-http-client package. (source: https://github.com/a2aproject/a2a-java/security/advisories/GHSA-f72f-v52v-99g2)
- The redirect is followed on credentialed GET and DELETE requests. (source: https://github.com/a2aproject/a2a-java/security/advisories/GHSA-f72f-v52v-99g2)
Setup: the bug needs a feature or setting that is off by default or uncommon. Check whether each asset has it on.
Attacker needs: network access, no login, no user action.
Workaround: Supply a JDK HttpClient configured with HttpClient.Redirect.NEVER to prevent automatic redirect following. (source: https://www.cve.org/CVERecord?id=CVE-2026-130626)
CISA KEV: CVE-2026-130626 is not listed as of cve.now's last read.
This KEV status is for CVE-2026-130626 only. If you also check another CVE, look up its own KEV status; never assume it from this one.
How to check:
- Installed software: check what is actually running, not what a repo declares. Read the version from each host, container image and Kubernetes node (the binary's version output, the OS package database, image layers), and check whether the conditions above hold there. Distribution packages may carry a backported fix under an older version number; confirm against the distribution's own advisory.
Verify against the linked advisories before concluding, and cite the date you read each one:
- https://github.com/a2aproject/a2a-java/security/advisories/GHSA-f72f-v52v-99g2
- https://www.cve.org/CVERecord?id=CVE-2026-130626
Do not conclude an asset is unaffected unless you checked it and the evidence covers both its version and the conditions above. If you could not check something, mark it unknown and say what is missing.
Report a table with one row per asset and these columns: Asset | Version or build | Status (affected, fixed, not applicable, unknown) | Compensating controls | Exposure (internet-facing, internal, none) | Evidence | Next action.
Entry: https://cve.now/CVE-2026-130626
For follow-up questions, use the cve.now MCP server at https://mcp.cve.now/mcp (no authentication), for example execute with name cve.get and arguments {"id": "CVE-2026-130626"}.Timeline
- CVE published
- First seen by cve.now
- CISA SSVC assessment
Exploitation: poc · Automatable: yes · Technical impact: partial
- Record last updated
Affected versions
- a2a-java a2a-java-sdk-http-client
From 1.3.0.Final · through 1.4.0.Final
Evidence 3
Vendor advisory · 1
Establishes: Affected and fixed versions.
- Advisory
CVE record · 2
Establishes: The identifier and description.
- Record
- Record
Corrections
None so far.
Something wrong on this page? Report an error. Every fix is listed here.
Questions about CVE-2026-130626
Is CVE-2026-130626 being exploited?
It is not in CISA's Known Exploited Vulnerabilities catalog, and CISA's SSVC assessment does not mark exploitation as active. That does not mean it has not been attacked: vendors and researchers can report attacks before CISA lists them. CISA's SSVC assessment notes a proof of concept exists. No public exploit code is tracked.Source: cve.now feed data
What does this mean?
The SDK's HTTP client follows cross-authority redirects on credentialed GET and DELETE requests when the application supplies a redirect-capable JDK HttpClient, so API-key headers can be sent to a different authority. The advisory states that an attacker can capture the victim's API-key credentials for the legitimate agent authority.Source: github.com, cve.org
Which versions are affected by CVE-2026-130626?
a2a-java-sdk-http-client: from 1.3.0.Final through 1.4.0.Final.Source: cve.now feed data
Am I affected, and how do I check?
Versions 1.3.0.Final through 1.4.0.Final of the a2a-java-sdk-http-client package are in the affected range. The relevant setup is an application that passes a JDK HttpClient with Redirect.NORMAL or Redirect.ALWAYS to the SDK, which is the documented way to enable POST redirects. Check the SDK version in the dependency tree and the redirect policy of the HttpClient passed to the SDK.Source: github.com, cve.org
How do I fix CVE-2026-130626?
Upgrade a2a-java-sdk-http-client to 1.5.0.Final or later. Until the upgrade is made, supply a JDK HttpClient configured with HttpClient.Redirect.NEVER.Source: github.com, cve.org