CVE-2026-107280: AsyncHttpClient Cookie Domain Attribute Is Not Vulnerability
MODERATECVE-2026-107280 is a MODERATE cookie domain attribute is not vulnerability (CWE-1275: Sensitive Cookie with Improper SameSite Attribute) affecting AsyncHttpClient libraries in the Maven ecosystem. The issue involves cookie domain attribute is not checked against the public suffix list, so a cookie can be set for co.uk. Remediation is available by upgrading affected packages to version 3.0.13, 2.16.1.
CVE-2026-107280 at a Glance
How to Fix CVE-2026-107280
To remediate this vulnerability, upgrade all affected AsyncHttpClient dependencies to a patched release. Both direct and transitive dependencies should be checked, as frameworks or security libraries may pull in vulnerable versions transitively.
<dependency>
<groupId>org.asynchttpclient</groupId>
<artifactId>async-http-client</artifactId>
<version>3.0.13</version>
</dependency>
<dependency>
<groupId>org.asynchttpclient</groupId>
<artifactId>async-http-client</artifactId>
<version>2.16.1</version>
</dependency>
Run the following command in your project directory to verify that all resolved dependencies use the patched release:
mvn dependency:tree -Dincludes=org.asynchttpclient
How to Check if You Are Affected
To determine whether your Java application is affected by CVE-2026-107280, inspect your build dependencies using the Maven Dependency Plugin:
mvn dependency:tree -Dincludes=org.asynchttpclient
Analyze the terminal output to locate any version of AsyncHttpClient in your dependency tree. If any resolved version matches the vulnerable ranges listed in the table below (for example, versions earlier than 3.0.13), your application is affected.
Note: The mvn dependency:tree -Dincludes=org.asynchttpclient command inspects the resolved dependency graph declared in your project's POM files; it does not perform automated security scanning or inspect runtime dynamic classpaths. Always verify runtime container classpaths and shaded JARs.
Technical Details
Vulnerability Mechanism & Technical Analysis
This vulnerability is classified under CWE-1275: Sensitive Cookie with Improper SameSite Attribute, where the samesite attribute for sensitive cookies is not set, or an insecure value is used. In AsyncHttpClient, software state validation or input boundaries are circumvented during processing. Review the official source advisory statement below for specific affected components, classes, and reproduction details.
Source Advisory Statement
CVE-2026-107280 Affected AsyncHttpClient Versions
2 component(s)| Product / Package | Ecosystem | Affected Versions | Fixed Version |
|---|---|---|---|
|
org.asynchttpclient:async-http-client
|
Maven |
≥ 3.0.0
< 3.0.13
|
3.0.13
|
|
org.asynchttpclient:async-http-client
|
Maven |
≥ 2.0.0
< 2.16.1
|
2.16.1
|
References
Frequently Asked Questions
What is CVE-2026-107280?
Which AsyncHttpClient versions are affected?
What version fixes CVE-2026-107280?
Is async-http-client affected?
What CWE is associated with CVE-2026-107280?
How can I check Maven dependencies for CVE-2026-107280?
Machine-readable OSV JSON
OSV v1.5 Schema
{
"schema_version" : "1.4.0",
"id" : "GHSA-f9m8-cv68-674w",
"modified" : "2026-10-08T16:30:53Z",
"published" : "2026-10-08T16:30:53Z",
"aliases" : [ "CVE-2026-107280" ],
"summary" : "AsyncHttpClient: Cookie Domain attribute is not checked against the public suffix list, so a cookie can be set for co.uk",
"details" : "### Impact\nThe cookie store decides whether a `Domain` attribute may be accepted using only the domain-matching rule of RFC 6265 Section 5.1.3, which asks whether the request host is the domain or ends with a dot followed by it. Section 5.3 step 5, which additionally requires rejecting a `Domain` that is a public suffix, is not implemented anywhere in the client.\n\nSo a host under a multi-label public suffix can set a cookie for the suffix itself, and the store then hands it to every other host under that suffix:\n\n```\nattacker.co.uk -> Set-Cookie: SID=attacker-value; Domain=co.uk; Path=/\nbank.co.uk -> Cookie: SID=attacker-value\n```\n\n`Domain=uk` works the same way. The attacker needs only a site under the same suffix as the victim, which for suffixes such as `co.uk`, `com.au`, or `github.io` is trivially obtainable.\n\nDepending on what the application does with the cookie, this is session fixation, or it overwrites a session the victim site set, or it lets the attacker plant a value the victim site trusts.\n\n### Affected versions\n* 3.x: up to and including 3.0.12\n* 2.x: up to and including 2.16.0\n\n### Relationship to CVE-2026-55688\nCVE-2026-55688 (GHSA-m452-q8c9-rg2f) covered the direct form of this, where a host sets a `Domain` naming an unrelated host, and that form is genuinely fixed: `attacker.co.uk` can no longer set `Domain=bank.co.uk`, and this was verified as a control. What that fix did not add is the public suffix test, so setting `Domain=co.uk` still reaches `bank.co.uk`. This advisory covers only the residual.\n\n### Patches\nFixed in 3.0.13 on the 3.x line. The ICANN section of the Mozilla public suffix list is bundled with the client and a `Domain` matching it is rejected, honouring the list's wildcard and exception rules. The list is data and goes stale, so a suffix added upstream after a release is not recognised until the bundled copy is refreshed. The 2.x line is not yet fixed.\n\n### Workarounds\nDo not share one `CookieStore` across origins that are not mutually trusted. Supplying a `CookieStore` implementation that rejects `Domain` values which are public suffixes also avoids it.\n\n### Details\n`ThreadSafeCookieStore.domainsMatch` is `requestDomain.equals(cookieDomain) || requestDomain.endsWith('.' + cookieDomain)`. It is used both to accept a `Domain` on storage and to select cookies for a request, and neither call site consults a public suffix list. A search of the client for any public suffix or effective TLD handling returns nothing.",
"severity" : [ {
"type" : "CVSS_V4",
"score" : "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"
} ],
"affected" : [ {
"package" : {
"ecosystem" : "Maven",
"name" : "org.asynchttpclient:async-http-client"
},
"ranges" : [ {
"type" : "ECOSYSTEM",
"events" : [ {
"introduced" : "3.0.0"
}, {
"fixed" : "3.0.13"
} ]
} ],
"database_specific" : {
"last_known_affected_version_range" : "<= 3.0.12"
}
}, {
"package" : {
"ecosystem" : "Maven",
"name" : "org.asynchttpclient:async-http-client"
},
"ranges" : [ {
"type" : "ECOSYSTEM",
"events" : [ {
"introduced" : "2.0.0"
}, {
"fixed" : "2.16.1"
} ]
} ],
"database_specific" : {
"last_known_affected_version_range" : "<= 2.16.0"
}
} ],
"references" : [ {
"type" : "WEB",
"url" : "https://github.com/AsyncHttpClient/async-http-client/security/advisories/GHSA-f9m8-cv68-674w"
}, {
"type" : "ADVISORY",
"url" : "https://nvd.nist.gov/vuln/detail/CVE-2026-107280"
}, {
"type" : "WEB",
"url" : "https://github.com/AsyncHttpClient/async-http-client/commit/330267895fe0bdb41bbd027ea6b151d38ee7c23d"
}, {
"type" : "WEB",
"url" : "https://github.com/AsyncHttpClient/async-http-client/commit/d1f0ccec417092098d40242fee7dfac84bb3c21f"
}, {
"type" : "PACKAGE",
"url" : "https://github.com/AsyncHttpClient/async-http-client"
}, {
"type" : "WEB",
"url" : "https://github.com/AsyncHttpClient/async-http-client/releases/tag/async-http-client-project-2.16.1"
}, {
"type" : "WEB",
"url" : "https://github.com/AsyncHttpClient/async-http-client/releases/tag/async-http-client-project-3.0.13"
} ],
"database_specific" : {
"cwe_ids" : [ "CWE-1275" ],
"severity" : "MODERATE",
"github_reviewed" : true,
"github_reviewed_at" : "2026-10-08T16:30:53Z",
"nvd_published_at" : "2026-10-07T22:17:03Z"
}
}