ZDF
Sign inSign up

Vulnerabilities

Vulnerability · CVE-2026-107280

AsyncHttpClient: Cookie Domain attribute is not checked against the public suffix list, so a cookie can be set for co.uk

Published Oct 8, 2026 · catalog updated Oct 8, 2026 · AsyncHttpClient: Cookie Domain attribute

Check if you run it

No confirmed exploitation is on record for CVE-2026-107280. EPSS is 0.26%. Act only if a listed version of AsyncHttpClient: Cookie Domain attribute is installed.

Gaps on this record

  • The stored product name is a package slug. The name on this page is taken from the title (AsyncHttpClient: Cookie Domain attribute).
  • No vendor fix or required action is stored. Compare the linked advisory before you change production.
Severity
Unknown—
Known exploitation
Not in CISA/VulnCheck KEV
EPSS
0.26%
Remediation
Advisory link
Affected products
Maven org.asynchttpclient:async-http-client

### Impact The cookie store decides whether a 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 that is a public suffix, is not implemented anywhere in the client. So 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: works the same way. The attacker needs only a site under the same suffix as the victim, which for suffixes such as , , or is trivially obtainable. Depending 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. ### Affected versions * 3.x: up to and including 3.0.12 * 2.x: up to and including 2.16.0 ### Relationship to CVE-2026-55688 CVE-2026-55688 (GHSA-m452-q8c9-rg2f) covered the direct form of this, where a host sets a naming an unrelated host, and that form is genuinely fixed: can no longer set , and this was verified as a control. What that fix did not add is the public suffix test, so setting still reaches . This advisory covers only the residual. ### Patches Fixed 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 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. ### Workarounds Do not share one across origins that are not mutually trusted. Supplying a implementation that rejects values which are public suffixes also avoids it. ### Details is . It is used both to accept a on storage and to select cookies for a request, and neither call site consults a public suffix list. A search of the client for an

Are you affected?

Enter the version you run. The result uses only the ranges stored on this record.

The check returns affected, not affected, or incomplete. It does not guess a version that is missing from the record.

  • Maven org.asynchttpclient:async-http-client2.0.0 → 2.16.1
  • Maven org.asynchttpclient:async-http-client3.0.0 → 3.0.13

How to fix CVE-2026-107280

What to do

Three questions, each answered from this record only. Confirm the vendor advisory before you patch.

Should you patch?

No confirmed exploitation is on record for CVE-2026-107280. EPSS is 0.26%. Act only if a listed version of AsyncHttpClient: Cookie Domain attribute is installed.

Which versions are affected?

Compare what you have installed with 2.0.0 → 2.16.1, 3.0.0 → 3.0.13. Compare the installed version with the linked vendor advisory before you change production.

What should an analyst verify?

CWE-1275. EPSS 0.26%. There is no CISA KEV listing. No Exploit-DB or Metasploit reference is linked. Use the source links for the original advisory.

Code

The project this record applies to. Exploit listings stay in References.

Timeline

Detection, updates, and resolution for this record.

  1. Oct 8, 2026 · Catalog

    Detected

    ### Impact The cookie store decides whether a 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 that is a public suffix, is not implemented anywhere in the client. So a host under a multi-label public suffix can set

  2. Oct 8, 2026 · Catalog

    Fix available

    Maven org.asynchttpclient:async-http-client 3.0.0 → 3.0.13

  3. Oct 8, 2026 · Catalog

    Fix available

    Maven org.asynchttpclient:async-http-client 2.0.0 → 2.16.1

  4. Oct 8, 2026 · GitHub Advisory Database

    Fix available

    org.asynchttpclient:async-http-client fixed in 3.0.13; org.asynchttpclient:async-http-client fixed in 2.16.1

  5. Oct 8, 2026 · GitHub Advisory Database

    Fix available

    org.asynchttpclient:async-http-client fixed in 3.0.13

  6. Oct 8, 2026 · GitHub Advisory Database

    Fix available

    org.asynchttpclient:async-http-client fixed in 2.16.1

  7. Oct 8, 2026 · Catalog

    Updated

    ### Impact The cookie store decides whether a 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 that is a public suffix, is not implemented anywhere in the client. So a host under a multi-label public suffix can set

Sources

References

Freshness

Last verified in this catalog Oct 18, 2026. Significant claims (KEV, EPSS, CVSS, affected ranges) come from the source rows above — open the original publisher for the authoritative advisory.