Resource exhaustion in Qax-Os Excelize
CVE-2026-107212
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.
Published .
CVSS v3 metric
CVSS v3 base score 7.5 (High). Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H.
EPSS exploit prediction
No EPSS score from FIRST.org yet. New CVEs usually get one within a few days; no score means no signal yet, not low risk. How EPSS works.
Affected products
- Qax-Os Excelize — versions >= 2.1.0, <= 2.11.0
Weakness classification (CWE)
References
Frequently asked questions
- What is CVE-2026-107212?
- CVE-2026-107212 is a high-severity vulnerability in Qax-Os Excelize, classified under Allocation of Resources Without Limits or Throttling. CVSS score: 7.5/10. Published 2026-10-07.
- How severe is CVE-2026-107212?
- High severity. CVSS v3 base score is 7.5 out of 10.