Is CVE-2026-107230 exploited in the wild?

No. Junglewise Threat Intelligence has no report of CVE-2026-107230 being exploited in the wild.

How severe is CVE-2026-107230?

High severity, with a CVSS score of 7.4, published 8 October 2026.

Which products and versions are affected?

AsyncHttpClient 3.0.13, 2.16.1.

How is CVE-2026-107230 attacked?

It is attacked over the network, in a software library.

Am I affected by CVE-2026-107230?

Check whether you run AsyncHttpClient at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.

CVE-2026-107230: AsyncHttpClient pooled connection reuse across NTLM and Negotiate logins

CVE-2026-107230 · Severity: high · CVSS 7.4 · Published 2026-10-08

AsyncHttpClient is a library that handles HTTP connections in Java applications. An incomplete security fix allows authenticated connections to be reused for requests with different user identities or no credentials at all, potentially allowing one user's requests to be served under another user's authenticated session. This affects applications that connect to the same host with different credentials, such as services that use Kerberos authentication for internal calls while also fetching user-supplied URLs.

Technologies: AsyncHttpClient. Vendors: AsyncHttpClient.

Quick answers

Is CVE-2026-107230 exploited in the wild?: No. Junglewise Threat Intelligence has no report of CVE-2026-107230 being exploited in the wild.
How severe is CVE-2026-107230?: High severity, with a CVSS score of 7.4, published 8 October 2026.
Which products and versions are affected?: AsyncHttpClient 3.0.13, 2.16.1.
Is there a fix for CVE-2026-107230?: Yes: fixed in 3.0.14. Until then: Use a separate AsyncHttpClient instance per identity, and do not share one between authenticated and unauthenticated requests to a host that uses NTLM or Negotiate. Alternatively, disable connection pooling to prevent connection reuse.</anigation> <parameter name="timeline">[{"kind":"disclosed","at":"2026-10-08"}] Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
How is CVE-2026-107230 attacked?: It is attacked over the network, in a software library.
Am I affected by CVE-2026-107230?: Check whether you run AsyncHttpClient at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.

How to fix

Fixed in: 3.0.14

Use a separate AsyncHttpClient instance per identity, and do not share one between authenticated and unauthenticated requests to a host that uses NTLM or Negotiate. Alternatively, disable connection pooling to prevent connection reuse.</anigation> <parameter name="timeline">[{"kind":"disclosed","at":"2026-10-08"}]

Technical details

The vulnerability is a connection pool key collision in NTLM, Kerberos, and SPNEGO authentication handling. Three cases were not covered by a previous fix: unauthenticated requests reusing sockets authenticated by Kerberos/SPNEGO tickets, proxy realm identities not being differentiated in the pool key, and different realms with the same user name sharing connections. An attacker can send requests to a shared host that reuse authenticated sockets, causing the server to serve their request as a previously authenticated identity.

Affected products

AsyncHttpClient AsyncHttpClient 3.0.13, 2.16.1

Identifiers

CVE-2026-107230
GHSA-v2j5-22fr-j62r

This page as Markdown. Free to reuse under CC BY 4.0 with a link back.