← Back
CVE-2026-54399
high
CVSS 7.5
Vulnerability in org.apache.httpcomponents.core5:httpcore5 (CVE-2026-54399)
Summary
vulnerability in org.apache.httpcomponents.core5:httpcore5 (CVE-2026-54399). Risk of unauthorized operations or information disclosure. Mitigation: upgrade to `5.5-beta2` or later.
AI summary snake-internal / snake-material-v2
A vulnerability tracked as **CVE-2026-54399** has been found in org.apache.httpcomponents.core5:httpcore5.
Risk of unauthorized operations or information disclosure. CVSS score: 7.5/10.
What to do: upgrade org.apache.httpcomponents.core5:httpcore5 to **5.5-beta2** or later.
If unsure, ask your IT team or search "org.apache.httpcomponents.core5:httpcore5 CVE-2026-54399" on the vendor's site.
CVE-2026-54399 (org.apache.httpcomponents.core5:httpcore5) — CWE-400 / CVSS v3 7.5
Attack vector: remote (network-reachable) / unauthenticated / no user interaction
Patched: `5.5-beta2` — 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-400) exists in org.apache.httpcomponents.core5:httpcore5.
📍 Affected scope
org.apache.httpcomponents.core5:httpcore5 — .
🔥 Severity
Severity: High (CVSS 7.5/10). Risk of unauthorized operations or information disclosure
🔧 How to fix
Update to **5.5-beta2**.
🛡️ 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.apache.httpcomponents.core5:httpcore5' .` 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.apache.httpcomponents.core5:httpcore5' . | grep -v node_modulesリポジトリと本番環境の依存ファイル (package-lock.json / requirements.txt / go.sum / Gemfile.lock 等) で `org.apache.httpcomponents.core5:httpcore5` を grep し、稼働しているサービス・バージョンを把握する。
-
6Apply patch patch
Upgrade org.apache.httpcomponents.core5:httpcore5 to 5.5-beta2ステージング環境で 5.5-beta2 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスと、Step 3 で見つけた異常検知の続報チェックを含めること。
-
7Post-deployment verification verify
Confirm patched version is live in productionパッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番では Step 3 と同じログクエリでアラート再発が無いか継続監視。
Affected packages
maven
org.apache.httpcomponents.core5:httpcore5
[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.5-beta2"}]}]
References
- web https://nvd.nist.gov/vuln/detail/CVE-2026-54399
- web https://lists.apache.org/thread/zmxh1pl2zohov5ntdh4lt85gfrlchgpy
- web http://www.openwall.com/lists/oss-security/2026/07/01/4
- web https://github.com/advisories/GHSA-hf6x-8p5f-cgmf
- web https://github.com/apache/httpcomponents-core/commit/d96a00fec9b2e19f8005e35681df5f6cd6e21a9e
- web https://github.com/apache/httpcomponents-core/commit/fdc53a32fe0fccf098cc67e71cd125e447c759ed