Sign in Sign up
JA · EN · FR
SecPulse
Categories
CVE-2026-107280

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

Summary

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

Original description

The description as published by the source.

Impact

The cookie store decides whether a Domain attribute may be accepted using only the domain-matching rule of RFC 6265 Section 5.1.3, which asks whether the request host is the domain or ends with a dot followed by it. Section 5.3 step 5, which additionally requires rejecting a Domain that is a public suffix, is not implemented anywhere in the client.

So a host under a multi-label public suffix can set a cookie for the suffix itself, and the store then hands it to every other host under that suffix:

attacker.co.uk  ->  Set-Cookie: SID=attacker-value; Domain=co.uk; Path=/
bank.co.uk      ->  Cookie: SID=attacker-value

Domain=uk works the same way. The attacker needs only a site under the same suffix as the victim, which for suffixes such as co.uk, com.au, or github.io is trivially obtainable.

Depending on what the application does with the cookie, this is session fixation, or it overwrites a session the victim site set, or it lets the attacker plant a value the victim site trusts.

Affected versions

  • 3.x: up to and including 3.0.12
  • 2.x: up to and including 2.16.0

Relationship to CVE-2026-55688

CVE-2026-55688 (GHSA-m452-q8c9-rg2f) covered the direct form of this, where a host sets a Domain naming an unrelated host, and that form is genuinely fixed: attacker.co.uk can no longer set Domain=bank.co.uk, and this was verified as a control. What that fix did not add is the public suffix test, so setting Domain=co.uk still reaches `b…

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

CVE-2026-107280 (org.asynchttpclient:async-http-client) — CWE-1275
Attack surface: Domain / co.uk / com.au / github.io
Patched: 3.0.13 — apply immediately
Workaround: Do not share one CookieStore across origins that are not mutually trusted.
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 Domain.

📍 Affected scope

Check the vendor advisory for the affected versions of org.asynchttpclient:async-http-client. Attack surface: Domain / co.uk / com.au / github.io.

🔥 Severity

Severity: ?. Risk of unauthorized operations or information disclosure.

🔧 How to fix

Update to 3.0.13.

🛡️ Workaround

Workaround: Do not share one CookieStore across origins that are not mutually trusted.

🔍 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 
    Do not share one `CookieStore` across origins that are not mutually trusted.

    パッチが適用されるまでの応急処置として、Do not share one CookieStore across origins that are not mutually trusted. を実施。回避策の副作用 (機能低下) を確認した上で。

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

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

  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.0.0"},{"fixed":"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