{
  "id": "CVE-2026-130626",
  "url": "https://poc.griffinguard.io/cve/CVE-2026-130626",
  "published_at": "2026-11-17T14:15:56.7Z",
  "title": "JDK HTTP client GET/DELETE follow cross-authority redirects with injected client, leaking API-key headers (POST-only gap)",
  "vendor": "a2a-java",
  "product": "a2a-java-sdk-http-client",
  "cvss": {
    "score": 7.5,
    "source": "cna",
    "vector": "CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N"
  },
  "kev": {
    "in_kev": false,
    "added_at": null,
    "days_after_publication": null
  },
  "first_poc": null,
  "poc_repo_count": 0,
  "exploit_count": 0,
  "suspicious_repo_count": 0,
  "edge_device": null,
  "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.",
  "cwe": "CWE-522",
  "cvss_by_source": {
    "cna": 7.5
  },
  "repos": [],
  "remediation": {
    "affected": [
      {
        "vendor": "a2a-java",
        "product": "a2a-java-sdk-http-client",
        "ranges": [
          "\u003e= 1.3.0.Final, \u003c= 1.4.0.Final"
        ],
        "fixed_in": null
      }
    ],
    "solutions": [
      "Upgrade to 1.5.0.Final or later. PR #1257 routes JDK GET, DELETE, and SSE requests through a client with native redirects disabled. Synchronous GET redirects are handled explicitly by the SDK using the shared RedirectHeaderPolicy; streaming requests do not follow redirects. The reporter reviewed the proposed fix and confirmed that it addresses the reported issue."
    ],
    "workarounds": [
      "On affected versions, supply a JDK HttpClient configured with HttpClient.Redirect.NEVER to prevent automatic redirect following."
    ],
    "references": [
      {
        "kind": "Vendor advisory",
        "url": "https://github.com/a2aproject/a2a-java/security/advisories/GHSA-f72f-v52v-99g2"
      }
    ]
  },
  "exploit_refs": [],
  "hunt_profile": [],
  "rules": []
}
