# CVE-2026-107280: AsyncHttpClient: Cookie Domain attribute is not checked against the public suffix list, so a cookie can be set for co.uk > Attackers can set cookies for public suffixes like co.uk, allowing cross-origin session hijacking or data injection in Java applications using AsyncHttpClient. - **Severity:** Medium 6.9 (`CVSS:4.0/AV:N/AC:H/AT:P/PR:N/UI:N/VC:N/VI:N/VA:N/SC:N/SI:H/SA:N`) - **Exploited in the wild:** Not known - **Login needed:** Not needed - **Attackable:** Over the internet - **Victim action needed:** Not needed - **Fix available:** Yes - **Published:** 7 Oct 2026 - **Updated:** 8 Oct 2026 - **Also known as:** DEBIAN-CVE-2026-107280, ECHO-9a26-378a-6a12, GHSA-f9m8-cv68-674w, MINI-f8wh-3fx7-f27j, MINI-jhp2-x5rc-855h, MINI-v38v-wgfm-mcq6, MINI-vmhf-796w-qq86, UBUNTU-CVE-2026-107280 ## What is CVE-2026-107280? CVE-2026-107280 is a medium-severity vulnerability in AsyncHttpClient async-http-client, published on 7 Oct 2026. An attacker can exploit it over the internet without logging in, with no action from the victim. ### Official description The AsyncHttpClient (AHC) library allows Java applications to easily execute HTTP requests and asynchronously process HTTP responses. Prior to 3.0.13 and 2.16.1, ThreadSafeCookieStore validates Domain attributes with domain matching but does not reject public suffixes. A host beneath a suffix such as co.uk can set a cookie for that suffix, after which the shared cookie store sends it to unrelated hosts under the suffix. This can inject or overwrite session-relevant cookie values across origins. This issue is fixed in versions 3.0.13 and 2.16.1. Weakness: CWE-1275 (Sensitive Cookie with Improper SameSite Attribute) ## Which versions are affected by CVE-2026-107280? 4 open source packages ship an affected version, including org.asynchttpclient:async-http-client. | Package | Ecosystem | Affected | Fixed in | | --- | --- | --- | --- | | `org.asynchttpclient:async-http-client` | Maven | From 2.0.0 | 2.16.1 | | `org.asynchttpclient:async-http-client` | Maven | From 2.0.0 | 2.16.1 | | `org.asynchttpclient:async-http-client` | Maven | From 3.0.0 | 3.0.13 | | `org.asynchttpclient:async-http-client` | Maven | From 3.0.0 | 3.0.13 | ## How do I fix CVE-2026-107280? Upgrade org.asynchttpclient:async-http-client to a fixed version for your release line: 2.16.1 or 3.0.13. ## Is CVE-2026-107280 being exploited? There is no known exploitation of CVE-2026-107280 in the wild and no public exploit code. ## Fix prompt for AI coding agents ```text Check this codebase for CVE-2026-107280 and fix it if it is affected. What it is: CVE-2026-107280 is a medium-severity vulnerability in AsyncHttpClient async-http-client, published on 7 Oct 2026. An attacker can exploit it over the internet without logging in, with no action from the victim. Exploitation: There is no known exploitation of CVE-2026-107280 in the wild and no public exploit code. Affected packages and fixed versions: - org.asynchttpclient:async-http-client (Maven): affected from 2.0.0; fixed in 2.16.1 - org.asynchttpclient:async-http-client (Maven): affected from 2.0.0; fixed in 2.16.1 - org.asynchttpclient:async-http-client (Maven): affected from 3.0.0; fixed in 3.0.13 - org.asynchttpclient:async-http-client (Maven): affected from 3.0.0; fixed in 3.0.13 Task: 1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies. 2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it. 3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead. 4. Run the tests and summarise what changed and why. 5. If nothing in the project is affected, say so and change nothing. Reference: https://insights.sbomify.com/CVE-2026-107280/ (Markdown: https://insights.sbomify.com/CVE-2026-107280/index.md) ``` ## Sources - CVE record: https://www.cve.org/CVERecord?id=CVE-2026-107280 - NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-107280 - OSV: https://osv.dev/vulnerability/CVE-2026-107280 --- From sbomify Insights: https://insights.sbomify.com/CVE-2026-107280/ Summaries are generated and may contain mistakes; the official description above is the record.