CVE-2026-107215
Received Received - Intake

Memory Allocation Flaw in Excelize Library

Publication date: 2026-10-07

Last updated on: 2026-10-07

Assigner: GitHub, Inc.

Description
Excelize is a Go language library for reading and writing Microsoft Excel spreadsheets. From 2.3.1 to 2.11.0, extractPart allocates a byte slice directly from an attacker-controlled CFB directory-entry size before validating the sector chain or size domain. extractPart trusts the CFB directory entry streamSize for EncryptionInfo and EncryptedPackage allocations before validating the stream. When a crafted OLE compound file declares a negative or extremely large EncryptionInfo or EncryptedPackage stream size, the declared size reaches make with a negative length or forces a multi-gigabyte allocation, allowing an attacker to panic or exhaust process memory. No fixed version is available as of this review.

CVSS Scores

EPSS Scores

Probability:
Percentile:

Meta Information

Published
2026-10-07
Last Modified
2026-10-07
Generated
2026-10-08
AI Q&A
2026-10-07
EPSS Evaluated
N/A
NVD
CVE-2026-107215
EUVD
EUVD-2026-94533

Affected Vendors & Products

Showing 1 associated CPE
Vendor Product Version / Range
qax-os excelize >= 2.3.1, <= 2.11.0

Helpful Resources

Exploitability

CWE
CWE Icon
KEV
KEV Icon
CWE ID Description
CWE-789 The product allocates memory based on an untrusted, large size value, but it does not ensure that the size is within expected limits, allowing arbitrary amounts of memory to be allocated.

Attack-Flow Graph

AI Quick Actions

Instant insights powered by AI
Executive Summary

CVE-2026-107215 is a denial-of-service vulnerability in the Excelize Go library affecting versions 2.3.1 to 2.11.0. The extractPart function allocates memory based on attacker-controlled CFB stream sizes without validation. This allows triggering a panic or memory exhaustion by specifying negative or extremely large sizes, causing makeslice errors or massive allocations from small files.

Detection Guidance

Detecting this vulnerability requires checking if your system uses vulnerable versions of the Excelize library (2.3.1 to 2.11.0). Inspect Go module dependencies for excelize and verify versions. No direct network detection commands exist, but monitoring for crashes or memory exhaustion during file processing may indicate exploitation.

Impact Analysis

An attacker could crash your application by uploading a maliciously crafted Excel file. This could lead to service disruption, process termination, or memory exhaustion in systems processing these files. The attack requires no authentication and can be executed remotely via network-based vectors.

Compliance Impact

This vulnerability primarily impacts availability by enabling denial-of-service attacks through memory exhaustion or process termination. While it does not directly expose or leak data, prolonged service disruption could violate compliance requirements for data availability in GDPR (Article 32) and HIPAA (Security Rule §164.312(a)(2)(ii)). Organizations processing sensitive data must ensure systems remain operational to meet these standards.

Mitigation Strategies

Upgrade to Excelize version 2.11.1 or later, which includes input validation for stream sizes. If upgrading is not possible, restrict file processing to trusted sources only and implement size limits for uploaded files. Monitor for crashes or memory exhaustion as potential signs of exploitation.

Chat Assistant

Ask questions about this CVE
Hi! I’m here to help you understand CVE-2026-107215. Ask me anything about the vulnerability, its impact, or mitigation strategies.
0/70

EPSS Chart