Connect your agent
AdvisoriesCriticalCheck your lockfilePluginHow it worksPricing Connect your agent

Advisory record · GHSA-v2j5-22fr-j62r

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

CVSS 7.4 HighEPSS 0.0019 · 8th percentile

Published by the GitHub Advisory Database at 8 Oct 2026, 16:49 UTC. agentprime has not analysed this yet, so whether it affects any app is not known.

PackageEcosystemAffectedFixed in
org.asynchttpclient:async-http-clientMaven>=3.0.0, <3.0.14 || >=2.0.0, <=2.16.13.0.14
Identifiers
GHSA-v2j5-22fr-j62r · CVE-2026-107230
Weakness (CWE)
CWE-346 · CWE-863
Tags
Published
8 Oct 2026
Updated
8 Oct 2026

Machine-written summary

Summary written by Claude Haiku from the source advisory. Not reviewed by a person.

Async-http-client (Maven org.asynchttpclient:async-http-client) versions 3.0.13 and earlier 3.x releases, and 2.x up to 2.16.1, can reuse a pooled HTTP/1.1 connection across different NTLM, Kerberos, SPNEGO or proxy identities. A request under one identity may be served on a connection that another identity authenticated, including unauthenticated requests and requests with same-named users from different realms. Upgrade to 3.0.14. The 2.x line will not be fixed, so upgrade to 3.0.14. Using separate client instances per identity avoids the sharing.

Written 2 Nov 2026.

Not analysed yet

We haven’t published our analysis of this Advisory yet. Once a person has reviewed it, this page will say what’s vulnerable, what has to be true for your app to be affected, and how to check.

Severity and exploitation

ScoreRatingCVSSVectorSource
7.4 High 3.1 CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:N CNA (GitHub_M)
  • CISA KEV Not listed.
  • EPSS 0.0019, the 8th percentile, on 5 Nov 2026: FIRST’s estimate of the chance of exploitation in the next 30 days.

Timeline

  1. 31 Oct 2026, 14:16 UTC First seen by agentprime
  2. 31 Oct 2026, 14:16 UTC Confirmed by OSV

Sources

Facts on this page come from the GitHub Advisory Database (CC-BY 4.0), OSV and the other sources listed, as published. We don’t reproduce full advisory descriptions, which can contain exploit code.