AsyncHttpClient: Cookies received over plaintext HTTP can plant, overwrite or delete Secure cookies set over HTTPS
CVE-2026-107226GHSA-p2jm-6hj6-9rjg
What to do
Partial vendor fix. Follow the primary source's mitigation guidance and check back for a fix.
This page has no inventory attached, so it cannot say whether you are affected. A vendor fix is not proof that your deployment is fixed.
Affected packages
Maven org.asynchttpclient:async-http-client
- Affected
- >= 3.0.0, <= 3.0.13>= 2.1.0, <= 2.16.1
- Fixed in
- 3.0.14
Sources
- Open Source Vulnerabilities (OSV.dev), including the GitHub Advisory Database
OSV record GHSA-p2jm-6hj6-9rjg lists affected ranges: Maven org.asynchttpclient:async-http-client >=3.0.0 =2.1.0 <=2.16.1
VerifiedObserved Structured OSV record; GitHub-reviewed advisory.
- GitHub Advisory Database and maintainer security advisories on GitHub
GitHub-reviewed advisory GHSA-p2jm-6hj6-9rjg lists affected ranges: Maven org.asynchttpclient:async-http-client >=3.0.0 =2.1.0 <=2.16.1
VerifiedObserved Structured GitHub Advisory Database record (type=reviewed) from the GitHub REST API.
Severity and exploitation
- Exploitation
- No confirmed exploitation recorded. Patch Next marks exploitation only from CISA KEV.
- CVSS
- 6.8 · CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:C/C:N/I:H/A:N
- EPSS
- CVE-2026-107226: 0.29% estimated exploitation activity in the next 30 days; percentile 22.07 (FIRST EPSS, 2026-11-03). This is a model estimate, not proof of exploitation or customer exposure.
Source description
As published by the source; long descriptions are shortened.
Impact The cookie store ignores the scheme a Set-Cookie 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 Secure 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 Secure 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 Secure 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 Set-Cookie of the same name, domain and path overwrites a Secure cookie, and one with Max-Age=0 deletes it. Depending…
Dates and revisions
- Published by the source
- Last modified by the source
- Source last checked
- Revision 2 · amended ·
Amended from ghsa record GHSA-p2jm-6hj6-9rjg
- Revision 1 · created ·
Published from osv record GHSA-p2jm-6hj6-9rjg
Agent brief
Preview the exact text before you copy it. Commands are read-only suggestions; review them before running anything.
# Patch Next advisory brief: CVE-2026-107226 Advisory: AsyncHttpClient: Cookies received over plaintext HTTP can plant, overwrite or delete Secure cookies set over HTTPS IDs: CVE-2026-107226, GHSA-p2jm-6hj6-9rjg Record: https://patchnext.com/advisories/cve-2026-107226 (revision 2, source checked 26 Oct 2026, 16:58 UTC) Inventory: none attached. This brief comes from a public page and does not say whether any deployment is affected. Severity: Medium (CVSS 6.8) Exploitation: no confirmed exploitation recorded. Patch Next confirms exploitation only from CISA KEV. Vendor response: Partial vendor fix; fixed versions by package: org.asynchttpclient:async-http-client 3.0.14. A vendor fix does not mean a deployment is fixed. ## Affected components - Maven org.asynchttpclient:async-http-client: affected >= 3.0.0, <= 3.0.13; >= 2.1.0, <= 2.16.1; fixed in 3.0.14 ## Suggested inspection (read-only) - Maven org.asynchttpclient:async-http-client: check the installed version with your package manager. ## Supported action No complete vendor fix is recorded. Follow the primary source's mitigation guidance and check this record again before closing anything. ## Required regression checks - Run the test suite and a production build. - Exercise the features that depend on org.asynchttpclient:async-http-client. - Repeat the inspection and confirm that only fixed versions remain installed. ## Rollback considerations - Keep the previous lockfile and deployment artifact. Rolling back reinstates the vulnerable version, so apply any documented mitigation while you fix forward. ## Unresolved questions - Which deployments run an affected version? - Exploitation status can change. Check again before lowering the priority. - Mark the work resolved only after the fixed version is verified in production. ## Sources - Verified: https://osv.dev/vulnerability/GHSA-p2jm-6hj6-9rjg (OSV record GHSA-p2jm-6hj6-9rjg lists affected ranges: Maven org.asynchttpclient:async-http-client >=3.0.0 =2.1.0 <=2.16.1) - Verified: https://github.com/advisories/GHSA-p2jm-6hj6-9rjg (GitHub-reviewed advisory GHSA-p2jm-6hj6-9rjg lists affected ranges: Maven org.asynchttpclient:async-http-client >=3.0.0 =2.1.0 <=2.16.1) Commands are suggestions: review each one before running it.
Loading voting…