CWE-1325Base

Improperly Controlled Sequential Memory Allocation

Incomplete in the CWE catalog · 23 CVEs mapped

23
CVEs mapped
5.7
Median CVSS
What it is

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.

Recent examples
8.1cvss
CVE-2026-109619

CVE-2026-109619 - HIGH Severity Vulnerability

PHP has various global state that temporarily points into request memory. In some scenarios, global state may not be correctly reset, or may be repopulated after being reset. The global state may then refer to request memory even after it has been freed. Subsequent requests may read or branch on this stale state before it is fully initialized. Multiple strategies can trigger this condition and produce remote code execution (RCE).

HIGHno explanation yet
6%
epss
9.8cvss
CVE-2026-109618

CVE-2026-109618 - CRITICAL Severity Vulnerability

PHP uses longjmp() for out-of-memory (OOM) errors to exit the current context and abort handling of the request. Some contexts may not properly account for this scenario and leave request memory in an uninitialized state before performing an allocation. The subsequent request cleanup procedure may read or branch on this memory. Multiple OOM strategies can consistently trigger this condition and lead to remote code execution (RCE).

CRITICALno explanation yet
5%
epss
5.3cvss
CVE-2026-92707

CVE-2026-92707 - MEDIUM Severity Vulnerability

MessagePack for C# is a MessagePack serializer for C#. Prior to 2.5.303 and 3.1.9, deserializing attacker-controlled MessagePack data as System.Object through PrimitiveObjectFormatter can cause excessive memory allocation. The formatter allocates an object[] from each declared array length before the configured object-graph depth limit rejects the input, while nested array headers can reuse the same trailing unread bytes to satisfy per-header length validation. A comparatively small payload can therefore keep many large arrays alive at once. When an attacker can submit such data repeatedly, the allocations can cause severe managed-heap pressure, excessive garbage collection, process termination, or loss of service. Exposure requires an application to deserialize untrusted data through the affected formatter path and permit repeated attacker-controlled submissions, such as a reachable ASP.NET Core SignalR hub method with an object parameter and AddMessagePackProtocol() enabled. This issue is fixed in versions 2.5.303 and 3.1.9.

MEDIUMno explanation yet
1%
epss
The record
Technical detail
CWE ID
CWE-1325
Abstraction
Base
Structure
Simple
Status
Incomplete