Skip to content
Patch Next
Sign inAdd to your agent

← Actionable
High, CVSS 7.4amended

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

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

What to do

Partial vendor fix. Follow the primary source's mitigation guidance and check back for a fix.

This page has no inventory attached, so it cannot say whether you are affected. A vendor fix is not proof that your deployment is fixed.

Add to your agent

Affected packages

Sources

Severity and exploitation
Exploitation
No confirmed exploitation recorded. Patch Next marks exploitation only from CISA KEV.
CVSS
7.4 · CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:N
EPSS
  • CVE-2026-107230: 0.19% estimated exploitation activity in the next 30 days; percentile 8.53 (FIRST EPSS, 2026-11-03). This is a model estimate, not proof of exploitation or customer exposure.
Source description

As published by the source; long descriptions are shortened.

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…

Dates and revisions
Published by the source
Last modified by the source
Source last checked
  1. Revision 2 · amended ·

    Amended from ghsa record GHSA-v2j5-22fr-j62r

  2. Revision 1 · created ·

    Published from osv record GHSA-v2j5-22fr-j62r

Agent brief

Preview the exact text before you copy it. Commands are read-only suggestions; review them before running anything.

# Patch Next advisory brief: CVE-2026-107230

Advisory: AsyncHttpClient: Pooled connections can still be shared across NTLM, Negotiate and proxy logins
IDs: CVE-2026-107230, GHSA-v2j5-22fr-j62r
Record: https://patchnext.com/advisories/cve-2026-107230 (revision 2, source checked 26 Oct 2026, 16:58 UTC)
Inventory: none attached. This brief comes from a public page and does not say whether any deployment is affected.
Severity: High (CVSS 7.4)
Exploitation: no confirmed exploitation recorded. Patch Next confirms exploitation only from CISA KEV.
Vendor response: Partial vendor fix; fixed versions by package: org.asynchttpclient:async-http-client 3.0.14. A vendor fix does not mean a deployment is fixed.

## Affected components
- Maven org.asynchttpclient:async-http-client: affected >= 3.0.0, < 3.0.14; >= 2.0.0, <= 2.16.1; fixed in 3.0.14

## Suggested inspection (read-only)
- Maven org.asynchttpclient:async-http-client: check the installed version with your package manager.

## Supported action
No complete vendor fix is recorded. Follow the primary source's mitigation guidance and check this record again before closing anything.

## Required regression checks
- Run the test suite and a production build.
- Exercise the features that depend on org.asynchttpclient:async-http-client.
- Repeat the inspection and confirm that only fixed versions remain installed.

## Rollback considerations
- Keep the previous lockfile and deployment artifact. Rolling back reinstates the vulnerable version, so apply any documented mitigation while you fix forward.

## Unresolved questions
- Which deployments run an affected version?
- Exploitation status can change. Check again before lowering the priority.
- Mark the work resolved only after the fixed version is verified in production.

## Sources
- Verified: https://osv.dev/vulnerability/GHSA-v2j5-22fr-j62r (OSV record GHSA-v2j5-22fr-j62r lists affected ranges: Maven org.asynchttpclient:async-http-client >=3.0.0 =2.0.0 <=2.16.1)
- Verified: https://github.com/advisories/GHSA-v2j5-22fr-j62r (GitHub-reviewed advisory GHSA-v2j5-22fr-j62r lists affected ranges: Maven org.asynchttpclient:async-http-client >=3.0.0 =2.0.0 <=2.16.1)

Commands are suggestions: review each one before running it.

Loading voting…