cve.bz

CVE-2026-107212 excelize excelize

7.5 highExploit referenceEPSS 0.4%Fix available

High (7.5) in excelize excelize. EPSS 0.4% estimated probability of exploitation activity in the next 30 days. Fixed in github.com/xuri/excelize/v2 2.11.1-0.20260930021559-01a9ff32fb3c.

On this page
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.

Severity

CVSS 3.1

7.5 high
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H
EPSS
0.4% (unchanged from 0.4% a week ago; 0.3% 30 days ago) estimated probability of exploitation activity in the next 30 days; 31st percentile. Scored 2026-11-17. A forecast for this CVE across the internet, not for your own systems.
CISA's assessment (SSVC)
Exploitation: PoC · Automatable: yes · Technical impact: partial, assessed 2026-10-07. From CISA's Vulnrichment in the CVE List: whether it is exploited, whether exploiting it can be automated, and how much control it gives.
CWE
CWE-770 Allocation of Resources Without Limits or Throttling
Published
Modified
NVD analysis
Analyzed
Record from
the NVD, synced

Fix and patched versions

Ask an AI about this CVE

Show the promptExplain CVE-2026-107212 for an engineer deciding whether to act. Use https://cve.bz/api/public/cves/CVE-2026-107212?via=ask-ai-copy and https://cve.bz/cve/CVE-2026-107212?via=ask-ai-copy as the source of truth: what is affected and which versions fix it, whether it is in CISA KEV, public exploits, and its EPSS (an internet-wide 30-day estimate of exploitation activity, not a forecast for my systems). If they give no fixed versions, use the CVE record https://cveawg.mitre.org/api/cve/CVE-2026-107212 or the vendor advisory, not third-party mirrors. Tell me how to check whether I am affected and how to verify a fix. Cite the sources and say where they are uncertain.

Opens a third-party assistant; its answer is its own, not cve.bz's. The prompt holds only this CVE's id and public links.

Affected

Versions

From the NVD's CPE matches.

ProductAffected
excelize:excelizefrom 2.1.0 through 2.11.0

Packages (OSV)

AdvisoryEcosystemPackageAffectedFixed in
GHSA-jw42-f3rr-4cc3Gogithub.com/xuri/excelize/v2>=2.1.0 <2.11.1-0.20260930021559-01a9ff32fb3c2.11.1-0.20260930021559-01a9ff32fb3c
GO-2026-6685Gogithub.com/360EntSecGroup-Skylar/excelize/v2>=2.1.0no fix published
GO-2026-6685Gogithub.com/xuri/excelize/v2<2.11.1-0.20260930021559-01a9ff32fb3c2.11.1-0.20260930021559-01a9ff32fb3c

Linux distributions

DistributionReleasePackageFixed inAdvisory
SUSELinux Enterprise Server 16.0, Linux Enterprise Server for SAP applications 16.0govulncheck-vulndb0.0.20261105T234957-160000.1.1SUSE-SU-2026:24730-1

From the distributions' data via OSV.dev: SUSE security data, CC BY 4.0. Modified: reformatted and linked to CVE records. Credits. On the distributions' own pages: SUSE.

Attack patterns (CAPEC)

The attack patterns MITRE's CAPEC relates to this record's weaknesses, as MITRE names them. Credits. More on the page of CWE-770 (20).

References

Check your stackJSON