CVE-2026-107218 json
Excelize: RIGHT() on supplementary-plane text slices with a negative index and panics
published last mo. modified 4d ago also EUVD-2026-94548 , GHSA-8jjq-8j9w-m2v6 , GO-2026-6675
- cvss
- 5.3
- version 3.1, CNA
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 0.3%
- EPSS 0.3% chance of exploitation in 30 days, percentile 23%
- public exploits
- 0
- none known
Summary
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.
Patch / fix
- go github.com/xuri/excelize/v2 2.11.1-0.20260908032718-ecd99d761fe0
- github.com/qax-os/excelize@ecd99d7 commit
- github.com/qax-os/excelize#2390 pull request
Is CVE-2026-107218 in your dependencies? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.
Check with FencerCISA SSVC
- Exploitation
- none
- Automatable
- yes
- Technical impact
- partial
- Assessed
- last mo.
Exploit prediction
0.31% chance of exploitation in the next 30 days, higher than 23% of all scored CVEs (FIRST EPSS, 2026-11-09).
Exploits and checks
- github.com https://github.com/qax-os/excelize/security/advisories/GHSA-8jjq-8j9w-m2v6 referenced PoC, tagged "exploit" by a source, unverified
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| CNA | 3.1 | 5.3 | CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:L |
| GitHub | 3.1 | 5.3 | CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:L |
Affected packages
| ecosystem | package | affected | fixed in |
|---|---|---|---|
| go | github.com/xuri/excelize/v2 | >=2.10.1, <2.11.1-0.20260908032718-ecd99d761fe0 |
2.11.1-0.20260908032718-ecd99d761fe0 |
Affected products
- qax-os excelize
Classification
- Weakness
-
- CWE-129 Improper Validation of Array Index
References
-
github.com
/qax-os/excelize/pull/2390
web, issue-tracking, patch
-
github.com
/qax-os/excelize/commit/ecd99d761fe0489f1ed308e2f7dc2e0502d1a396
web, patch
-
github.com
/qax-os/excelize/security/advisories/GHSA-8jjq-8j9w-m2v6
web, exploit, vendor-advisory, advisory
-
github.com
/qax-os/excelize
package
Sources
- CVE List CVE-2026-107218
- GitHub Advisory GHSA-8jjq-8j9w-m2v6
- NVD CVE-2026-107218
- OSV GO-2026-6675
Fencer Intel keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.
CPEs and fixed versions use Anchore's correction of NVD's data: Added CPE configurations because not yet analyzed by NVD.