# CVE-2026-130626: The core JDK HTTP client (a2a-java-sdk-http-client) applies the GHSA-9rhm redirect-neutralization only to the POST path.


- **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:** No
- **Published:** 17 Nov 2026
- **Updated:** 17 Nov 2026
- **Also known as:** GHSA-f72f-v52v-99g2

## What is CVE-2026-130626?

CVE-2026-130626 is a high-severity vulnerability in a2a-java-sdk-http-client, published on 17 Nov 2026. 

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

Weakness: CWE-522 (Insufficiently Protected Credentials)

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


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

No fix has been published for CVE-2026-130626 yet. Limit exposure of the affected software until one is available.

## Is CVE-2026-130626 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-130626 is a high-severity vulnerability in a2a-java-sdk-http-client, published on 17 Nov 2026. 
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-130626 exists.

Affected product: a2a-java-sdk-http-client. No package-level version data is available, so check the vendor advisory linked from the reference page.

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-130626/ (Markdown: https://insights.sbomify.com/CVE-2026-130626/index.md)
```

## Sources

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

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