CVE-2026-107230

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

Published Oct 7, 2026 CVSS 3.1 · 7.4 High EPSS < 1% KEV · Not listed
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.

Analysis

AI-generated

Technical impact

The AsyncHttpClient library incorrectly partitions connection pools by ignoring identity‑defining fields for Kerberos, SPNEGO, NTLM, and proxy authentication. When a socket is authenticated as one user, the library may later reuse that socket for another request that also uses authentication, causing the request to be processed under the original identity. This can allow a caller to access data or perform actions that belong to the first identity, leading to accidental credential misuse and information disclosure. The flaw is captured by CWE‑346, CWE‑488 and CWE‑863.

Affected Systems

Any Java application that links AsyncHttpClient between versions 2.0.0 and 3.0.14 and performs HTTP requests with Kerberos, SPNEGO, NTLM, or authenticated proxy protocols is affected. The vulnerability resides in the library itself rather than in a specific external product.

Risk and Exploitability

The CVSS score of 7.4 indicates high severity. The EPSS score of <1% means exploitation probability is low. The vulnerability is not listed in CISA’s KEV catalog. An attacker can potentially trigger the flaw by making an HTTP request through the affected library that re‑uses a previously authenticated socket belonging to a different identity. Since the vulnerability does not require modifying application code, it can be exploited by normal client traffic if the application uses connection pooling for these authentication schemes.

Remediation

No solution or workaround provided in the CVE record.

OpenCVE Recommended Actions

  • Upgrade AsyncHttpClient to version 3.0.14 or later, where the connection pool properly partitions connections by identity.
  • If upgrading is not immediately possible, configure the library to disable connection pooling for NTLM, SPNEGO, and authenticated proxy authentication flows until the patch is applied.
  • Add application‑level checks to verify that the identity of an established connection matches the requester before allowing privileged operations, and monitor for anomalous reuse of authenticated sockets.

Generated by OpenCVE AI on October 9, 2026 at 03:35 UTC.

Tracking

Sign in to view the affected projects.

Advisories

Source ID Title
Github GHSA Github GHSA GHSA-v2j5-22fr-j62r AsyncHttpClient: Pooled connections can still be shared across NTLM, Negotiate and proxy logins
History
Type Values Removed Values Added
First Time appeared Asynchttpclient Project
Asynchttpclient Project async-http-client
Vendors & Products Asynchttpclient Project
Asynchttpclient Project async-http-client
Type Values Removed Values Added
Metrics ssvc

{'options': {'Automatable': 'no', 'Exploitation': 'none', 'Technical Impact': 'total'}, 'version': '2.0.3'}

Type Values Removed Values Added
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.
Title AsyncHttpClient: Pooled connections can still be shared across NTLM, Negotiate and proxy logins
Weaknesses CWE-346
CWE-863
References
Metrics cvssV3_1

{'score': 7.4, 'vector': 'CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:N'}

Weaknesses
  • CWE-346

    Origin Validation Error

  • CWE-488

    Exposure of Data Element to Wrong Session

  • CWE-863

    Incorrect Authorization

Sources

Status
PUBLISHED
Assigner
GitHub_M
Published
Updated
Oct 8, 2026, 5:59 PM
Reserved
Oct 7, 2026, 2:34 PM
Status
Awaiting Analysis
Published
Oct 7, 2026, 10:17 PM
Modified
Oct 8, 2026, 8:35 PM
Severity
Important
Public date
Oct 7, 2026, 9:00 PM