cve.bz

CVE-2026-107215 excelize excelize

7.5 highExploit referenceEPSS 0.2%Fix available

High (7.5) 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.20260912113515-5f636f9dcde5.

On this page
Excelize is a Go language library for reading and writing Microsoft Excel spreadsheets. From 2.3.1 to 2.11.0, extractPart allocates a byte slice directly from an attacker-controlled CFB directory-entry size before validating the sector chain or size domain. extractPart trusts the CFB directory entry streamSize for EncryptionInfo and EncryptedPackage allocations before validating the stream. When a crafted OLE compound file declares a negative or extremely large EncryptionInfo or EncryptedPackage stream size, the declared size reaches make with a negative length or forces a multi-gigabyte allocation, allowing an attacker to panic or exhaust process memory. 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.2% (unchanged from 0.2% a week ago; 0.2% 30 days ago) estimated probability of exploitation activity in the next 30 days; 15th 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-10. 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-789 Memory Allocation with Excessive Size Value
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-107215 for an engineer deciding whether to act. Use https://cve.bz/api/public/cves/CVE-2026-107215?via=ask-ai-copy and https://cve.bz/cve/CVE-2026-107215?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-107215 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.3.1 through 2.11.0

Packages (OSV)

AdvisoryEcosystemPackageAffectedFixed in
GHSA-x2q3-8cjh-766fGogithub.com/xuri/excelize/v2>=2.3.1 <2.11.1-0.20260912113515-5f636f9dcde52.11.1-0.20260912113515-5f636f9dcde5
GO-2026-6689Gogithub.com/360EntSecGroup-Skylar/excelize/v2>=2.3.1no fix published
GO-2026-6689Gogithub.com/xuri/excelize/v2<2.11.1-0.20260912113515-5f636f9dcde52.11.1-0.20260912113515-5f636f9dcde5

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