Sign in Sign up
JA · EN · FR
SecPulse
Categories
CVE-2026-107230 high CVSS 7.4

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

Summary

Vulnerability in org.asynchttpclient:async-http-client (CVE-2026-107230). Confidential information can be exposed externally. Exploitable via SpnegoEngine. Mitigation: upgrade to 3.0.14 or later.

Original description

The description as published by the source.

Impact

The fix for GHSA-vvp4-63h8-v5pm in 3.0.13 folded the authenticated principal into the HTTP/1.1 connection pool key, so that a connection one principal authenticated with NTLM, Kerberos or SPNEGO is not handed to another. It left three cases out. In each, a socket that one identity authenticated can still be drawn by a request belonging to a different identity, and the server serves that request as the first one.

  1. A login with no configured principal. Kerberos and SPNEGO against the ticket cache or the default JAAS login, which is the usual deployment, leave the realm's principal unset, and the key stayed unscoped in that case. A request to the same host that carries no credentials at all draws the authenticated socket and is served as the service identity.
  2. The proxy realm. Only the origin realm went into the key. A connection authenticated to a proxy with NTLM or Negotiate is handed to requests of another proxy identity, or of none, and the proxy acts for them as the first identity.
  3. Identities that share a user name. Only the principal string went into the key, so CORP\alice and OTHER\alice shared connections, as did two realms differing only in password, login context, keytab or service principal. The Kerberos login cache in SpnegoEngine had the same collision, and it was an unsynchronised map, so concurrent first use could hand one caller's login to another.

Who is Impacted

Applications that authenticate with NTLM, Kerberos or SPNE…

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-107230 has been found in org.asynchttpclient:async-http-client.
Attackers can target a specific entry point like SpnegoEngine over the network to misuse the product.
Confidential information can be exposed externally. CVSS score: 7.4/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-107230" on the vendor's site.

CVE-2026-107230 (org.asynchttpclient:async-http-client) — CWE-346 / CVSS v3 7.4
Attack vector: remote (network-reachable) / unauthenticated / no user interaction
Attack surface: SpnegoEngine / AsyncHttpClient
Patched: 3.0.14 — 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-346) exists in org.asynchttpclient:async-http-client. Attackers reach the vulnerable code path via SpnegoEngine without authentication.

📍 Affected scope

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

🔥 Severity

Severity: High (CVSS 7.4/10). Confidential information can be exposed externally.

🔧 How to fix

Update to 3.0.14.

🛡️ 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.14

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

  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":"2.0.0"},{"last_affected":"2.16.1"}]}]

References

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