# AsyncHttpClient re-sends client-wide realm credentials to a cross-origin redirect target Advisory record · `GHSA-f8m2-889x-vw4x` - **Identifiers:** `GHSA-f8m2-889x-vw4x` · `CVE-2026-85717` - **State:** Confirmed - **Severity:** CVSS 6.8 Medium - **Critical:** No - **Weakness (CWE):** [CWE-200](https://cwe.mitre.org/data/definitions/200.html) · [CWE-522](https://cwe.mitre.org/data/definitions/522.html) - **Tags:** [Information disclosure](https://agentprime.io/advisories/tag/info-disclosure.md) · [Hard-coded credentials](https://agentprime.io/advisories/tag/hard-coded-credentials.md) - **Published:** 17 Sept 2026 - **Updated:** 17 Sept 2026 - **Reviewed by a person:** No Published by the GitHub Advisory Database at 17 Sept 2026, 17:19 UTC. agentprime has not analysed this yet, so whether it affects any app is not known. ## Affected packages - `org.asynchttpclient:async-http-client` (Maven): affected `>=3.0.9, <3.0.12 || >=2.14.5, <2.16.1`; fixed in `3.0.12`, `2.16.1` ## Machine-written summary Summary written by Claude Haiku from the source advisory. Not reviewed by a person. > The async-http-client Maven package (org.asynchttpclient:async-http-client) versions 3.0.9 through 3.0.11 and 2.14.5 through 2.16.0 can re-send client-wide realm credentials, such as Basic or Digest credentials, to a different origin when following redirects that end in a 401 response. An attacker who controls a redirect target can receive these credentials, which requires the client to have a realm set on its configuration and redirects enabled. Upgrade to 3.0.12 or 2.16.1. As a workaround, set the realm on individual requests instead of on the client configuration. Written 2 Nov 2026. ## Not analysed yet We haven’t published our analysis of this Advisory yet. Once a person has reviewed it, this page will say what’s vulnerable, what has to be true for your app to be affected, and how to check. ## Severity and exploitation - 6.8 Medium, CVSS 3.1: `CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:C/C:H/I:N/A:N`, from CNA (GitHub_M) - **CISA KEV:** Not listed. - **EPSS:** 0.0053, the 44th percentile, on 6 Nov 2026: FIRST’s estimate of the chance of exploitation in the next 30 days. ## Timeline - 31 Oct 2026, 14:16 UTC: First seen by agentprime - 31 Oct 2026, 14:16 UTC: [Confirmed by OSV](https://osv.dev/vulnerability/GHSA-f8m2-889x-vw4x) ## Sources - [GitHub Advisory Database: GHSA-f8m2-889x-vw4x](https://github.com/advisories/GHSA-f8m2-889x-vw4x) - [OSV: GHSA-f8m2-889x-vw4x](https://osv.dev/vulnerability/GHSA-f8m2-889x-vw4x) - - - - - Facts on this page come from the GitHub Advisory Database (CC-BY 4.0), OSV and the other sources listed, as published. We don’t reproduce full advisory descriptions, which can contain exploit code. ## Check whether this affects you A Match means an installed version is in the affected range above. Most don’t affect the app; agentprime hasn’t analysed this one yet. - With the agentprime MCP server (), ask your agent to check the project: `check_lockfile` sends a lockfile, `check_packages` a list of installed packages, and both return the Matches and the upgrades that clear them. `get_advisory` returns this record. Setup: - In a browser: reads your lockfile in the browser, never uploading it. - Whether it touches your code, with file and line: the Claude Code plugin, - As JSON: , or `POST https://api.agentprime.io/v1/match` with your packages () --- The web page: . Everything for agents: .