CWE-1325: Stack Exhaustion
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.
Also known as Improperly Controlled Sequential Memory Allocation.
A kind of CWE-770 Allocation of Resources Without Limits or Throttling.
From the CWE List. © The MITRE Corporation.
Newest
- php, paloaltonetworks pan-os, panorama virtual appliance +111 more +113 more RCE via stale global state 9.2 Critical
- php, paloaltonetworks pan-os, panorama virtual appliance +110 more +112 more RCE via OOM corruption 9.2 Critical
-
Microsoft.AspNetCore.SignalR.Protocols.MessagePackNuGet Microsoft Security Advisory CVE-2026-92707 - ASP.NET Core Denial of Service Vulnerability 5.3 Medium - messagepack-csharp MessagePack: Nested arrays can blow past buffer length limits 5.3 Medium
- wireshark Improperly Controlled Sequential Memory Allocation in Wireshark 5.5 Medium
- mermaid-js mermaid Mermaid XY Charts are vulnerable to an infinite loop DoS 5.3 Medium
- samsung rlottie Improper input validation vulnerability in Samsung Open Source rlottie allows Oversized... 6.5 Medium
- verapdf verapdf-parser veraPDF Parser DoS via PostScript Type 1 Font Programs 6.9 Medium
- verapdf verapdf-parser veraPDF Parser DoS via PostScript CMap Streams 6.9 Medium
- mongodb server, mongodb, mongodb, inc. mongodb server +2 more A user with read access can cause a DoS by executing a specifically crafted query to consume a large amount of RAM 7.1 High
- guzzle guzzlehttp/guzzle before 7.15.1 Unbounded Cookie Denial of Service 6.9 Medium
- openssl Unbounded Memory Growth in the QUIC PATH_CHALLENGE Handler 7.5 High
- mongodb, mongodb, inc. mongodb server +1 more Post-auth memory exhaustion via bitwise match expressions 7.1 High
- wireshark Improperly Controlled Sequential Memory Allocation in Wireshark 5.5 Medium
- wireshark Improperly Controlled Sequential Memory Allocation in Wireshark 5.5 Medium
- wireshark Improperly Controlled Sequential Memory Allocation in Wireshark 5.5 Medium
- wireshark Improperly Controlled Sequential Memory Allocation in Wireshark 5.5 Medium
-
Meridian.MappingNuGet,Meridian.MediatorNuGet +1 more Meridian: Multiple defense-in-depth gaps (collection/depth caps, telemetry, retry, fan-out) 7.5 High - wireshark Improperly Controlled Sequential Memory Allocation in Wireshark 4.7 Medium
- foxinmy weixin4j An out-of-memory (OOM) issue in foxinmy/weixin4j 6.3 Medium
- wireshark Improperly Controlled Sequential Memory Allocation in Wireshark 5.5 Medium
- red hat build of apache camel 4.8 for quarkus 3.15, build of apache camel 4.8.5 for spring boot, build of apicurio registry 2 +8 more +10 more Smallrye-fault-tolerance: smallrye fault tolerance 7.5 High
- siemens simatic energy manager basic, simatic energy manager pro, simatic ipc diagbase +3 more +5 more A vulnerability has been identified in SIMATIC Energy Manager Basic (All versions < V7.5),... 5.3 Medium
- apple ipados, macos, ios and ipados +2 more +4 more The issue was addressed with improved checks. This issue is fixed in iOS 17.5 and iPadOS 17.5,... 7.8 High
- apple ipados, macos, tvos +5 more +7 more The issue was addressed with improved memory handling. This issue is fixed in iOS 17.5 and iPadOS... 5.5 Medium
- openssl, debian linux, netapp 500f firmware +79 more +81 more Unbounded memory growth with session handling in TLSv1.3 5.9 Medium
- isc bind, bind 9, debian linux +1 more +3 more A stack exhaustion flaw in control channel code may cause named to terminate unexpectedly 7.5 High
- juniper jdpi-decoder engine, junos, juniper networks junos os +1 more +3 more Junos OS: SRX Series: Policies that rely on JDPI-Decoder actions may fail open 5.3 Medium
- nlnet labs routinator, debian linux +1 more gzip transfer encoding caused out-of-memory crash 7.5 High