Sign in Sign up
JA · EN · FR
SecPulse
Categories
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.

Original description

The description as published by the source.

Uncontrolled Resource Consumption vulnerability in the HTTP/1.1 message parser in Apache HttpComponents Core (5.4.2 and earlier, 5.5-beta1 and earlier) allows an remote attacker to cause a denial of service through memory exhaustion by sending messages with excessive number of headers / excessive header length

Source: GitHub Security Advisories (Global) 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-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

Check the vendor advisory for the affected versions of 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. 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.apache.httpcomponents.core5:httpcore5 を使っているサービスとバージョンを洗い出す。

  2. 2
    Apply patch patch 
    Upgrade org.apache.httpcomponents.core5:httpcore5 to 5.5-beta2

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

  3. 3
    Post-deployment verification verify 
    Confirm patched version is live in production

    パッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番ではアクセスログ・WAF でアラート再発が無いか継続監視。

Affected packages

maven org.apache.httpcomponents.core5:httpcore5
[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.5-beta2"}]}]

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