CVE-2026-107226
Received Received - Intake

AsyncHttpClient Cookie Handling Security Bypass

Vulnerability report for CVE-2026-107226, including description, CVSS score, EPSS score, affected products, exploitability, helpful resources, and attack-flow context.

Publication date: 2026-10-12

Last updated on: 2026-10-12

Assigner: GitHub, Inc.

Description

The AsyncHttpClient (AHC) library allows Java applications to easily execute HTTP requests and asynchronously process HTTP responses. From 2.1.0 until 3.0.14, the default ThreadSafeCookieStore does not retain whether a Set-Cookie response used a secure transport. It accepts Secure cookies received over plaintext and permits insecure cookies to overlay or delete existing Secure cookies with matching scope. An attacker controlling a plaintext same-site response can consequently plant, replace, or remove cookie state later sent to an HTTPS origin, enabling session fixation, CSRF-token replacement, or loss of security-relevant state. This issue is fixed in version 3.0.14.

CVSS Scores

EPSS Scores

Probability:
Percentile:

Meta Information

Published
2026-10-12
Last Modified
2026-10-12
Generated
2026-10-13
AI Q&A
2026-10-12
EPSS Evaluated
N/A
NVD
EUVD

Affected Vendors & Products

Showing 2 associated CPEs
Vendor Product Version / Range
AsyncHttpClient async-http-client >= 2.1.0, <= 2.16.1
AsyncHttpClient async-http-client >= 3.0.0, < 3.0.14

Helpful Resources

Exploitability

CWE
CWE Icon
KEV
KEV Icon
CWE ID Description
CWE-384 Authenticating a user, or otherwise establishing a new user session, without invalidating any existing session identifier gives an attacker the opportunity to steal authenticated sessions.
CWE-693 The product does not use or incorrectly uses a protection mechanism that provides sufficient defense against directed attacks against the product.

Attack-Flow Graph

AI Quick Actions

Instant insights powered by AI
Executive Summary

This vulnerability affects the AsyncHttpClient library in Java applications. The default ThreadSafeCookieStore from versions 2.1.0 to 3.0.13 does not properly handle Secure cookies, which should only be set over HTTPS. Plaintext HTTP responses can set, overwrite, or delete Secure cookies, allowing attackers to manipulate session state or CSRF tokens.

Detection Guidance

Check if your system uses AsyncHttpClient versions between 2.1.0 and 3.0.13. Run commands like 'mvn dependency:tree' for Maven or 'gradle dependencies' for Gradle to inspect dependencies. Look for AsyncHttpClient in the output.

Impact Analysis

An attacker could exploit this to perform session fixation, replace CSRF tokens, or remove critical cookies by sending malicious plaintext HTTP responses. This compromises the integrity of HTTPS sessions and could lead to unauthorized access or data manipulation.

Compliance Impact

This vulnerability could violate security requirements in GDPR and HIPAA by allowing unauthorized session manipulation or data access. Secure cookie handling is critical for protecting sensitive data, and improper handling may lead to compliance violations.

Mitigation Strategies

Upgrade AsyncHttpClient to version 3.0.14 or later. If using version 2.x, migrate to 3.0.14 as the 2.x line is end-of-life. Avoid shared cookie stores between plaintext and HTTPS origins as a temporary workaround.

Chat Assistant

Ask questions about this CVE
Hi! I’m here to help you understand CVE-2026-107226. Ask me anything about the vulnerability, its impact, or mitigation strategies.
0/70

EPSS Chart