CVE-2026-107212: CWE-770: Allocation of Resources Without Limits or Throttling in qax-os excelize
Description
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.
CVSS v3.1
Score 7.5high
Affected software
qax-os
excelize
pkg:golang/github.com/qax-os/excelizeRun on your own infrastructure? Check whether these packages are installed with threat-finder — our free open-source scanner.
Weaknesses
AI-Powered Analysis
Machine-generated threat intelligence
Technical Analysis
Excelize versions 2.1.0 to 2.11.0 contain a resource exhaustion vulnerability (CWE-770) due to the Rows.Columns method accepting a look-ahead row number beyond the TotalRows limit enforced by Rows.Next. The File.GetRows function relies on these methods but does not enforce the limit in Rows.Columns, allowing an attacker to craft a worksheet with an oversized row number after a valid row. When the application calls GetRows or iterates Rows, the iterator processes every missing row number instead of rejecting the workbook, causing prolonged CPU consumption controlled by the attacker. This vulnerability can lead to denial of service by exhausting CPU resources. No patch or fixed version is currently available.
Potential Impact
The vulnerability allows an attacker to cause high CPU usage on systems processing malicious Excel files using affected Excelize versions. This can lead to denial of service conditions by consuming a CPU core for an attacker-controlled duration. There is no impact on confidentiality or integrity reported. No known exploits in the wild have been documented.
Mitigation Recommendations
No official fix or patch is currently available for this vulnerability. Users should monitor vendor advisories for updates. Until a fix is released, avoid processing untrusted Excel files with affected versions of Excelize or implement external resource usage limits where possible to mitigate potential denial of service.
Technical Details
- Data Version
- 5.2
- Assigner Short Name
- GitHub_M
- Date Reserved
- 2026-10-07T14:34:14.815Z
- Cvss Version
- 3.1
- State
- PUBLISHED
Threat ID: 6ac686182cdf04f6566c0b2e
Added to database: 10/07/2026, 17:49:12 UTC
Last enriched: 10/07/2026, 18:03:25 UTC
Last updated: 10/07/2026, 18:56:10 UTC
Views: 11
Community Reviews
0 reviewsCrowdsource mitigation strategies, share intel context, and vote on the most helpful responses. Sign in to add your voice and help keep defenders ahead.
Want to contribute mitigation steps or threat intel context? Sign in or create an account to join the community discussion.
Actions
Updates to AI analysis require Pro Console access. Upgrade inside Console → Billing.
Need more coverage?
Upgrade to Pro Console for AI refresh and higher limits.
For incident response and remediation, OffSeq services can help resolve threats faster.
Latest Threats
Check if your credentials are on the dark web
Instant breach scanning across billions of leaked records. Free tier available.