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

> Attackers can reuse authenticated connections to access data or authority belonging to other identities due to improper connection pool partitioning.

- **Severity:** High 7.4 (`CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 7 Oct 2026
- **Updated:** 8 Oct 2026
- **Also known as:** DEBIAN-CVE-2026-107230, GHSA-v2j5-22fr-j62r, MINI-635g-6pfv-9vmc, MINI-8cmg-j6cq-jgc6, ROOT-APP-MAVEN-CVE-2026-107230, UBUNTU-CVE-2026-107230

## What is CVE-2026-107230?

CVE-2026-107230 is a high-severity authentication bypass vulnerability in AsyncHttpClient async-http-client, published on 7 Oct 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

The AsyncHttpClient (AHC) library allows Java applications to easily execute HTTP requests and asynchronously process HTTP responses. From 2.0.0 until 3.0.14, connection-pool partitioning still omits identity-defining fields for Kerberos, SPNEGO, NTLM, and authenticated proxy connections. Logins without a configured principal, proxy realms, identities sharing a user name, and SOCKS or CONNECT proxy logins can reuse a socket authenticated as a different identity. A later request is then executed under the first identity and can expose that identity's data or authority to another caller. In the affected execution path, SpnegoEngine, NTLM, Kerberos, SPNEGO, SOCKS, and CONNECT control or expose the vulnerable behavior. This issue is fixed in version 3.0.14.

Weakness: CWE-863 (Incorrect Authorization), CWE-346 (Origin Validation Error)

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

4 open source packages ship an affected version, including org.asynchttpclient:async-http-client.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `org.asynchttpclient:async-http-client` | Maven | From 2.0.0 to 2.16.1 | None |
| `org.asynchttpclient:async-http-client` | Maven | From 2.0.0 to 2.16.1 | None |
| `org.asynchttpclient:async-http-client` | Maven | From 3.0.0 | 3.0.14 |
| `org.asynchttpclient:async-http-client` | Maven | From 3.0.0 | 3.0.14 |

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

Upgrade org.asynchttpclient:async-http-client to 3.0.14 or later.

## Is CVE-2026-107230 being exploited?

There is no known exploitation of CVE-2026-107230 in the wild and no public exploit code.

## Fix prompt for AI coding agents

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

What it is: CVE-2026-107230 is a high-severity authentication bypass vulnerability in AsyncHttpClient async-http-client, published on 7 Oct 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2026-107230 in the wild and no public exploit code.

Affected packages and fixed versions:
- org.asynchttpclient:async-http-client (Maven): affected from 2.0.0 up to 2.16.1; no fix listed
- org.asynchttpclient:async-http-client (Maven): affected from 2.0.0 up to 2.16.1; no fix listed
- org.asynchttpclient:async-http-client (Maven): affected from 3.0.0; fixed in 3.0.14
- org.asynchttpclient:async-http-client (Maven): affected from 3.0.0; fixed in 3.0.14

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

## Sources

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

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