These pages are published after PatchSiren validates generated defensive summaries against stored public CVE and source evidence.
The AsyncHttpClient library fails to properly handle Secure cookies received over plaintext HTTP, allowing an attacker to plant, overwrite, or delete Secure cookies set over HTTPS. This vulnerability affects versions 2.1.0 to 2.16.1 and 3.0.0 to 3.0.13 of the org.asynchttpclient:async-http-client package. The vulnerability can be exploited without being on the network path, as long as an attacker can answ [truncated]
The AsyncHttpClient library, used for executing HTTP requests and processing responses in Java applications, has a vulnerability in versions 2.2.0 through 3.0.14. This issue allows for unbounded WebSocket permessage-deflate decompression when compression is enabled, potentially leading to a denial-of-service (DoS) attack through a decompression bomb. A malicious WebSocket peer can exploit this by sending [truncated]
The AsyncHttpClient library, used for executing HTTP requests and processing responses in Java applications, had a vulnerability prior to versions 3.0.12 and 2.16.1. The library generated the HTTP Digest client nonce (cnonce) using ThreadLocalRandom, which is not a cryptographically secure random source. This could allow an observer to infer the generator state and reduce the protection of the authenticat [truncated]
The AsyncHttpClient library, used for HTTP requests in Java applications, had a vulnerability prior to versions 3.0.12 and 2.16.1. When using a proxied WebSocket (ws) request, the CONNECT tunnel would send the proxy's authentication credentials to the origin server. This happened because the library only checked if the URI was secure to decide whether to attach proxy authentication, and since ws is not co [truncated]
The AsyncHttpClient library for Java allows easy execution of HTTP requests and asynchronous processing of HTTP responses. A vulnerability exists in versions prior to 3.0.12 and 2.16.1 where the WebSocketHandler.upgrade function aborts a handshake if the Sec-WebSocket-Accept value is missing or invalid. However, it continues into pipeline installation and onOpen delivery. This could potentially allow fram [truncated]
The AsyncHttpClient library, used in Java applications for executing HTTP requests, has a vulnerability prior to versions 3.0.13 and 2.16.1. This issue allows for cross-host request replay, which can lead to unintended exposure of sensitive information, including the original host's path, Host header, Authorization credentials, or plaintext request, when the request is replayed to a different host.
The AsyncHttpClient library, used by Java applications for HTTP requests, had a vulnerability prior to versions 3.0.13 and 2.16.1. The connection pool key for NTLM and Negotiate authentication did not include the authenticated principal, allowing a pooled socket authenticated for one request to be reused for another request with a different principal. This could lead to the server executing the later requ [truncated]
The AsyncHttpClient library for Java, prior to versions 3.0.13 and 2.16.1, contains a vulnerability where the Domain attribute of cookies is not checked against the public suffix list. This allows a host beneath a public suffix, such as co.uk, to set a cookie for that suffix. Consequently, the shared cookie store sends this cookie to unrelated hosts under the same suffix, potentially leading to the inject [truncated]
The AsyncHttpClient library, used for executing HTTP requests and processing responses in Java applications, had a vulnerability in version 3.0.12. When a peer offered only Digest qop=auth-int, mutual-authentication verification was skipped due to how AuthenticatorUtils.computeExpectedRspAuth and Interceptors handled the response. This allowed a peer that did not know the shared secret to be accepted as t [truncated]
The AsyncHttpClient library, used by Java applications for HTTP requests, had an issue where it could send origin credentials in cleartext to a proxy that rejects the CONNECT request. This happened because the client would infer the existence of an HTTP proxy tunnel from the last request method instead of the CONNECT result. As a result, after a proxy rejects CONNECT, redirect or authentication handlers c [truncated]
The AsyncHttpClient library, used by Java applications for HTTP requests, had a vulnerability prior to versions 3.0.13 and 2.16.1. A malicious origin or proxy could manipulate a Digest challenge to omit or empty the nonce, causing the client to resend credentials in cleartext using Basic authentication. This issue is fixed in the mentioned versions.
The AsyncHttpClient library, used in Java applications for executing HTTP requests, had a vulnerability in versions 2.0.0 through 3.0.14. This issue allowed pooled connections to be shared across different authentication mechanisms like NTLM, Negotiate, and proxy logins, potentially exposing data or authority of one identity to another. The vulnerability is fixed in version 3.0.14.
The AsyncHttpClient library, used by Java applications for HTTP requests, had incomplete origin checks in its default cookie store from versions 2.16.0 to 3.0.13. This flaw allows for cookie tossing onto public-suffix and IP-address hosts, potentially leading to session fixation attacks when applications share a client across different trust domains.
The AsyncHttpClient library, used by Java applications for HTTP requests, had a vulnerability where its cookie store could silently override explicit Cookie headers set by callers, potentially causing requests to be executed under the wrong session. This issue, fixed in version 3.0.14, bypassed a previous fix for CVE-2024-53990 and could impact shared client scenarios.
CVE-2026-85720 debrief based on the supplied source corpus. The AsyncHttpClient library allows Java applications to execute HTTP requests and process HTTP responses asynchronously. A vulnerability in versions 2.0.0 to 2.16.1 and 3.0.12 exposes preemptive origin credentials when using an HTTP proxy to reach an HTTPS origin. This issue is fixed in versions 2.16.1 and 3.0.12. Defenders should assess the vuln [truncated]
The AsyncHttpClient library for Java allows applications to execute HTTP requests and process responses asynchronously. A vulnerability exists in versions 3.0.8 through 3.0.12 where SCRAM ServerSignature or Digest rspauth verification results are computed but a mismatch is logged and the response is still delivered as authenticated. This issue is particularly concerning on non-TLS or compromised transport [truncated]
The AsyncHttpClient library in Java applications allows easy execution of HTTP requests and asynchronous processing of HTTP responses. A vulnerability exists from versions 2.1.0 to 2.16.1 and 3.0.12, where requests using an authenticated SOCKS proxy can expose the proxy's credentials to the origin server due to improper handling of Proxy-Authorization headers.
The CVE-2026-55688 vulnerability affects the AsyncHttpClient library, used for asynchronous HTTP requests in Java applications. This library improperly handles the Domain attribute when storing cookies, leading to a cookie injection issue. Versions 2.0.0 to 2.15.0 and 3.0.0.Beta1 to 3.0.10 are impacted. An attacker can exploit this by setting a cookie for an unrelated domain, which the client will then se [truncated]
The AsyncHttpClient (AHC) library allows Java applications to easily execute HTTP requests and asynchronously process HTTP responses. Versions on the 2.x branch prior to 2.15.0 and the 3.x branch prior to 3.0.10 leak `Cookie` headers to cross-origin redirect targets. When following a redirect to a different origin, the `propagatedHeaders()` method in `Redirect30xInterceptor.java` strips `Authorization` an [truncated]
