What is CWE-400?
The product does not properly control the allocation and maintenance of a limited resource.
CWE-400 is a class-level weakness in MITRE’s Common Weakness Enumeration, with a MITRE likelihood of exploit of High. Applicable platforms: Language: Not Language-Specific; Technology: Not Technology-Specific.
Source: MITRE CWE (CWE-400 definition, reproduced verbatim). Counts and linkage below are Threadlinqs data.
Consequences
- Availability — DoS: Crash, Exit, or Restart, DoS: Resource Consumption (CPU), DoS: Resource Consumption (Memory), DoS: Resource Consumption (Other). If an attacker can trigger the allocation of the limited resources, but the number or size of the resources is not controlled, then the most common result is denial of service. This would prevent valid users from accessing the product, and it could potentially have an impact on the surrounding environment, i.e., the product may slow down, crash due to unhandled errors, or lock out legitimate users. For example, a memory exhaustion attack against an application could slow down the application as…
- Access Control, Other — Bypass Protection Mechanism, Other. In some cases it may be possible to force the product to "fail open" in the event of resource exhaustion. The state of the product -- and possibly the security functionality - may then be compromised.
Source: MITRE CWE, common consequences.
How CWE-400 is exploited in the wild
Threadlinqs maps 92 CVEs to CWE-400, published between 2021-10-29 and 2026-11-11. 4 are listed in CISA’s Known Exploited Vulnerabilities catalog, the authoritative record of exploitation in the wild, and 2 are tied to ransomware campaigns. By CVSS v3 severity the set splits into 3 critical, 37 high, 38 medium, 3 low. The highest EPSS score in the set is 99.9% (CVE-2023-44487), the modelled probability of exploitation in the next 30 days. 79 tracked threats reference CWE-400 directly or through a CVE it covers; the most recent is “WordPress 7.1.5 Security Release: 20 Core Fixes Including Template Part Block Permission Flaw (Potential RCE) and SQL Injection in WP_Meta_Query / Customizer Previews” (2026-11-19). Affected products concentrate in Elastic (11), IBM (7), nodejs (7), among 56 vendors in total.
Vulnerabilities (CVEs)
Showing 40 of 92 CVEs mapped to CWE-400, CISA KEV first, then by CVSS score.
- CVE-2021-44228 — CISA KEV · CVSS 10 critical · EPSS 99.9% · published 2021-12-10
- CVE-2023-44487 — CISA KEV · CVSS 7.5 high · EPSS 99.9% · published 2023-10-10
- CVE-2026-28318 — CISA KEV · CVSS 7.5 high · EPSS 1.9% · published 2026-06-04
- CVE-2026-45498 — CISA KEV · CVSS 4 medium · EPSS 1.2% · published 2026-05-20
- CVE-2026-61186 — CVSS 9.4 critical · EPSS 0.4% · published 2026-07-21
- CVE-2026-55450 — CVSS 9.3 critical · EPSS 0.3% · published 2026-06-23
- CVE-2026-93441 — CVSS 8.6 high · EPSS 0.3% · published 2026-10-20
- CVE-2026-55266 — CVSS 7.8 high · EPSS 0.0% · published 2026-10-05
- CVE-2026-49160 — CVSS 7.5 high · EPSS 48.4% · published 2026-06-09
- CVE-2025-67779 — CVSS 7.5 high · EPSS 19.9% · published 2025-12-12
- CVE-2026-58627 — CVSS 7.5 high · EPSS 1.1% · published 2026-07-14
- CVE-2026-71360 — CVSS 7.5 high · EPSS 0.9% · published 2026-08-25
- CVE-2026-56819 — CVSS 7.5 high · EPSS 0.6% · published 2026-07-21
- CVE-2026-66299 — CVSS 7.5 high · EPSS 0.5% · published 2026-07-28
- CVE-2026-68763 — CVSS 7.5 high · EPSS 0.5% · published 2026-08-25
- CVE-2026-123865 — CVSS 7.5 high · EPSS 0.5% · published 2026-11-11
- CVE-2026-56846 — CVSS 7.5 high · EPSS 0.5% · published 2026-08-04
- CVE-2026-20356 — CVSS 7.5 high · EPSS 0.4% · published 2026-10-21
- CVE-2025-40944 — CVSS 7.5 high · EPSS 0.4% · published 2026-01-13
- CVE-2026-67861 — CVSS 7.5 high · EPSS 0.4% · published 2026-08-04
- CVE-2025-0114 — CVSS 7.5 high · EPSS 0.4% · published 2025-03-12
- CVE-2026-84375 — CVSS 7.5 high · EPSS 0.3% · published 2026-09-01
- CVE-2026-82397 — CVSS 7.5 high · EPSS 0.3% · published 2026-08-31
- CVE-2026-85443 — CVSS 7.5 high · EPSS 0.3% · published 2026-09-03
- CVE-2026-96580 — CVSS 7.5 high · EPSS 0.3% · published 2026-10-06
- CVE-2026-86344 — CVSS 7.5 high · EPSS 0.3% · published 2026-10-01
- CVE-2026-77384 — CVSS 7.5 high · EPSS 0.3% · published 2026-08-24
- CVE-2026-93879 — CVSS 7.5 high · EPSS 0.3% · published 2026-11-08
- CVE-2026-96146 — CVSS 7.5 high · EPSS 0.3% · published 2026-11-08
- CVE-2026-55446 — CVSS 7.5 high · EPSS 0.3% · published 2026-06-23
- CVE-2026-9071 — CVSS 7.5 high · EPSS 0.3% · published 2026-06-22
- CVE-2026-9675 — CVSS 7.5 high · EPSS 0.2% · published 2026-06-17
- CVE-2026-44435 — CVSS 7.5 high · EPSS 0.2% · published 2026-07-16
- CVE-2026-67864 — CVSS 7.5 high · EPSS 0.2% · published 2026-08-05
- CVE-2026-119283 — CVSS 7.5 high · EPSS 0.2% · published 2026-10-29
- CVE-2026-67862 — CVSS 7.5 high · EPSS 0.2% · published 2026-08-04
- CVE-2026-12151 — CVSS 7.5 high · published 2026-06-17
- CVE-2026-67978 — CVSS 7.5 high · published 2026-08-03
- CVE-2026-75095 — CVSS 7.5 high · published 2026-10-12
- CVE-2026-92596 — CVSS 7.5 high · published 2026-09-16
Affected vendors
- Elastic — 11 CVEs
- IBM — 7 CVEs
- nodejs — 7 CVEs
- Apache Software Foundation — 4 CVEs
- Microsoft — 3 CVEs
- Mozilla — 3 CVEs
- Siemens — 3 CVEs
- nodemailer — 3 CVEs
- vllm-project — 3 CVEs
- Gerrit — 2 CVEs
- authlib — 2 CVEs
- h2o — 2 CVEs
Threat activity
79 tracked threats cite CWE-400; the 25 most recent are listed.
- WordPress 7.1.5 Security Release: 20 Core Fixes Including Template Part Block Permission Flaw (Potential RCE) and SQL Injection in WP_Meta_Query / Customizer PreviewsHIGH
- DragonForce Ransomware Cartel Windows Payload Analysis (.df_win, ChaCha20/RSA-4096, ARP/SMB Discovery)HIGH
- Tor Releases Emergency Security Update 0.4.9.17 as Ongoing DDoS Attack Overwhelms Network RelaysHIGH
- Node.js November 2026 Security Releases Patch 16 Vulnerabilities (HTTP/2 crashes, HTTPS heap/TLS key leak CVE-2026-123864, TLS client-certificate auth bypass)HIGH
- BO Team (Black Owl) Supply Chain Attack Against a Software Developer's Infrastructure (CVE-2021-44228)HIGH
- Siemens SSA-364175: Multiple Vulnerabilities in Palo Alto Networks Virtual NGFW on RUGGEDCOM APE1808 (CVE-2024-3596, CVE-2025-4231 and others)CRITICAL
- OpenAI GPT-6 Cyber Identifies 81 Previously Unknown High-Severity Firefox Vulnerabilities (Mozilla MFSA2026-118, Firefox 159)HIGH
- CVE-2025-40944: Denial-of-Service Vulnerability in Siemens SIMATIC ET 200 Devices (SSA-674753)HIGH
- PHP2Shell (CVE-2026-109618/CVE-2026-109619) + Fragnesia (CVE-2026-46300) Chain Roots 25 Servers, Breaches U.S. Government-Affiliated NetworkCRITICAL
- Unit 42: Retail Peak Season Cyber Threats - Ransomware/Extortion, DDoS, Digital Skimming, Account Takeover and AI-Assisted Intrusion (CVE-2024-34102, CVE-2021-44228)HIGH
- Apache Kafka Unbounded Memory Allocation Zero-Days (CVE-2026-114349, CVE-2026-111551) — Compressed Batch Decoding and Kafka Streams DeserializersHIGH
- Tailscale 'Tailworm' Vulnerabilities (11 Findings in Tailscale SSH, App Connectors, Serve, DERP and Headscale) Allowing Root Privilege Escalation (Tailscale v1.104.2, Headscale v0.29.5)HIGH
- Multiple Vulnerabilities Fixed in Cisco Snort 3 (NCSC-2026-0450; CVE-2026-20043, CVE-2026-76524 and 11 others)CRITICAL
- Cisco patches 34 vulnerabilities across Expressway (CVE-2026-76466 RCE), Unified Communications, Snort 3, IOS XR and Secure ClientCRITICAL
- PHP Unpatched RCE CVE-2026-115560 Disclosed Two Days After Emergency PHP2Shell Patches (CVE-2026-109618/CVE-2026-109619)CRITICAL
- Operation Escaneo: MexicanMafia (PanchoVilla) Intrusion Campaign Against Mexican Government Agencies and Latin American Financial InstitutionsHIGH
- Splunk Enterprise / Splunk SOAR and SolarWinds Security Updates (CVE-2026-76299, CVE-2026-76302, CVE-2026-76531, CVE-2026-76407, CVE-2026-28328)CRITICAL
- Proxyjacking campaign hijacks 143+ edge devices in 34 countries (D-Link, Ubiquiti, SAP) to resell bandwidth via Pawns.app, plus active exploitation of PAN-OS CVE-2026-0322HIGH
- Bitdefender Threat Debrief June 2026: Ransomware Landscape (Qilin, The Gentlemen, DragonForce, KryBit) and Actively Exploited SolarWinds Serv-U Flaw CVE-2026-28318HIGH
- PHP pre-announces two critical RCE flaws in PHP core (CVE-2026-109618, CVE-2026-109619); emergency patches due 2026-10-21 after embargo leakCRITICAL
- skynox7: Proxyjacking Edge Devices Into Residential Proxies (D-Link ShareCenter CVE-2024-3272/3273, UniFi Video CVE-2021-44228, SAP NetWeaver CVE-2025-31324)HIGH
- IBM Langflow OSS Multiple Vulnerabilities Including Two Critical Unauthenticated RCE Flaws (CVE-2026-104334, CVE-2026-93674)CRITICAL
- Android October 2026 Security Bulletin - 25 Vulnerabilities Patched in Framework and System (Patch Level 2026-10-01)HIGH
- Elastic Patches 14 Security Flaws Including Kibana Cross-Tenant Data Interception (CVE-2026-102406)HIGH
- React Server Components DoS Vulnerability (CVE-2026-23870) Lets Attackers Freeze Next.js Servers With a Single POST RequestHIGH
Mitigations
- Architecture and Design: Design throttling mechanisms into the system architecture. The best protection is to limit the amount of resources that an unauthorized user can cause to be expended. A strong authentication and access control model will help prevent such attacks from occurring in the first place. The login application should be protected against DoS attacks as much as possible. Limiting the database access, perhaps by caching result sets, can help minimize the resources expended. To further limit the potential for a DoS attack, consider tracking the rate of requests received from users and blocking requests that exceed a defined rate threshold.
- Architecture and Design: Mitigation of resource exhaustion attacks requires that the target system either: recognizes the attack and denies that user further access for a given amount of time, or uniformly throttles all requests in order to make it more difficult to consume resources more quickly than they can again be freed. The first of these solutions is an issue in itself though, since it may allow attackers to prevent the use of the system by a particular valid user. If the attacker impersonates the valid user, they may be able to prevent the user from accessing the server in question. The second solution is simply difficult to effectively institute -- and even when properly done, it does not provide a full…
- Architecture and Design: Ensure that protocols have specific limits of scale placed on them.
- Implementation: Ensure that all failures in resource allocation place the system into a safe posture.
Source: MITRE CWE, potential mitigations.
Detection methods (MITRE CWE)
- Automated Static Analysis (effectiveness: Limited): Automated static analysis typically has limited utility in recognizing resource exhaustion problems, except for program-independent system resources such as files, sockets, and processes. For system resources, automated static analysis may be able to detect circumstances in which resources are not released after they have expired. Automated analysis of configuration files may be able to detect settings that do not specify a maximum value. Automated static analysis tools will not be appropriate…
- Automated Dynamic Analysis (effectiveness: Moderate): Certain automated dynamic analysis techniques may be effective in spotting resource exhaustion problems, especially with resources such as processes, memory, and connections. The technique may involve generating a large number of requests to the product within a short time frame.
- Fuzzing (effectiveness: Opportunistic): While fuzzing is typically geared toward finding low-level implementation bugs, it can inadvertently find resource exhaustion problems. This can occur when the fuzzer generates a large number of test cases but does not restart the targeted product in between test cases. If an individual test case produces a crash, but it does not do so reliably, then an inability to handle resource exhaustion may be the cause.
Source: MITRE CWE, detection methods. Threadlinqs detection rules for the threats above are Blue tier and higher.