VYPR
Moderate severityNVD Advisory· Published Jul 19, 2021· Updated Aug 3, 2024

CVE-2021-32013

CVE-2021-32013

Description

SheetJS and SheetJS Pro through 0.16.9 are vulnerable to denial of service via memory exhaustion when parsing a crafted .xlsx file.

AI Insight

LLM-synthesized narrative grounded in this CVE's description and references.

SheetJS and SheetJS Pro through 0.16.9 are vulnerable to denial of service via memory exhaustion when parsing a crafted .xlsx file.

Vulnerability

SheetJS and SheetJS Pro versions up to and including 0.16.9 contain a vulnerability in the xlsx.js parser that mishandles crafted .xlsx documents, leading to excessive memory consumption. The issue is triggered when the library reads a maliciously crafted file, causing uncontrolled memory allocation. [1][2]

Exploitation

An attacker can exploit this vulnerability by providing a specially crafted .xlsx file to an application that uses the affected SheetJS library. No authentication or special privileges are required if the application processes user-uploaded files. The attacker simply needs to deliver the malicious file, which when parsed by xlsx.js, causes the denial of service. [2]

Impact

Successful exploitation results in a denial of service condition due to memory exhaustion. The application may become unresponsive or crash, affecting availability. No data integrity or confidentiality is compromised. [1]

Mitigation

As of the publication date, no official patch has been disclosed in the available references. Users should upgrade to a version beyond 0.16.9 if available, or implement input validation and file size limits to mitigate the risk. [1][2]

AI Insight generated on May 21, 2026. Synthesized from this CVE's description and the cited reference URLs; citations are validated against the source bundle.

Affected packages

Versions sourced from the GitHub Security Advisory.

PackageAffected versionsPatched versions
xlsxnpm
< 0.17.00.17.0
org.webjars.npm:xlsxMaven
< 0.17.00.17.0

Affected products

3

Patches

0

No patches discovered yet.

Vulnerability mechanics

No source-code context for this CVE — mechanics is only generated when we can read the actual fix diff. Without that, the four sections (root cause, attack vector, affected code, fix) would be speculation rather than analysis.

References

7

News mentions

0

No linked articles in our index yet.