Sign in Sign up
JA · EN · FR
SecPulse
Categories
CVE-2026-107228 medium CVSS 6.8

Authentication Bypass in org.asynchttpclient:async-http-client (CVE-2026-107228)

Summary

Authentication bypass in org.asynchttpclient:async-http-client (CVE-2026-107228). Confidential information can be exposed externally. Exploitable via Cookie. Mitigation: upgrade to 3.0.14 or later.

Original description

The description as published by the source.

Impact

With the cookie store enabled, which is the default, a Cookie header that the caller sets on a request with setHeader or addHeader is thrown away whenever the store holds any cookie for the request's origin: the request's cookie list is written into that header afterwards and replaces it. CVE-2024-53990 fixed the same problem for cookies added with addCookie, but that fix works on the cookie list, and a header set directly never reaches it.

This is not limited to a cookie of the same name. A store cookie of any name erases the caller's header, so a request meant to carry the caller's session cookie goes out with only the store's cookies, and where the store has a cookie of the caller's name, the store's value is sent instead.

It matters most where one client acts for several users. An application that puts each user's session on the request itself, and shares one client and its default cookie store, sends one user's request with a session cookie the store took from a response to another user. The request runs as that other user, so a user of such an application can have their request served under someone else's session, or someone else's under theirs.

Affected versions

  • 3.x: up to and including 3.0.13
  • 2.x: from 2.1.0 up to and including 2.16.1

Patches

Fixed in 3.0.14. The store's cookies are added to a caller's Cookie header instead of replacing it, and where both name the same cookie the caller's is kept. The caller's text is kept as wr…

Source: NIST National Vulnerability Database 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-107228 has been found in org.asynchttpclient:async-http-client.
Attackers can target a specific entry point like Cookie over the network to misuse the product.
Confidential information can be exposed externally. 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-107228" on the vendor's site.

CVE-2026-107228 (org.asynchttpclient:async-http-client) — CWE-287 / CVSS v3 6.8
Attack vector: remote (network-reachable) / no user interaction
Attack surface: Cookie / setHeader / addHeader / addCookie
Patched: 3.0.14 — apply immediately
Workaround: Where requests carry per-user cookies, use a separate client per user, or disable the cookie store with setCookieStore(null).
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.

❓ What is the problem

Authentication bypass (CWE-287) exists in org.asynchttpclient:async-http-client. Attackers reach the vulnerable code path via Cookie.

📍 Affected scope

Check the vendor advisory for the affected versions of org.asynchttpclient:async-http-client. Attack surface: Cookie / setHeader / addHeader / addCookie.

🔥 Severity

Severity: Medium (CVSS 6.8/10). Confidential information can be exposed externally.

🔧 How to fix

Update to 3.0.14.

🛡️ Workaround

Workaround: Where requests carry per-user cookies, use a separate client per user, or disable the cookie store with setCookieStore(null).

🔍 Detection

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

  1. 1
    Identify exposure identify 
    Audit SBOM/dependencies for affected components.

    資産台帳・SBOM・依存マニフェストで org.asynchttpclient:async-http-client を使っているサービスとバージョンを洗い出す。

  2. 2
    Apply temporary workaround mitigate 
    Where requests carry per-user cookies, use a separate client per user, or disable the cookie store with `setCookieStore(null)`.

    パッチが適用されるまでの応急処置として、Where requests carry per-user cookies, use a separate client per user, or disable the cookie store with setCookieStore(null). を実施。回避策の副作用 (機能低下) を確認した上で。

  3. 3
    Apply patch patch 
    Upgrade org.asynchttpclient:async-http-client to 3.0.14

    ステージング環境で 3.0.14 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスを含めること。

  4. 4
    Post-deployment verification verify 
    Confirm patched version is live in production

    パッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番ではアクセスログ・WAF でアラート再発が無いか継続監視。

Affected packages

maven org.asynchttpclient:async-http-client
[{"type":"ECOSYSTEM","events":[{"introduced":"2.1.0"},{"last_affected":"2.16.1"}]}]

Fix status by distribution

Fixed packages published by each distribution for this CVE

References

We use cookies for analytics and ad measurement. This setting applies to all Game co., Ltd. sites. Details