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.
CVE-2026-55688
This medium-severity CVE scores 4.0 under a secondary CVSS source (NVD's own analysis pending). EPSS exploit probability: 0.3%, top 75% of all CVEs by exploit prediction. GitHub Security Advisory data not yet ingested — confidence will rise once GHSA publishes (typical lag: hours to days for open-source ecosystem CVEs; never for infrastructure-only CVEs).
- Lower severity and no public exploit yet
A fix is available — apply it.
- CVSS v3
- 4.0
- EG Score
- 4.0(medium)
- EG Risk
- 18(Track)EG Risk 18/100SSVC: Track
EG Risk is EchelonGraph's 0–100 priority score: it fuses intrinsic severity with real-world exploitation and automatability so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner. Distinct from the 0–10 EG Score (severity).
How it’s computedSeverity40% × 45%Exploitation0% × 40%Automatability0% × 15%Action: Routine — remediate on your standard cadence. - EPSS PROB
- 0%
- EPSS %ILE
- 25%
- KEV
- Not listed
Published
July 1, 2026
Last Modified
August 6, 2026
Advisory Details (2)
Auto-updated Jul 3, 2026Cookie stored for an unrelated domain (cookie tossing) in AsyncHttpClient ThreadSafeCookieStore · Advisory · AsyncHttpClient/async-http-client · GitHub
Affected: 3.0.11 and 2.16.0
https://github.com/AsyncHttpClient/async-http-client/security/advisories/GHSA-m452-q8c9-rg2freject set-cookie domain that doesn't match the request host
Patch available: AsyncHttpClient/async-http-client async-http-client-project-3.0.11 (PR #2196 merged 2026-06-14)
https://github.com/AsyncHttpClient/async-http-client/pull/2196Patch Availability(1)
| Vendor / Ecosystem | Fixed in / Patch | Released | Source |
|---|---|---|---|
| ubuntu | libasync-http-client-java (2.12.3-1ubuntu0.24.04.1) @ noble | 2026-08-25 | ubuntu |
Patches are aggregated from vendor advisories (Red Hat, Microsoft, Cisco, GitHub) and package ecosystems (OSV, GHSA). Multiple rows for the same upstream release have been deduplicated.
Affected Packages
(2 across 2 ecosystems)
Debian:11(1)
| Package | Vulnerable range | Fixed in | Dependents |
|---|---|---|---|
| async-http-client | 2.12.2-1 | 2.12.2-1+deb11u1 | — |
Debian:12(1)
| Package | Vulnerable range | Fixed in | Dependents |
|---|---|---|---|
| async-http-client | 2.12.3-1 | — | — |
Weakness Classification(1)
MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.
All Vendor Advisories
(1)
Every vendor that published an advisory referencing this CVE — pulled from our cve_vendor_advisories aggregation. Click any row for the vendor's original advisory page.
Data Freshness Timeline
(refreshed 9× in last 7d / 51× in last 30d)
Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. Most recent first.
- 2026-08-25 13:49 UTCEPSS rescore
- 2026-08-25 02:04 UTCEG score recompute
- 2026-08-25 02:04 UTCVendor advisory
- 2026-08-23 04:51 UTCEG score recompute
- 2026-08-23 00:19 UTCEPSS rescore
- 2026-08-22 06:58 UTCEG score recompute
- 2026-08-21 23:49 UTCEPSS rescore
- 2026-08-20 04:36 UTCEG score recompute
- 2026-08-19 17:04 UTCEPSS rescore
- 2026-08-18 22:31 UTCEG score recompute
- 2026-08-18 13:48 UTCEPSS rescore
- 2026-08-17 23:19 UTCEG score recompute
- 2026-08-17 13:47 UTCEPSS rescore
- 2026-08-16 23:35 UTCEG score recompute
- 2026-08-16 14:56 UTCEPSS rescore
- 2026-08-16 02:14 UTCEPSS rescore
- 2026-08-15 03:48 UTCEG score recompute
- 2026-08-15 01:30 UTCEPSS rescore
- 2026-08-14 05:54 UTCEG score recompute
- 2026-08-13 22:00 UTCEPSS rescore
- 2026-08-13 08:01 UTCEG score recompute
- 2026-08-12 13:51 UTCEPSS rescore
- 2026-08-12 10:08 UTCEG score recompute
- 2026-08-11 12:13 UTCEG score recompute
- 2026-08-11 00:00 UTCEPSS rescore
Show 64 moreShow fewer
- 2026-08-09 16:26 UTCEG score recompute
- 2026-08-09 13:46 UTCEPSS rescore
- 2026-08-08 18:33 UTCEG score recompute
- 2026-08-08 16:37 UTCEPSS rescore
- 2026-08-07 20:39 UTCEG score recompute
- 2026-08-06 22:45 UTCEG score recompute
- 2026-08-06 15:52 UTCEG score recompute
- 2026-08-06 13:47 UTCEPSS rescore
- 2026-08-05 19:17 UTCEPSS rescore
- 2026-08-04 20:06 UTCEG score recompute
- 2026-08-04 15:10 UTCEPSS rescore
- 2026-08-04 10:39 UTCEPSS rescore
- 2026-08-03 22:11 UTCEG score recompute
- 2026-08-03 10:36 UTCEPSS rescore
- 2026-08-03 00:18 UTCEG score recompute
- 2026-08-02 02:27 UTCEPSS rescore
- 2026-08-01 04:31 UTCEG score recompute
- 2026-08-01 04:16 UTCEPSS rescore
- 2026-07-31 06:35 UTCEG score recompute
- 2026-07-30 16:28 UTCEPSS rescore
- 2026-07-30 08:39 UTCEG score recompute
- 2026-07-30 01:30 UTCEPSS rescore
- 2026-07-29 08:31 UTCEG score recompute
- 2026-07-28 15:37 UTCEPSS rescore
- 2026-07-28 09:09 UTCEG score recompute
- 2026-07-27 11:08 UTCEG score recompute
- 2026-07-26 14:54 UTCEPSS rescore
- 2026-07-26 13:13 UTCEG score recompute
- 2026-07-25 14:18 UTCEPSS rescore
- 2026-07-24 14:18 UTCEPSS rescore
- 2026-07-23 14:18 UTCEPSS rescore
- 2026-07-23 03:20 UTCEG score recompute
- 2026-07-22 14:08 UTCEPSS rescore
- 2026-07-21 15:25 UTCEPSS rescore
- 2026-07-20 17:08 UTCEPSS rescore
- 2026-07-19 14:31 UTCEPSS rescore
- 2026-07-19 14:31 UTCEPSS rescore
- 2026-07-19 02:29 UTCEPSS rescore
- 2026-07-18 10:04 UTCEPSS rescore
- 2026-07-16 17:03 UTCEPSS rescore
- 2026-07-15 16:57 UTCEPSS rescore
- 2026-07-15 16:57 UTCEPSS rescore
- 2026-07-15 02:00 UTCEPSS rescore
- 2026-07-15 02:00 UTCEPSS rescore
- 2026-07-13 22:31 UTCEPSS rescore
- 2026-07-13 06:13 UTCEPSS rescore
- 2026-07-13 06:13 UTCEPSS rescore
- 2026-07-12 05:46 UTCEPSS rescore
- 2026-07-11 08:27 UTCEPSS rescore
- 2026-07-11 08:27 UTCEPSS rescore
- 2026-07-09 19:10 UTCEPSS rescore
- 2026-07-09 19:10 UTCEPSS rescore
- 2026-07-08 15:16 UTCEPSS rescore
- 2026-07-08 15:16 UTCEPSS rescore
- 2026-07-07 13:46 UTCEPSS rescore
- 2026-07-07 13:46 UTCEPSS rescore
- 2026-07-06 02:23 UTCEPSS rescore
- 2026-07-06 02:23 UTCEPSS rescore
- 2026-07-05 02:31 UTCEPSS rescore
- 2026-07-05 02:30 UTCEPSS rescore
- 2026-07-04 06:31 UTCEPSS rescore
- 2026-07-04 06:31 UTCEPSS rescore
- 2026-07-01 21:09 UTCEG score recompute
- 2026-07-01 21:08 UTCNVD updatefirst tracked
Frequently asked(5)
What is CVE-2026-55688?
When was CVE-2026-55688 disclosed?
Is CVE-2026-55688 actively exploited?
What is the CVSS score of CVE-2026-55688?
How do I remediate CVE-2026-55688?
Dependency Blast Radius
See which npm, PyPI, Go, and Maven packages are affected by CVE-2026-55688
Is Your Infrastructure Affected by CVE-2026-55688?
EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.