ZDF
Sign inSign up

Vulnerabilities

Vulnerability · CVE-2026-107226

AsyncHttpClient: Cookies received over plaintext HTTP can plant, overwrite or delete Secure cookies set over HTTPS

Published Oct 8, 2026 · catalog updated Oct 8, 2026 · AsyncHttpClient: Cookies received over

Check if you run it

No confirmed exploitation is on record for CVE-2026-107226. EPSS is 0.36%. Act only if a listed version of AsyncHttpClient: Cookies received over 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: Cookies received over).
  • No vendor fix or required action is stored. Compare the linked advisory before you change production.
Severity
Medium6.8
Known exploitation
Not in CISA/VulnCheck KEV
EPSS
0.36%
Remediation
Advisory link
Affected products
Maven org.asynchttpclient:async-http-client

### Impact The cookie store ignores the scheme a arrived on. draft-ietf-httpbis-rfc6265bis-22 (approved to obsolete RFC 6265, in the RFC Editor queue) Section 5.7 requires a user agent to ignore a cookie with the attribute unless it arrived over a secure connection (step 13), and to ignore a non-Secure cookie from an insecure connection when it would overlay a Secure cookie the store already holds (step 16). Neither rule is implemented. The only handling is on retrieval, where a Secure cookie is not sent over plaintext. So anyone who can answer a plaintext request to a site can set, replace or delete the site's cookies, and the next HTTPS request carries the attacker's value back inside TLS: This does not need an attacker on the network path. A plaintext host under the same site reaches the HTTPS one by setting a domain cookie: A plaintext of the same name, domain and path overwrites a Secure cookie, and one with deletes it. Depending on what the application does with the cookie, this is session fixation into the HTTPS session, an overwritten CSRF token, or the removal of a cookie the site relies on. Unlike GHSA-qjr7-w8pj-pmv9, which can only add a cookie, this replaces or deletes one, hence Integrity: High; the harm lands on the HTTPS site, hence Scope: Changed. ### Affected versions * 3.x: up to and including 3.0.13 * 2.x: from 2.1.0, when the cookie store was introduced, up to and including 2.16.1 ### Patches Fixed in 3.0.14 on the 3.x line. A cookie with the attribute is ignored unless the request was secure, and a non-Secure cookie from a request that did not use TLS is ignored when it would overlay a Secure cookie of the same name whose path its own path falls under. A plaintext response can therefore no longer plant, overwrite or delete a cookie. When several cookies of one name match a request, the client sends only the first, so the order in which the store returns them decides which one is used. That order is now: on a secure request, cookies received in a

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.1.0 → 2.16.1
  • Maven org.asynchttpclient:async-http-client2.1.0, 2.1.1, 2.1.2
  • Maven org.asynchttpclient:async-http-client3.0.0 → 3.0.14

How to fix CVE-2026-107226

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-107226. EPSS is 0.36%. Act only if a listed version of AsyncHttpClient: Cookies received over is installed.

Which versions are affected?

Compare what you have installed with 2.1.0 → 2.16.1, 2.1.0, 2.1.1, 2.1.2, 3.0.0 → 3.0.14. Compare the installed version with the linked vendor advisory before you change production.

What should an analyst verify?

CWE-384; CWE-693: Protection Mechanism Failure. EPSS 0.36%. 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 ignores the scheme a arrived on. draft-ietf-httpbis-rfc6265bis-22 (approved to obsolete RFC 6265, in the RFC Editor queue) Section 5.7 requires a user agent to ignore a cookie with the attribute unless it arrived over a secure connection (step 13), and to ignore a non-Secure cookie from an insecure connection when it would overlay a Secure cookie the store already holds

  2. Oct 8, 2026 · Catalog

    Fix available

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

  3. Oct 8, 2026 · GitHub Advisory Database

    Fix available

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

  4. Oct 8, 2026 · GitHub Advisory Database

    Fix available

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

  5. Oct 8, 2026 · GitHub Advisory Database

    Fix available

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

  6. Oct 8, 2026 · Catalog

    Updated

    ### Impact The cookie store ignores the scheme a arrived on. draft-ietf-httpbis-rfc6265bis-22 (approved to obsolete RFC 6265, in the RFC Editor queue) Section 5.7 requires a user agent to ignore a cookie with the attribute unless it arrived over a secure connection (step 13), and to ignore a non-Secure cookie from an insecure connection when it would overlay a Secure cookie the store already holds

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.