Quick answers
- Is CVE-2026-107212 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-107212 being exploited in the wild.
- How severe is CVE-2026-107212?
- High severity, with a CVSS score of 7.5, published 8 October 2026.
- Which products and versions are affected?
- Excelize before 2.11.1; github.com/360EntSecGroup-Skylar/excelize/v2 (Go) SEMVER:introduced=2.1.0; github.com/xuri/excelize/v2 (Go) >= 2.1.0, < 2.11.1-0.20260930021559-01a9ff32fb3c, SEMVER:introduced=0,fixed=2.11.1-0.20260930021559-01a9ff32fb3c, SEMVER:introduced=2.1.0,fixed=2.11.1-0.20260930021559-01a9ff32fb3c.
- Is there a fix for CVE-2026-107212?
- Yes. github.com/xuri/excelize/v2 (Go): upgrade to 2.11.1-0.20260930021559-01a9ff32fb3c or later. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
- How is CVE-2026-107212 attacked?
- It is attacked over the network, in a software library.
- Am I affected by CVE-2026-107212?
- Check whether you run Excelize, github.com/360EntSecGroup-Skylar/excelize/v2 (Go) or github.com/xuri/excelize/v2 (Go) at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.
How to fix
- github.com/xuri/excelize/v2 (Go): upgrade to 2.11.1-0.20260930021559-01a9ff32fb3c or later
go get github.com/xuri/excelize/v2@v2.11.1-0.20260930021559-01a9ff32fb3c
Technical details
The Rows.Columns method reads row elements without validating the row number against the Excel limit (1,048,576 rows), whereas Rows.Next performs the check. When a valid row precedes an out-of-bounds row number, Columns consumes and caches the oversized value, causing subsequent Next() calls to iterate from the current row to that value without ever hitting the validation check. The vulnerability requires network access and no authentication, and denial of service is the only impact.
Affected products
- Excelize Excelize before 2.11.1
Identifiers
- CVE-2026-107212
- GHSA-jw42-f3rr-4cc3
- GO-2026-6685
Timeline
- 2026-10-08: disclosed