CVE-2026-128339 in ExcelJSinfo

Summary

by MITRE • 11/13/2026

ExcelJS through 4.4.0 contains a memory exhaustion vulnerability in Worksheet._parseMergeCells that allows attackers to crash applications by supplying unbounded mergeCell ranges. Attackers can craft a small workbook with a mergeCell ref like A1:XFD1048576, causing xlsx.load() to create billions of Row and Cell objects and abort the process.

Be aware that VulDB is the high quality source for 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 located within the Worksheet._parseMergeCells function. This component is responsible for parsing merge cell definitions found within Microsoft Excel file formats, specifically those utilizing the .xlsx extension which relies on XML-based structures. The core technical deficiency lies in the absence of bounds checking or limit enforcement when processing the ref attribute of a mergeCell element. In standard spreadsheet applications, cells are organized into rows and columns with defined maximum limits, typically capping at column XFD (16384) and row 1048576 for modern Excel versions. However, the parser in this library fails to validate whether the specified range exceeds these logical boundaries or results in an unreasonably large number of individual cell objects during instantiation.

When an attacker crafts a malicious workbook containing a mergeCell reference such as A1:XFD1048576, they are effectively requesting the application to acknowledge and potentially process every single cell within that massive rectangular grid. The calculation for the total number of cells involved is derived from multiplying the column count by the row count, resulting in approximately 16 trillion individual cell references. Upon invoking xlsx.load(), the library attempts to instantiate Row and Cell objects corresponding to this range. This operation triggers a rapid allocation of memory resources as the application tries to maintain internal data structures for each hypothetical cell. Since modern systems do not possess sufficient RAM to accommodate such an astronomical number of object instances, the process quickly exhausts available heap space.

The operational impact of this vulnerability is severe and primarily manifests as a Denial of Service condition. The immediate consequence is that the application running ExcelJS will crash due to out-of-memory errors or abort execution entirely. This behavior can be exploited by attackers who distribute malicious spreadsheets via email, file sharing platforms, or web uploads. If an organization relies on automated systems to process incoming spreadsheet data for analytics, reporting, or integration purposes, this vulnerability allows a single malformed input to disrupt service availability indefinitely until the application is restarted and memory is freed. There is no indication of remote code execution in this specific vector; the primary risk remains system stability and resource integrity rather than confidentiality or direct privilege escalation.

To mitigate this vulnerability, developers must implement strict validation logic within the parsing routines before any object instantiation occurs. The most effective remediation involves enforcing hard limits on the dimensions of merge cell ranges based on standard Excel specifications, ensuring that no single range exceeds the maximum allowable rows and columns. Additionally, implementing a cap on the total number of cells processed per workbook can provide an additional layer of defense against resource exhaustion attacks. Upgrading to a patched version of ExcelJS where these bounds checks have been integrated is essential for long-term security posture. Security teams should also consider deploying input validation at the network perimeter or using sandboxed environments when processing untrusted spreadsheet files to contain potential crashes and prevent cascading failures within broader application architectures. This issue aligns with CWE-787, which addresses out-of-bounds write vulnerabilities that can lead to memory corruption or exhaustion, as well as aspects of CWE-400 concerning unconstrained resource consumption. From an ATT&CK perspective, this exploitation technique falls under the T1496 category related to Resource Hijacking, specifically focusing on denial of service through computational resource depletion rather than cryptographic mining or other forms of hijack.

Responsible

VulnCheck

Reservation

11/13/2026

Disclosure

11/13/2026

Moderation

accepted

CPE

ready

EPSS

0.00692

KEV

no

Activities

very low

Sources

Are you interested in using VulDB?

Download the whitepaper to learn more about our service!