← Back
CVE-2026-45300
high
CVSS 7.4
Information Disclosure in org.asynchttpclient:async-http-client (CVE-2026-45300)
Summary
vulnerability in org.asynchttpclient:async-http-client (CVE-2026-45300). Confidential information can be exposed externally. Exploitable via ``Cookie``. Mitigation: upgrade to `2.15.0` or later.
AI summary snake-internal / snake-material-v2
A vulnerability tracked as **CVE-2026-45300** 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: 7.4/10.
What to do: upgrade org.asynchttpclient:async-http-client to **2.15.0** or later.
If unsure, ask your IT team or search "org.asynchttpclient:async-http-client CVE-2026-45300" on the vendor's site.
CVE-2026-45300 (org.asynchttpclient:async-http-client) — CWE-200 / CVSS v3 7.4
Attack vector: remote (network-reachable) / unauthenticated
Attack surface: `Cookie` / `Redirect30xInterceptor.java` / `Authorization` / `stripAuth`
Patched: `2.15.0` — 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
**information disclosure** (CWE-200) exists in org.asynchttpclient:async-http-client. Attackers reach the vulnerable code path via ``Cookie`` without authentication.
📍 Affected scope
org.asynchttpclient:async-http-client — . Attack surface: `Cookie` / `Redirect30xInterceptor.java` / `Authorization` / `stripAuth`.
🔥 Severity
Severity: High (CVSS 7.4/10). Confidential information can be exposed externally
🔧 How to fix
Update to **2.15.0**.
🛡️ 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. Run `grep -r 'org.asynchttpclient:async-http-client' .` against your dependency files (package-lock.json, requirements.txt, go.sum) to find affected services.
Response Actions (7 steps)
Concrete steps and command examples for SOC/SRE teams to execute in order
-
1Identify exposure identify
grep -r 'org.asynchttpclient:async-http-client' . | grep -v node_modulesリポジトリと本番環境の依存ファイル (package-lock.json / requirements.txt / go.sum / Gemfile.lock 等) で `org.asynchttpclient:async-http-client` を grep し、稼働しているサービス・バージョンを把握する。
-
6Apply patch patch
Upgrade org.asynchttpclient:async-http-client to 2.15.0ステージング環境で 2.15.0 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスと、Step 3 で見つけた異常検知の続報チェックを含めること。
-
7Post-deployment verification verify
Confirm patched version is live in productionパッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番では Step 3 と同じログクエリでアラート再発が無いか継続監視。
Affected packages
maven
org.asynchttpclient:async-http-client
[{"type":"ECOSYSTEM","events":[{"introduced":"2.0.0"},{"fixed":"2.15.0"}]}]
References
- advisory https://nvd.nist.gov/vuln/detail/CVE-2026-45300
- package https://github.com/AsyncHttpClient/async-http-client
- web https://github.com/AsyncHttpClient/async-http-client/security/advisories/GHSA-fmxf-pm6p-7xgm
- web https://github.com/AsyncHttpClient/async-http-client/commit/3b0e3e9e
- web https://github.com/AsyncHttpClient/async-http-client/releases/tag/async-http-client-project-3.0.10
- web https://github.com/advisories/GHSA-fmxf-pm6p-7xgm