cve.bz

CVE-2026-107218 excelize excelize: Improper Validation of Array Index

5.3 mediumExploit referenceEPSS 0.3%Fix available

Medium (5.3) in excelize excelize. EPSS 0.3% estimated probability of exploitation activity in the next 30 days. Fixed in github.com/xuri/excelize/v2 2.11.1-0.20260908032718-ecd99d761fe0.

On this page
Excelize is a Go language library for reading and writing Microsoft Excel spreadsheets. From 2.10.1 to 2.11.0, RIGHT validates the requested length with UTF-16 code-unit counts but slices a rune array using Unicode code-point counts. RIGHT reaches leftRight through CalcCellValue, where countUTF16String validates one unit but utf8.RuneCountInString supplies the slice index in another. When RIGHT evaluates supplementary-plane text with a requested character count between the rune count and UTF-16 code-unit count, the inconsistent units produce a negative rune-slice index, allowing an attacker to panic during formula evaluation. No fixed version is available as of this review.

Severity

CVSS 3.1

5.3 medium
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:L
EPSS
0.3% (unchanged from 0.3% a week ago; 0.3% 30 days ago) estimated probability of exploitation activity in the next 30 days; 24th 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-129 Improper Validation of Array Index
OWASP Top 10
A05:2025 Injection
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-107218 for an engineer deciding whether to act. Use https://cve.bz/api/public/cves/CVE-2026-107218?via=ask-ai-copy and https://cve.bz/cve/CVE-2026-107218?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-107218 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.10.1 through 2.11.0

Packages (OSV)

AdvisoryEcosystemPackageAffectedFixed in
GHSA-8jjq-8j9w-m2v6Gogithub.com/xuri/excelize/v2>=2.10.1 <2.11.1-0.20260908032718-ecd99d761fe02.11.1-0.20260908032718-ecd99d761fe0
GO-2026-6675Gogithub.com/xuri/excelize/v2>=2.10.1 <2.11.1-0.20260908032718-ecd99d761fe02.11.1-0.20260908032718-ecd99d761fe0

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)

  • CAPEC-100 Overflow Buffers Likelihood: High · Severity: Very High

The attack patterns MITRE's CAPEC relates to this record's weaknesses, as MITRE names them. Credits.

References

Check your stackJSON