Skip to main content
VulnerabilityPublished Updated

CVE-2026-107225: qax-os excelize · Improper Input Validation

Affects qax-os excelizeSource CVE Database V5

0
Compare

Not known to be exploited · CVSS 6.5 Medium.

Data as of 21 Nov 2026, 17:34 UTC

CVSS 3.1 base score
6.5Medium
How severe the flaw is on the 0–10 CVSS scale.
EPSS
0.2% chance of exploitation in 30 days – higher than 19% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:N/I:N/A:H

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 7 Oct 2026

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponized: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq 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

ProductAffectedFixed in
qax-osexcelizeAffected
  • >=2.8.0 <=2.11.0
Fixed in–
Gogithub.com/qax-os/excelizepkg:golang/github.com/qax-os/excelizeOther threatsAffected
  • >=2.8.0 <=2.11.0
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 or official patch is currently available. Users should be aware of the risk of denial of service when processing untrusted Excel files with affected versions of excelize. Until a fix is released, avoid processing untrusted or maliciously crafted styles.xml files or implement additional input validation at the application level to prevent negative style IDs.

Description

CVE-2026-107225 is an improper input validation vulnerability in the Go library excelize versions 2.8.0 through 2.11.0. The vulnerability arises because the GetStyle function's predicates only check upper bounds for style-table indices, allowing negative indices to be used. When a crafted styles.xml file contains negative fillId, borderId, or fontId values, these negative values bypass the upper-bound checks and cause negative slice indexing, leading to a panic during cell styling reads. No fix is currently available for this issue.

References

Community reviews

Loading reviews…