CVE-2026-107212: Excelize: Unbounded row number in Rows.Columns makes GetRows and the Rows iterator loop for days
Excelize is a Go language library for reading and writing Microsoft Excel spreadsheets. From 2.1.0 to 2.11.0, Rows.Columns accepts a look-ahead row number above TotalRows without applying the limit enforced by Rows.Next. File.GetRows relies on Rows.Next and Rows.Columns, but Rows.Columns consumes the row r attribute without the limit check in Rows.Next. When a crafted worksheet places an oversized row number after an ordinary valid row and the application calls GetRows or iterates Rows, the iterator advances through every missing row number instead of rejecting the workbook, allowing an attacker to consume a CPU core for an attacker-controlled duration. No fixed version is available as of this review.
Affected Software
Event History
Frequently Asked Questions
Which applications are exposed to this issue?
Applications using Excelize versions 2.1.0 through 2.11.0 are exposed when they call File.GetRows or iterate worksheet rows on attacker-controlled or otherwise untrusted Excel workbooks.
What must an attacker include in a workbook to trigger the denial of service?
The worksheet must contain an oversized row number after an ordinary valid row. When the application reads rows through GetRows or the Rows iterator, Excelize advances across the missing row numbers, consuming CPU for an attacker-controlled duration.
Is a fixed Excelize version available?
No fixed version was available as of this review. The provided data does not identify a release containing the fix.
How can I determine whether an application may be affected?
Check whether the application uses Excelize 2.1.0 through 2.11.0 and processes workbooks with File.GetRows or by iterating Rows. The issue is relevant where such workbooks can contain crafted worksheet row attributes.