Skip to main content
VulnerabilityPublished

CVE-2026-107223: qax-os excelize · Excessive Memory Allocation

Affects qax-os excelizeSource CVE Database V5

0
Compare

Not known to be exploited · CVSS 7.1 High.

Data as of 21 Nov 2026, 17:34 UTC

CVSS 4.0 base score
7.1High
How severe the flaw is on the 0–10 CVSS scale.
EPSS
0.3% chance of exploitation in 30 days – higher than 31% 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:P/VC:N/VI:N/VA:H/SC:N/SI:N/SA:N

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.1.0 <=2.11.0
Fixed in–
Gogithub.com/qax-os/excelizepkg:golang/github.com/qax-os/excelizeOther threatsAffected
  • >=2.1.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

Since no fixed version is available as of this review, users should consider avoiding processing untrusted Excel files with affected versions of excelize or implement resource usage limits at the application level to mitigate potential denial of service.

Description

CVE-2026-107223 is a high-severity vulnerability in the qax-os excelize Go library for handling Microsoft Excel spreadsheets. Versions from 2.1.0 through 2.11.0 are affected. The flaw arises because the library's flatCols function expands column ranges without validating the Min and Max column indices against the worksheet's column limit. An attacker can craft a worksheet with an excessively large column max attribute, causing the library to allocate excessive memory and CPU during column mutation operations, potentially leading to out-of-memory conditions. No official fix or patch is currently available.

References

Community reviews

Loading reviews…