DEBIAN-CVE-2026-107226

The AsyncHttpClient AHC library allows Java applications to easily execute HTTP requests and asynchronously process HTTP responses. From 2.1.0 until 3.0.14, the default ThreadSafeCookieStore does not retain whether a Set-Cookie response used a secure transport. It accepts Secure cookies received...

CVE-2026-107226

The AsyncHttpClient AHC library allows Java applications to easily execute HTTP requests and asynchronously process HTTP responses. From 2.1.0 until 3.0.14, the default ThreadSafeCookieStore does not retain whether a Set-Cookie response used a secure transport. It accepts Secure cookies received...

CVE-2026-107226

The AsyncHttpClient AHC library allows Java applications to easily execute HTTP requests and asynchronously process HTTP responses. From 2.1.0 until 3.0.14, the default ThreadSafeCookieStore does not retain whether a Set-Cookie response used a secure transport. It accepts Secure cookies received...

EUVD-2026-97761

The AsyncHttpClient AHC library allows Java applications to easily execute HTTP requests and asynchronously process HTTP responses. From 2.1.0 until 3.0.14, the default ThreadSafeCookieStore does not retain whether a Set-Cookie response used a secure transport. It accepts Secure cookies received...

CVE-2026-107226

The AsyncHttpClient (AHC) library (versions 2.1.0 through 3.0.13) contains a vulnerability where the default ThreadSafeCookieStore fails to track whether a Set-Cookie response was sent over a secure transport. This allows an attacker controlling a plaintext same-site response to plant, overwrite,...

CVE-2026-107226 AsyncHttpClient: Cookies received over plaintext HTTP can plant, overwrite or delete Secure cookies set over HTTPS

The AsyncHttpClient AHC library allows Java applications to easily execute HTTP requests and asynchronously process HTTP responses. From 2.1.0 until 3.0.14, the default ThreadSafeCookieStore does not retain whether a Set-Cookie response used a secure transport. It accepts Secure cookies received...

CVE-2026-107226 AsyncHttpClient: Cookies received over plaintext HTTP can plant, overwrite or delete Secure cookies set over HTTPS

The AsyncHttpClient AHC library allows Java applications to easily execute HTTP requests and asynchronously process HTTP responses. From 2.1.0 until 3.0.14, the default ThreadSafeCookieStore does not retain whether a Set-Cookie response used a secure transport. It accepts Secure cookies received...

CVE-2026-107226: Session Fixation

The AsyncHttpClient AHC library allows Java applications to easily execute HTTP requests and asynchronously process HTTP responses. From 2.1.0 until 3.0.14, the default ThreadSafeCookieStore does not retain whether a Set-Cookie response used a secure transport. It accepts Secure cookies received...

CVE-2026-107282

A flaw was found in AsyncHttpClient. When an application performs request retries or failovers to a different host, the client fails to properly reset the original host's security and proxy context. Consequently, an unintended destination host can receive sensitive information, including...

CVE-2026-107230

A flaw was found in AsyncHttpClient. This flaw can lead to information disclosure and privilege escalation when handling authenticated connections. The library omits user identity details when partitioning its connection pool for authentication protocols such as Kerberos and NTLM. As a result, a...

CVE-2026-107231

A flaw was found in AsyncHttpClient where an HTTP Digest authentication challenge with a missing or empty nonce is incorrectly treated as Basic authentication. A malicious origin server or proxy can trigger the client to resend the request with an Authorization: Basic header, exposing the usernam...

CVE-2026-107232

A flaw was found in AsyncHttpClient. When an HTTP proxy rejects an HTTPS CONNECT request, the client can incorrectly treat the still-plaintext connection to the proxy as an established tunnel. A subsequent proxy authentication challenge or redirect can cause the client to resend the origin reques...

CVE-2026-107279

A flaw was found in AsyncHttpClient. A remote attacker can bypass mutual authentication by offering HTTP Digest authentication configured with integrity protection auth-int. Because the client fails to validate the response authentication value under this configuration and treats the unverified...

CVE-2026-107227

A flaw was found in AsyncHttpClient's WebSocket permessage-deflate handling. When WebSocket compression is enabled it is disabled by default, the client does not limit the size of a message after decompression; the configured frame and buffer limits apply to the compressed data. A malicious or...

Improper Input Validation

AsyncHttpClient is vulnerable to Improper Input Validation. The vulnerability is due to failure to reject public suffixes in cookie Domain attributes, which allows an attacker controlling a host beneath a public suffix to inject or overwrite cookies shared across unrelated hosts, potentially...

Cleartext Transmission Of Sensitive Information

AsyncHttpClient is vulnerable to Cleartext Transmission of Sensitive Information. The vulnerability is due to improper handling of cross-host request replay, which allows an attacker to trigger documented retry or failover paths that send the original host's request data, authorization credential...

Authentication Downgrade

AsyncHttpClient is vulnerable to Authentication Downgrade. The vulnerability is due to improper handling of Digest authentication challenges with missing or empty nonces, which allows a malicious origin or proxy to downgrade authentication to Basic and obtain the user's username and password in a...

EUVD-2026-94589

AsyncHttpClient CookieStore Silently Overrides Caller's Explicit Cookie Header via setHeader Bypass of CVE-2024-53990 Fix...

GHSA-2JWH-9RMR-J4XF AsyncHttpClient CookieStore Silently Overrides Caller's Explicit Cookie Header via setHeader (Bypass of CVE-2024-53990 Fix)

Impact With the cookie store enabled, which is the default, a Cookie header that the caller sets on a request with setHeader or addHeader is thrown away whenever the store holds any cookie for the request's origin: the request's cookie list is written into that header afterwards and replaces it...

AsyncHttpClient CookieStore Silently Overrides Caller's Explicit Cookie Header via setHeader (Bypass of CVE-2024-53990 Fix)

Impact With the cookie store enabled, which is the default, a Cookie header that the caller sets on a request with setHeader or addHeader is thrown away whenever the store holds any cookie for the request's origin: the request's cookie list is written into that header afterwards and replaces it...