Is org.asynchttpclient:async-http-client 2.15 vulnerable?
Maven · 1 release from 2.15.0 to 2.15.0 · latest org.asynchttpclient:async-http-client is 3.0.14 · checked 18 Nov 2026
Yes: 13 known advisories
Yes. org.asynchttpclient:async-http-client 2.15.0, the last 2.15 release, is affected by 13 known security advisories (1 critical, 4 high, 7 medium, 1 low), including CVE-2026-107282, CVE-2026-107227, CVE-2026-107230. Upgrade to 3.0.14 or later to fix all of them.
mvn versions:use-dep-version -Dincludes=org.asynchttpclient:async-http-client -DdepVersion=3.0.14 -DforceVersion=trueIs your project on an affected org.asynchttpclient:async-http-client?
Look after several Java apps? Indie watches up to 15 repos, private ones too, for $5 a month. See Indie
Advisories affecting org.asynchttpclient:async-http-client 2.15.0
AsyncHttpClient CookieStore Silently Overrides Caller's Explicit Cookie Header via setHeader (Bypass of CVE-2024-53990 Fix)
- Affected
- >=3.0.0 <3.0.14 · >=2.1.0 <=2.16.1
- Fixed in
- 3.0.14
AsyncHttpClient: Cookies received over plaintext HTTP can plant, overwrite or delete Secure cookies set over HTTPS
- Affected
- >=3.0.0 <3.0.14 · >=2.1.0 <=2.16.1
- Fixed in
- 3.0.14
AsyncHttpClient: Unbounded WebSocket permessage-deflate decompression enables a decompression-bomb denial of service when compression is enabled
- Affected
- >=3.0.0 <3.0.14 · >=2.2.0 <=2.16.1
- Fixed in
- 3.0.14
AsyncHttpClient: Pooled connections can still be shared across NTLM, Negotiate and proxy logins
- Affected
- >=3.0.0 <3.0.14 · >=2.0.0 <=2.16.1
- Fixed in
- 3.0.14
AsyncHttpClient: Digest authentication cnonce generated with a non-cryptographic random source
- Affected
- >=3.0.0 <3.0.12 · >=2.0.0 <2.16.1
- Fixed in
- 2.16.1, 3.0.12
AsyncHttpClient: WebSocket proxy credentials sent to the origin server over a CONNECT tunnel
- Affected
- >=3.0.0 <3.0.12 · >=2.0.0 <2.16.1
- Fixed in
- 2.16.1, 3.0.12
AsyncHttpClient: Cookie Domain attribute is not checked against the public suffix list, so a cookie can be set for co.uk
- Affected
- >=3.0.0 <3.0.13 · >=2.0.0 <2.16.1
- Fixed in
- 2.16.1, 3.0.13
AsyncHttpClient: Replay to a different host sends the original host request and credentials to the new host
- Affected
- >=3.0.0 <3.0.13 · >=2.0.0 <2.16.1
- Fixed in
- 2.16.1, 3.0.13
AsyncHttpClient: Digest challenge without a usable nonce downgrades to Basic and sends the password in cleartext
- Affected
- >=3.0.0.Beta1 <3.0.13 · >=2.0.0 <2.16.1
- Fixed in
- 2.16.1, 3.0.13
AsyncHttpClient re-sends client-wide realm credentials to a cross-origin redirect target
- Affected
- >=3.0.9 <3.0.12 · >=2.14.5 <2.16.1
- Fixed in
- 2.16.1, 3.0.12
AsyncHttpClient sends origin credentials to the proxy on the plaintext CONNECT request
- Affected
- >=3.0.0 <3.0.12 · >=2.0.0 <2.16.1
- Fixed in
- 2.16.1, 3.0.12
AsyncHttpClient's unbounded HTTP/1.1 response decompression enables a decompression-bomb denial of service
- Affected
- >=3.0.0 <3.0.12 · >=2.0.0 <2.16.1
- Fixed in
- 2.16.1, 3.0.12
AsyncHttpClient stores cookie for an unrelated domain (cookie tossing) via ThreadSafeCookieStore
- Affected
- >=3.0.0.Beta1 <3.0.11 · >=2.0.0 <2.16.0
- Fixed in
- 2.16.0, 3.0.11
Which of your client projects are still on org.asynchttpclient:async-http-client 2.15?
NPMscan reads the lockfiles in every GitHub repo you pick, finds the exact org.asynchttpclient:async-http-client version each one installs, and checks it against these advisories. Each finding comes with the command that fixes it.
Other org.asynchttpclient:async-http-client versions
- org.asynchttpclient:async-http-client 3.0
- org.asynchttpclient:async-http-client 2.16
- org.asynchttpclient:async-http-client 2.14
- org.asynchttpclient:async-http-client 2.12
- org.asynchttpclient:async-http-client 2.11
- org.asynchttpclient:async-http-client 2.10
- All org.asynchttpclient:async-http-client advisories
Advisory data from OSV.dev (opens OSV.dev in a new tab), which includes the GitHub Advisory Database. Release list from the Maven registry. Refreshed daily.