ZDF
Sign inSign up

Vulnerabilities

Vulnerability · CVE-2026-107230

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

Published Oct 8, 2026 · catalog updated Oct 8, 2026 · AsyncHttpClient: Pooled connections can

Check if you run it

No confirmed exploitation is on record for CVE-2026-107230. EPSS is 0.19%. Act only if a listed version of AsyncHttpClient: Pooled connections can is installed.

Gaps on this record

  • The stored product name is a package slug. The name on this page is taken from the title (AsyncHttpClient: Pooled connections can).
  • No vendor fix or required action is stored. Compare the linked advisory before you change production.
Severity
High7.4
Known exploitation
Not in CISA/VulnCheck KEV
EPSS
0.19%
Remediation
Advisory link
Affected products
Maven org.asynchttpclient:async-http-client

### Impact The fix for GHSA-vvp4-63h8-v5pm in 3.0.13 folded the authenticated principal into the HTTP/1.1 connection pool key, so that a connection one principal authenticated with NTLM, Kerberos or SPNEGO is not handed to another. It left three cases out. In each, a socket that one identity authenticated can still be drawn by a request belonging to a different identity, and the server serves that request as the first one. 1. **A login with no configured principal.** Kerberos and SPNEGO against the ticket cache or the default JAAS login, which is the usual deployment, leave the realm's principal unset, and the key stayed unscoped in that case. A request to the same host that carries no credentials at all draws the authenticated socket and is served as the service identity. 2. **The proxy realm.** Only the origin realm went into the key. A connection authenticated to a proxy with NTLM or Negotiate is handed to requests of another proxy identity, or of none, and the proxy acts for them as the first identity. 3. **Identities that share a user name.** Only the principal string went into the key, so and shared connections, as did two realms differing only in password, login context, keytab or service principal. The Kerberos login cache in had the same collision, and it was an unsynchronised map, so concurrent first use could hand one caller's login to another. ### Who is Impacted Applications that authenticate with NTLM, Kerberos or SPNEGO, to an origin or to a proxy, and send requests under different identities, or both with and without credentials, to the same host through one client. The sharpest case is a service that calls an internal host under its own Kerberos identity and also fetches user-supplied URLs: a URL on that host is fetched as the service. Basic and Digest are not affected. ### Affected versions * 3.x: 3.0.13 * 2.x: 2.16.1 Earlier versions are covered by GHSA-vvp4-63h8-v5pm. ### Patches Fixed in 3.0.14. The pool key now carries a digest of every field o

Are you affected?

Enter the version you run. The result uses only the ranges stored on this record.

The check returns affected, not affected, or incomplete. It does not guess a version that is missing from the record.

  • Maven org.asynchttpclient:async-http-client2.0.0 → 2.16.1
  • Maven org.asynchttpclient:async-http-client2.0.0, 2.0.1, 2.0.10
  • Maven org.asynchttpclient:async-http-client3.0.0 → 3.0.14

How to fix CVE-2026-107230

What to do

Three questions, each answered from this record only. Confirm the vendor advisory before you patch.

Should you patch?

No confirmed exploitation is on record for CVE-2026-107230. EPSS is 0.19%. Act only if a listed version of AsyncHttpClient: Pooled connections can is installed.

Which versions are affected?

Compare what you have installed with 2.0.0 → 2.16.1, 2.0.0, 2.0.1, 2.0.10, 3.0.0 → 3.0.14. Compare the installed version with the linked vendor advisory before you change production.

What should an analyst verify?

CWE-346; CWE-863: Incorrect Authorization. EPSS 0.19%. There is no CISA KEV listing. No Exploit-DB or Metasploit reference is linked. Use the source links for the original advisory.

Code

The project this record applies to. Exploit listings stay in References.

Timeline

Detection, updates, and resolution for this record.

  1. Oct 8, 2026 · Catalog

    Detected

    ### Impact The fix for GHSA-vvp4-63h8-v5pm in 3.0.13 folded the authenticated principal into the HTTP/1.1 connection pool key, so that a connection one principal authenticated with NTLM, Kerberos or SPNEGO is not handed to another. It left three cases out. In each, a socket that one identity authenticated can still be drawn by a request belonging to a different identity, and the server serves that

  2. Oct 8, 2026 · Catalog

    Fix available

    Maven org.asynchttpclient:async-http-client 3.0.0 → 3.0.14

  3. Oct 8, 2026 · GitHub Advisory Database

    Fix available

    org.asynchttpclient:async-http-client fixed in 3.0.14

  4. Oct 8, 2026 · GitHub Advisory Database

    Fix available

    org.asynchttpclient:async-http-client fixed in 3.0.14

  5. Oct 8, 2026 · GitHub Advisory Database

    Fix available

    org.asynchttpclient:async-http-client fixed in 2.16.1

  6. Oct 8, 2026 · Catalog

    Updated

    ### Impact The fix for GHSA-vvp4-63h8-v5pm in 3.0.13 folded the authenticated principal into the HTTP/1.1 connection pool key, so that a connection one principal authenticated with NTLM, Kerberos or SPNEGO is not handed to another. It left three cases out. In each, a socket that one identity authenticated can still be drawn by a request belonging to a different identity, and the server serves that

Sources

References

Freshness

Last verified in this catalog Oct 18, 2026. Significant claims (KEV, EPSS, CVSS, affected ranges) come from the source rows above — open the original publisher for the authoritative advisory.