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 7, 2026
·
Updated

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.

Affected Software

1 affected component
maven/org.asynchttpclient/async-http-client<3.0.13, <2.16.1

Remediation

Recommended actions to resolve this vulnerability, in priority order.

  1. Upgrade

    Upgrade AsyncHttpClient 3.x to a version that resolves this vulnerability.

    Fixed in 3.0.13
  2. Upgrade

    Upgrade AsyncHttpClient 2.x to a version that resolves this vulnerability.

    Fixed in 2.16.1

Event History

Oct 7, 2026
CVE Published
via MITRE·09:15 PM
Data Sourced
via MITRE·09:15 PM
DescriptionWeakness
Data Sourced
via NVD·10:17 PM
DescriptionSeverityWeakness

Frequently Asked Questions

1

Which applications are exposed to this issue?

Java applications using AsyncHttpClient with ThreadSafeCookieStore before version 3.0.13 or 2.16.1 are exposed if they use a shared cookie store while making requests to hosts beneath a public suffix.

2

What does an attacker need to exploit it?

An attacker needs control of, or the ability to cause the application to contact, a host under the same public suffix as another target host. That host can set a cookie scoped to the public suffix, which the shared store may then send to unrelated hosts beneath it.

3

What is the impact of a successful exploit?

A malicious host can inject or overwrite session-relevant cookie values for unrelated origins under the same public suffix. This can affect cookie-based session handling across those origins.

4

What should be done if upgrading is not immediately possible?

Avoid sharing a ThreadSafeCookieStore across requests to unrelated hosts under the same public suffix, and do not allow untrusted hosts to set cookies that will be retained for subsequent requests to other origins. Upgrade to AsyncHttpClient 3.0.13 or 2.16.1 when possible.

Contact

SecAlerts Pty Ltd.
132 Wickham Terrace
Fortitude Valley,
QLD 4006, Australia
info@secalerts.co
By using SecAlerts services, you agree to our services end-user license agreement. This website is safeguarded by reCAPTCHA and governed by the Google Privacy Policy and Terms of Service. All names, logos, and brands of products are owned by their respective owners, and any usage of these names, logos, and brands for identification purposes only does not imply endorsement. If you possess any content that requires removal, please get in touch with us.
© 2026 SecAlerts Pty Ltd.
ABN: 70 645 966 203, ACN: 645 966 203