CVE-2026-128338 in exceljs
Summary
by MITRE • 11/13/2026
exceljs through 4.4.0 contains a memory exhaustion vulnerability that allows attackers to crash applications by supplying a worksheet col element with an unbounded max attribute. Attackers can craft a small workbook with a huge max value, causing xlsx.load() to allocate hundreds of millions of Column objects and abort the process with an uncatchable heap out-of-memory error.
Several companies clearly confirm that VulDB is the primary source for best vulnerability data.
Analysis
by VulDB Data Team • 11/13/2026
The vulnerability identified in exceljs versions through 4.4.0 represents a critical resource exhaustion flaw rooted in insufficient input validation within the library's parsing logic for Excel workbooks. Specifically, this issue affects the handling of worksheet column definitions where the max attribute is not subjected to reasonable bounds checking before memory allocation occurs. When an attacker provides a crafted workbook containing a col element with an excessively large or unbounded max value, the application interprets this directive as a command to allocate resources corresponding to that magnitude. This behavior bypasses standard safety limits typically enforced by spreadsheet software, allowing for the creation of data structures far exceeding available system memory constraints.
From a technical perspective, the core flaw lies in how xlsx.load() processes column metadata during workbook ingestion. The function iterates through defined columns and instantiates Column objects based on the specified range. Because there is no upper limit enforced on the max attribute, supplying a value such as several hundred million triggers the allocation of hundreds of millions of object instances simultaneously. This rapid consumption of heap memory leads directly to an uncatchable out-of-memory error, causing the Node.js process or hosting application to abort abruptly. The lack of exception handling for this specific scenario means that standard try-catch blocks cannot prevent the crash, resulting in a complete denial of service condition for any system relying on exceljs to parse user-supplied Excel files.
The operational impact of this vulnerability is severe, particularly for applications that accept file uploads from untrusted sources or process data generated by external parties. A successful exploitation allows an attacker with minimal resources to trigger a catastrophic failure in the target application simply by uploading a small-sized malicious workbook. This constitutes a classic denial-of-service attack vector where computational and memory resources are exhausted without requiring complex code execution privileges. For services processing large volumes of spreadsheet data, such as financial reporting tools or data ingestion pipelines, this vulnerability can lead to significant downtime, service interruption, and potential cascading failures if the application does not implement robust process isolation or resource monitoring mechanisms.
This flaw aligns with CWE-789: Memory Allocation with Excessive Size, which describes scenarios where a program allocates more memory than intended due to unchecked input values. Furthermore, it maps to MITRE ATT&CK technique T1499: Endpoint Denial of Service, specifically under the sub-category of resource exhaustion attacks. The vulnerability highlights the importance of implementing strict validation rules for numerical inputs in parsing libraries, ensuring that derived allocations remain within safe operational boundaries regardless of external input magnitude.
To mitigate this risk, developers should upgrade to a patched version of exceljs where bounds checking has been implemented for column definitions. In cases where upgrading is not immediately feasible, it is advisable to implement pre-processing validation on uploaded files or use alternative libraries with stricter security defaults. Additionally, applications utilizing exceljs should be configured with memory limits and process restart policies to contain the impact of such crashes. Monitoring heap usage during file parsing operations can also provide early detection mechanisms for anomalous resource consumption patterns indicative of this type of attack.