Skip to main content
VulnerabilityPublished

CVE-2026-107219: qax-os excelize · Uncontrolled Resource Consumption

Affects qax-os excelizeSource CVE Database V5

0
Compare

Not known to be exploited · CVSS 7.5 High.

Data as of 21 Nov 2026, 17:34 UTC

CVSS 3.1 base score
7.5High
How severe the flaw is on the 0–10 CVSS scale.
EPSS
0.3% chance of exploitation in 30 days – higher than 30% 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: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.3.1 <=2.11.0
Fixed in–
Gogithub.com/qax-os/excelizepkg:golang/github.com/qax-os/excelizeOther threatsAffected
  • >=2.3.1 <=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

Consider implementing external timeouts or resource limits on processes that use excelize to mitigate denial of service risk. Monitor for vendor updates addressing this issue.

Description

CVE-2026-107219 is an uncontrolled resource consumption vulnerability in the qax-os excelize library. The vulnerability arises because the library processes the spinCount parameter from an encrypted file's EncryptionInfo stream without bounds, causing excessive CPU usage during key derivation. This leads to a denial of service by making file opening operations take an excessive amount of time. The vulnerability affects versions from 2.3.1 through 2.11.0. It impacts availability only and does not affect confidentiality or integrity. Legitimate files use a much lower spinCount, so normal usage is not impacted significantly.

References

Community reviews

Loading reviews…