CWE-789: Memory Allocation with Excessive Size Value
281 CVEs have CWE-789 as their primary weakness. 0 of them are in the CISA KEV catalog. The highest EPSS score among them is 89.885%.
The product allocates memory based on an untrusted, large size value, but it does not ensure that the size is within expected limits, allowing arbitrary amounts of memory to be allocated.
Child of CWE-770: Allocation of Resources Without Limits or Throttling
Mitigations
- Implementation Architecture and Design: Perform adequate input validation against any value that influences the amount of memory that is allocated. Define an appropriate strategy for handling requests that exceed the limit, and consider supporting a configuration option so that the administrator can extend the amount of memory to be used if necessary.
- Operation: Run your program using system-provided resource limits for memory. This might still cause the program to crash or exit, but the impact to the rest of the system will be minimized.
Observed examples
- CVE-2023-2253: Query capability for API endpoint allows a large value for number of records to return, leading to allocation of a large array
- CVE-2019-19911: Chain: Python library does not limit the resources used to process images that specify a very large number of bands (CWE-1284), leading to excessive memory consumption (CWE-789) or an integer overflow (CWE-190).
- CVE-2010-3701: program uses
- CVE-2008-1708: memory consumption and daemon exit by specifying a large value in a length field
- CVE-2008-0977: large value in a length field leads to memory consumption and crash when no more memory is available
- CVE-2006-3791: large key size in game program triggers crash when a resizing function cannot allocate enough memory
- CVE-2004-2589: large Content-Length HTTP header value triggers application crash in instant messaging application due to failure in memory allocation
Top released CVEs
KEV first, then the highest EPSS score, the highest CVSS score and the newest.
| CVE | Published | Severity | CVSS | EPSS | Description |
|---|---|---|---|---|---|
| CVE-2026-131844 | 2026-11-17 | MEDIUM | 6.5 | not scored | Poppler through 26.11.0 contains an uncontrolled memory allocation vulnerability in the libcurl-based remote file loader that trusts unvalidated HEAD… |
| CVE-2026-65167 | 2026-11-17 | MEDIUM | 5.5 | not scored | NVIDIA TensorRT contains a vulnerability where a user could cause memory allocation with excessive size value by crafting a malicious TRT engine. A successful… |
Get more CVE data from the API.
curl 'https://api.contrastcyber.com/cwe_lookup/CWE-789'curl 'https://api.contrastcyber.com/cve_search?cwe_id=CWE-789'
Sources
- Vulnerability data from the National Vulnerability Database (NIST) and the CVE Program. CVE records: Copyright © 1999-2026, The MITRE Corporation, used under the CVE Program Terms of Use. CVE® is a registered trademark of The MITRE Corporation.
- CWE definitions: Copyright © 2006-2026, The MITRE Corporation, used under the CWE Terms of Use. CWE is a trademark of The MITRE Corporation.
- EPSS scores by FIRST.org EPSS, used with attribution.
- KEV catalog and SSVC decisions by CISA.
- Advisory data from the GitHub Advisory Database through OSV.dev (CC BY 4.0).
- Exploit metadata from the Exploit Database (GPL-2.0-only, metadata only).
- Nuclei template names from nuclei-templates (MIT).