cve.bz

CVE-2026-107213 excelize excelize: NULL Pointer Dereference

8.7 highExploit referenceEPSS 0.2%Fix available

High (8.7) in excelize excelize. EPSS 0.2% estimated probability of exploitation activity in the next 30 days. Fixed in github.com/xuri/excelize/v2 2.11.1-0.20260929015830-8ffeb07ec9a3.

On this page
Excelize is a Go language library for reading and writing Microsoft Excel spreadsheets. From 2.9.0 to 2.11.0, GetSlicers checks for ExtLst but dereferences ws.Drawing without checking whether the independently optional drawing element exists. File.GetSlicers reads ws.Drawing.RID after seeing a worksheet extLst element even when the independently optional worksheet drawing element is absent. When a crafted worksheet contains an extLst element without a drawing element and the application calls GetSlicers, the nil ws.Drawing pointer is dereferenced while resolving the drawing relationship, allowing an attacker to panic and terminate an unprotected process. No fixed version is available as of this review.

Severity

CVSS 4.0

8.7 high
CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:N/VI:N/VA:H/SC:N/SI:N/SA:N

CVSS 3.1

5.5 medium
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H
EPSS
0.2% (unchanged from 0.2% a week ago; 0.2% 30 days ago) estimated probability of exploitation activity in the next 30 days; 14th percentile. Scored 2026-11-17. A forecast for this CVE across the internet, not for your own systems.
CISA's assessment (SSVC)
Exploitation: none · 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-476 NULL Pointer Dereference
OWASP Top 10
A10:2025 Mishandling of Exceptional Conditions
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-107213 for an engineer deciding whether to act. Use https://cve.bz/api/public/cves/CVE-2026-107213?via=ask-ai-copy and https://cve.bz/cve/CVE-2026-107213?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-107213 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.9.0 through 2.11.0

Packages (OSV)

AdvisoryEcosystemPackageAffectedFixed in
GHSA-r7x5-4969-99p7Gogithub.com/xuri/excelize/v2>=2.9.0 <2.11.1-0.20260929015830-8ffeb07ec9a32.11.1-0.20260929015830-8ffeb07ec9a3
GO-2026-6687Gogithub.com/xuri/excelize/v2>=2.9.0 <2.11.1-0.20260929015830-8ffeb07ec9a32.11.1-0.20260929015830-8ffeb07ec9a3

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.

References

Check your stackJSON