# AsyncHttpClient: Pooled connections can still be shared across NTLM, Negotiate and proxy logins

Advisory record · `GHSA-v2j5-22fr-j62r`

- **Identifiers:** `GHSA-v2j5-22fr-j62r` · `CVE-2026-107230`
- **State:** Confirmed
- **Severity:** CVSS 7.4 High
- **Critical:** No
- **Weakness (CWE):** [CWE-346](https://cwe.mitre.org/data/definitions/346.html) · [CWE-863](https://cwe.mitre.org/data/definitions/863.html)
- **Tags:** [Broken access control](https://agentprime.io/advisories/tag/access-control.md) · [CWE-346](https://agentprime.io/advisories/tag/cwe-346.md)
- **Published:** 8 Oct 2026
- **Updated:** 8 Oct 2026
- **Reviewed by a person:** No

Published by the GitHub Advisory Database at 8 Oct 2026, 16:49 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.0, <3.0.14 || >=2.0.0, <=2.16.1`; fixed in `3.0.14`

## Machine-written summary

Summary written by Claude Haiku from the source advisory. Not reviewed by a person.

> Async-http-client (Maven org.asynchttpclient:async-http-client) versions 3.0.13 and earlier 3.x releases, and 2.x up to 2.16.1, can reuse a pooled HTTP/1.1 connection across different NTLM, Kerberos, SPNEGO or proxy identities. A request under one identity may be served on a connection that another identity authenticated, including unauthenticated requests and requests with same-named users from different realms. Upgrade to 3.0.14. The 2.x line will not be fixed, so upgrade to 3.0.14. Using separate client instances per identity avoids the sharing.

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

- 7.4 High, CVSS 3.1: `CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:N`, from CNA (GitHub_M)

- **CISA KEV:** Not listed.
- **EPSS:** 0.0019, the 8th percentile, on 5 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-v2j5-22fr-j62r)

## Sources

- [GitHub Advisory Database: GHSA-v2j5-22fr-j62r](https://github.com/advisories/GHSA-v2j5-22fr-j62r)
- [OSV: GHSA-v2j5-22fr-j62r](https://osv.dev/vulnerability/GHSA-v2j5-22fr-j62r)
- <https://github.com/AsyncHttpClient/async-http-client/security/advisories/GHSA-v2j5-22fr-j62r>
- <https://nvd.nist.gov/vuln/detail/CVE-2026-107230>
- <https://github.com/AsyncHttpClient/async-http-client/commit/d3bb4d68b41acf5d3ab7541afa9fdfe7ec3ba054>
- <https://github.com/AsyncHttpClient/async-http-client>
- <https://github.com/AsyncHttpClient/async-http-client/releases/tag/async-http-client-project-3.0.14>

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 (<https://api.agentprime.io/mcp>), 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: <https://agentprime.io/mcp.md>
- In a browser: <https://agentprime.io/check/> reads your lockfile in the browser, never uploading it.
- Whether it touches your code, with file and line: the Claude Code plugin, <https://agentprime.io/plugin.md>
- As JSON: <https://api.agentprime.io/v1/advisories/GHSA-v2j5-22fr-j62r>, or `POST https://api.agentprime.io/v1/match` with your packages (<https://agentprime.io/api.md>)

---

The web page: <https://agentprime.io/advisories/GHSA-v2j5-22fr-j62r/>. Everything for agents: <https://agentprime.io/llms.txt>.