CVE-2026-107213: qax-os excelize · NULL Pointer Dereference
Affects qax-os excelizeSource CVE Database V5
Not known to be exploited · CVSS 8.7 High.
Data as of 21 Nov 2026, 17:34 UTC
- EPSS
- 0.2% chance of exploitation in 30 days – higher than 14% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:N/VI:N/VA:H/SC:N/SI:N/SA:NExploitation 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
Until a fix is available, applications using excelize versions 2.9.0 through 2.11.0 should consider implementing input validation or sandboxing to mitigate potential crashes caused by malicious Excel files.
Description
CVE-2026-107213 is a high-severity vulnerability in the qax-os excelize Go library versions 2.9.0 through 2.11.0. The flaw is a NULL pointer dereference caused by the GetSlicers function accessing a worksheet drawing element without verifying its existence. This can cause the application to panic and terminate when processing a crafted Excel worksheet containing an extLst element but lacking the drawing element. No fix is currently available for this issue.