Sign in Sign up
JA · EN · FR
SecPulse
Categories
CVE-2026-55688 medium CVSS 4.0

Vulnerability in org.asynchttpclient:async-http-client (CVE-2026-55688)

Summary

Vulnerability in org.asynchttpclient:async-http-client (CVE-2026-55688). Risk of unauthorized operations or information disclosure. Exploitable via ThreadSafeCookieStore. Mitigation: upgrade to 3.0.11 or later.

Original description

The description as published by the source.

Impact

A cookie tossing / cookie injection issue (CWE-1275). ThreadSafeCookieStore stored a cookie under the value of its Domain attribute without verifying that the responding host is allowed to set a cookie for that domain (RFC 6265 §5.3 step 6). A host the client connects to can therefore plant a cookie scoped to an unrelated domain, and the client will then send that cookie on later requests to that domain.

Who is Impacted

Applications that use a single AsyncHttpClient instance - and thus the default, shared CookieStore - to reach both an attacker-influenced host and a trusted host. Typical exposure: crawlers, link-preview / webhook fetchers, SSRF-style "fetch this URL" features, multi-backend aggregators, or following redirects to an attacker-controlled host. The attacker can write a cookie the client presents to the victim host (session fixation, overwriting a session id / CSRF-token cookie); they cannot read the victim host's cookies. Applications that talk only to a fixed trusted backend, or that disable/scope the cookie store, are not exposed.

Patches

Fixed in 3.0.11 and 2.16.0

Workarounds

  • Disable the cookie store (setCookieStore(null)) when cookies are not needed; or
  • Use a separate AsyncHttpClient (separate cookie store) per trust domain so an attacker-influenced host and a trusted host never share a jar
  • Supply a custom CookieStore whose add(Uri, Cookie) rejects cookies whose Domain is not domain-matched by the request h…

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-55688 has been found in org.asynchttpclient:async-http-client.
Attackers can target a specific entry point like ThreadSafeCookieStore over the network to misuse the product.
Risk of unauthorized operations or information disclosure. CVSS score: 4.0/10.
What to do: upgrade org.asynchttpclient:async-http-client to 3.0.11 or later.
If unsure, ask your IT team or search "org.asynchttpclient:async-http-client CVE-2026-55688" on the vendor's site.

CVE-2026-55688 (org.asynchttpclient:async-http-client) — CWE-1275 / CVSS v3 4.0
Attack vector: remote (network-reachable) / unauthenticated / no user interaction
Attack surface: ThreadSafeCookieStore / Domain / AsyncHttpClient / CookieStore
Patched: 3.0.11 — apply immediately
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

A vulnerability (CWE-1275) exists in org.asynchttpclient:async-http-client. Attackers reach the vulnerable code path via ThreadSafeCookieStore without authentication.

📍 Affected scope

Check the vendor advisory for the affected versions of org.asynchttpclient:async-http-client. Attack surface: ThreadSafeCookieStore / Domain / AsyncHttpClient / CookieStore.

🔥 Severity

Severity: Medium (CVSS 4.0/10). Risk of unauthorized operations or information disclosure.

🔧 How to fix

Update to 3.0.11.

🛡️ Workaround

Until the patch is applied: disable the affected feature, apply WAF rules, or restrict access via network ACLs.

🔍 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 patch patch 
    Upgrade org.asynchttpclient:async-http-client to 3.0.11

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

  3. 3
    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":"0"},{"fixed":"2.16.0"}]}]

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