CVE-2026-107218: qax-os excelize · Improper Validation of Array Index
Affects qax-os excelizeSource CVE Database V5
Not known to be exploited · CVSS 5.3 Medium.
Data as of 21 Nov 2026, 17:34 UTC
- EPSS
- 0.3% chance of exploitation in 30 days – higher than 24% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:LExploitation evidence
Disclosed: evidence found.
CVE published 7 Oct 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponized: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors
A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 21 Nov 2026.
What to do
Affected software
| Product | Affected | Fixed in |
|---|---|---|
| qax-osexcelize | Affected
| Fixed in– |
Gogithub.com/qax-os/excelizepkg:golang/github.com/qax-os/excelizeOther threats | Affected
| Fixed in– |
Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.
AI-suggested
No fixed version is currently available. Users should monitor the vendor's advisory channels for updates and consider avoiding processing untrusted or specially crafted Excel files that might trigger this vulnerability until a patch is released.
Description
CVE-2026-107218 is a medium severity vulnerability in the Go library excelize (versions 2.10.1 through 2.11.0) used for reading and writing Microsoft Excel spreadsheets. The issue arises from improper validation of array indices in the RIGHT function, which inconsistently uses UTF-16 code-unit counts and Unicode code-point counts when slicing strings. This mismatch can cause a negative index panic during formula evaluation when processing supplementary-plane Unicode characters. No fix is currently available for this vulnerability.