CWE · MITRE source
CWE-1325Improperly Controlled Sequential Memory Allocation
The product manages a group of objects or resources and performs a separate memory allocation for each object, but it does not properly limit the total amount of memory that is consumed by all of the combined objects.
While the product might limit the amount of memory that is allocated in a single operation for a single object (such as a malloc of an array), if an attacker can cause multiple objects to be allocated in separate operations, then this might cause higher total memory consumption than the developer intended, leading to a denial of service.
Last updated: 04 July 2026 00:28 UTC
Cumulative inbound coverage
How completely the frameworks we cross-walk collectively cover this — the verdict is the strongest single mapping (overlapping partials are not summed); breadth shows the corroboration behind it.
Collective: mostly · 4 mapping(s) from 3 framework(s): ATT&CK 2 (mostly) · CAPEC 1 (partial) · ASVS 5.0 1 (partial)
NIST 800-53 r5 controls that address this weakness (0)AI
| Control | Title | Family | Why it addresses this CWE |
|---|---|---|---|
| No NIST controls proposed yet. | |||
MITRE ATT&CK techniques this weakness enables
Our own two-way CWE↔ATT&CK cross-walk — a direct mapping with no public source (the CWE→CAPEC→ATT&CK chain leaves most top weaknesses, incl. XSS and SQLi, mapped to nothing). Drafted by Grok and spot-checked by Claude Opus 4.8.
Direction: ← other covers this;
→ this covers other (F/M/P = full / mostly /
partial).
Top CVEs of this weakness type, ranked by Risk Priority
| CVE | Risk | CVSS | EPSS | Published |
|---|---|---|---|---|
CVE-2024-2511 UPD | 8.0 | 5.9 | 0.5403 | 2024-04-08 |
CVE-2021-43174 | 5.5 | 7.5 | 0.0117 | 2021-11-09 |
CVE-2023-3341 | 5.5 | 7.5 | 0.0263 | 2023-09-20 |
CVE-2024-27796 | 5.5 | 7.8 | 0.0026 | 2024-05-14 |
CVE-2025-2240 | 5.5 | 7.5 | 0.0091 | 2025-03-12 |
CVE-2026-34183 UPD | 5.5 | 7.5 | 0.0051 | 2026-06-09 |
CVE-2023-28968 | 3.5 | 5.3 | 0.0056 | 2023-04-17 |
CVE-2024-27804 | 3.5 | 5.5 | 0.0132 | 2024-05-14 |
CVE-2023-52891 | 3.5 | 5.3 | 0.0046 | 2024-07-09 |
CVE-2025-13945 | 3.5 | 5.5 | 0.0013 | 2025-12-03 |
CVE-2026-3201 | 3.5 | 4.7 | 0.0018 | 2026-02-25 |
CVE-2026-6533 | 3.5 | 5.5 | 0.0015 | 2026-04-30 |
CVE-2026-6869 | 3.5 | 5.5 | 0.0013 | 2026-04-30 |
CVE-2026-6535 | 3.5 | 5.5 | 0.0014 | 2026-04-30 |
CVE-2026-6867 | 3.5 | 5.5 | 0.0012 | 2026-04-30 |
CVE-2026-8199 UPD | 3.5 | 6.5 | 0.0026 | 2026-05-13 |