Sensitive Cookie with Improper SameSite Attribute Affecting async-http-client package, versions <2.12.3-1+deb12u1
Threat Intelligence
The probability is the direct output of the EPSS model, and conveys an overall sense of the threat of exploitation in the wild. The percentile measures the EPSS probability relative to all known EPSS scores. Note: This data is updated daily, relying on the latest available EPSS model version. Check out the EPSS documentation for more details.
Do your applications use this vulnerable package?
In a few clicks we can analyze your entire application and see what components are vulnerable in your application, and suggest you quick fixes.
Test your applications- Snyk IDSNYK-ECHOLATEST-ASYNCHTTPCLIENT-18601857
- published10 Aug 2026
- disclosed1 Jul 2026
Introduced: 1 Jul 2026
CVE-2026-55688 (opens in a new tab)How to fix?
Upgrade Echo:latest async-http-client to version 2.12.3-1+deb12u1 or higher.
NVD Description
Note: Versions mentioned in the description apply only to the upstream async-http-client package and not the async-http-client package as distributed by Echo.
See How to fix? for Echo:latest relevant fixed versions and status.
The AsyncHttpClient (AHC) library allows Java applications to easily execute HTTP requests and asynchronously process HTTP responses. In versions from 2.0.0 prior to 2.16.0 and from 3.0.0.Beta1 prior to 3.0.11, ThreadSafeCookieStore stored a cookie under the value of its Domain attribute without verifying that the responding host is allowed to set a cookie for that domain, leading to a cookie tossing / cookie injection issue. A host the client connects to can therefore plant a cookie scoped to an unrelated domain, and the client will then send that cookie on later requests to that domain. Applications that use a single AsyncHttpClient instance - and thus the default, shared CookieStore - to reach both an attacker-influenced host and a trusted host are impacted. This issue has been fixed in versions 2.16.0 and 3.0.11.