Vulnerability in org.asynchttpclient:async-http-client (CVE-2026-107226)
Summary
Vulnerability in org.asynchttpclient:async-http-client (CVE-2026-107226). Data can be tampered with by attackers. Exploitable via Secure. Mitigation: upgrade to 3.0.14 or later.
Original description
The description as published by the source.
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:
http://example.com -> Set-Cookie: SID=attacker-value; Secure; Path=/
https://example.com -> Cookie: SID=attacker-value
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:
http://insecure.example.com -> Set-Cookie: SID=attacker-value; Secure; Domain=example.com; Path=/
https://bank.example.com -> Cookie: SID=attacker-value
A plaintext Set-Cookie of the same name, domain and path overwrites a Secure cookie, and one with Max-Age=0 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-…
Source: GitHub Security Advisories (Global) NVD GitHub Advisory
Auto-generated summary
Assembled by SecPulse from the source data (CVSS, CWE, affected versions) using templates — no AI involved. Check the original description and references below for exact details.
A vulnerability tracked as CVE-2026-107226 has been found in org.asynchttpclient:async-http-client.
Attackers can target a specific entry point like Secure over the network to misuse the product.
Data can be tampered with by attackers. CVSS score: 6.8/10.
What to do: upgrade org.asynchttpclient:async-http-client to 3.0.14 or later.
If unsure, ask your IT team or search "org.asynchttpclient:async-http-client CVE-2026-107226" on the vendor's site.
CVE-2026-107226 (org.asynchttpclient:async-http-client) — CWE-384 / CVSS v3 6.8
Attack vector: remote (network-reachable) / unauthenticated / no user interaction
Attack surface: Secure / localhost / CookieStore / SID
Patched: 3.0.14 — apply immediately
Workaround: Do not share one CookieStore between plaintext and HTTPS origins that are not mutually trusted, including hosts under the same site.
Plan: 1) Audit SBOM/dependencies, 2) Stage→prod upgrade, 3) Add WAF/proxy monitoring on affected endpoints, 4) Hunt IOCs in logs.
Refs: see the GHSA / vendor advisory / patched release linked on this page.
A vulnerability (CWE-384) exists in org.asynchttpclient:async-http-client. Attackers reach the vulnerable code path via Secure without authentication.
Check the vendor advisory for the affected versions of org.asynchttpclient:async-http-client. Attack surface: Secure / localhost / CookieStore / SID.
Severity: Medium (CVSS 6.8/10). Data can be tampered with by attackers.
Update to 3.0.14.
Workaround: Do not share one CookieStore between plaintext and HTTPS origins that are not mutually trusted, including hosts under the same site.
Search webserver/proxy logs for unusual request patterns matching this CVE's known IOCs. Audit SBOM/dependencies to find affected services.
Response actions
Concrete steps and command examples for SOC/SRE teams to execute in order
-
1Identify exposure identify
Audit SBOM/dependencies for affected components.資産台帳・SBOM・依存マニフェストで org.asynchttpclient:async-http-client を使っているサービスとバージョンを洗い出す。
-
2Apply temporary workaround mitigate
Do not share one `CookieStore` between plaintext and HTTPS origins that are not mutually trusted, including hosts under the same site.パッチが適用されるまでの応急処置として、Do not share one
CookieStorebetween plaintext and HTTPS origins that are not mutually trusted, including hosts under the same site. を実施。回避策の副作用 (機能低下) を確認した上で。 -
3Apply patch patch
Upgrade org.asynchttpclient:async-http-client to 3.0.14ステージング環境で 3.0.14 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスを含めること。
-
4Post-deployment verification verify
Confirm patched version is live in productionパッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番ではアクセスログ・WAF でアラート再発が無いか継続監視。