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: 09 May 2026 03:25 UTC
NIST 800-53 r5 controls that address this weakness (0)AI
| Control | Title | Family | Why it addresses this CWE |
|---|---|---|---|
| No NIST controls proposed yet. | |||
Top CVEs of this weakness type, ranked by Risk Priority
| CVE | Risk | CVSS | EPSS | Published |
|---|---|---|---|---|
CVE-2024-27796 | 1.6 | 7.8 | 0.0005 | 2024-05-14 |
CVE-2021-43174 | 1.5 | 7.5 | 0.0072 | 2021-11-09 |
CVE-2023-3341 | 1.5 | 7.5 | 0.0025 | 2023-09-20 |
CVE-2025-2240 | 1.5 | 7.5 | 0.0034 | 2025-03-12 |
CVE-2024-2511 | 1.4 | 5.9 | 0.0415 | 2024-04-08 |
CVE-2024-27804 | 1.4 | 5.5 | 0.0419 | 2024-05-14 |
CVE-2023-28968 | 1.1 | 5.3 | 0.0050 | 2023-04-17 |
CVE-2023-52891 | 1.1 | 5.3 | 0.0012 | 2024-07-09 |
CVE-2025-13945 | 1.1 | 5.5 | 0.0003 | 2025-12-03 |
CVE-2026-6533 | 1.1 | 5.5 | 0.0001 | 2026-04-30 |
CVE-2026-6869 | 1.1 | 5.5 | 0.0001 | 2026-04-30 |
CVE-2026-6535 | 1.1 | 5.5 | 0.0001 | 2026-04-30 |
CVE-2026-6867 | 1.1 | 5.5 | 0.0001 | 2026-04-30 |
CVE-2026-3201 | 0.9 | 4.7 | 0.0003 | 2026-02-25 |
CVE-2026-24819 | 0.0 | 0.0 | 0.0002 | 2026-01-27 |