Skip to main content
Meet us at Black Hat USA 2026— Las Vegas, August 1–6Book a Meeting
Mallory
High

Memory exhaustion DoS in Apache HttpComponents Core HTTP/1.1 message parser

IdentifiersCVE-2026-54399CWE-400· Uncontrolled Resource Consumption

CVE-2026-54399 is an uncontrolled resource consumption vulnerability in the HTTP/1.1 message parser of Apache HttpComponents Core. In affected versions, the default parser configuration permits processing of HTTP/1.1 messages containing an excessive number of headers or excessively long header lines without adequate resource limiting. A remote attacker can send crafted HTTP requests or responses that force the parser to consume excessive memory while handling header data, resulting in denial of service. The issue affects Apache HttpComponents Core 5.4.2 and earlier, and 5.5-beta1 and earlier.

Share:
For your environment

Are you exposed to this one?

Mallory correlates every CVE against your assets, your vendors, and active adversary campaigns. Know which vulnerabilities matter for you, not just which ones are loud.

ANALYST BRIEF

Impact, mitigation & remediation

What it means. What to do now. Patch path, mitigations, and the assume-compromise checklist.

Impact

What an attacker gets, and what they’ve been doing with it.

Successful exploitation allows a remote unauthenticated attacker to exhaust memory in an application using the vulnerable Apache HttpComponents Core HTTP/1.1 parser, causing denial of service. The primary impact described is service disruption due to memory exhaustion; no evidence was provided of code execution, privilege escalation, or data exposure.

Mitigation

If you can’t patch tonight, do this now.

Until patched releases are deployed, reduce exposure by enforcing strict limits on HTTP header count and maximum header line size at upstream components such as reverse proxies, load balancers, API gateways, or application-layer firewalls, and avoid using default parser settings that permit unbounded header processing where configurable.

Remediation

Patch, then assume compromise.

Upgrade Apache HttpComponents Core to a fixed release newer than 5.4.2 in the 5.4.x branch and newer than 5.5-beta1 in the 5.5 branch once an official patched version is available from Apache.
PUBLIC EXPLOITS

Exploits

No public exploits tracked yet. Mallory keeps watching.

VALID 0 / 0 TOTALView more in app

No public exploit code observed for this vulnerability.

EXPOSURE SURFACE

Affected products & vendors

Products and vendors Mallory has correlated with this vulnerability. Open in Mallory to drill down to specific CPE configurations and version ranges.

VendorProductType
Apache Software FoundationHttpcomponents Coreapplication

Vendor-confirmed product mapping. Mallory continuously reconciles this list against your asset inventory.

ACTIVITY FEED

Recent activity

9 sources tracked across advisories and community write-ups. News coverage will land here when it surfaces.

No news coverage yet. Advisories and community discussion only.

What this page doesn’t show

The version that knows your environment.

This page is what’s public. Mallory adds the parts that aren’t: which of your assets are affected, which adversaries are exploiting it right now, which detections to deploy, and what to do tonight.
Exposure mapping

Query your assets running an affected version, and investigate the blast radius.

Threat actor evidence

Every observed campaign linking this CVE to a named adversary.

Associated malware

Malware families riding this exploit, with evidence and IOCs.

Detection signatures

YARA, Sigma, Snort, and vendor rules, auto-deployed to your SIEM.

Vendor-by-vendor mapping

Cross-references every affected SKU, including bundled OEM variants.

Social activity9

Community discussion across Reddit, Mastodon, and other social sources.