Skip to content
Fencer Intel
medium 6.5

CVE-2026-107222 json

Excelize: GetConditionalFormats indexes conditional-formatting rule sub-elements with no length or nil check

published last mo. modified 4d ago also EUVD-2026-94552 , GHSA-rxcj-4pj5-74gr , GO-2026-6682

cvss
6.5
version 3.1, CNA
cisa kev
Not listed
not in CISA's catalog
epss
0.3%
EPSS 0.3% chance of exploitation in 30 days, percentile 19%
public exploits
0
none known

Summary

Excelize is a Go language library for reading and writing Microsoft Excel spreadsheets. From 2.7.0 to 2.11.0, conditional-format extraction indexes required child slices or dereferences an optional colorScale child without validating malformed rule structure. GetConditionalFormats reaches extractCondFmtCellIs and also indexes ColorScale.Cfvo, DataBar.Cfvo, and DataBar.Color without complete structural checks. When a crafted worksheet supplies a cellIs, dataBar, or colorScale rule missing expected children and the application calls GetConditionalFormats, missing formula, color, value-object, or colorScale data reaches an out-of-range index or nil dereference, allowing an attacker to panic and terminate an unprotected process. No fixed version is available as of this review.

Patch / fix

  • go github.com/xuri/excelize/v2 2.11.1-0.20260812075026-be7a16390fa6

Is CVE-2026-107222 in your dependencies? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.

Check with Fencer

CISA SSVC

Exploitation
Proof of concept is public
Automatable
no
Technical impact
partial
Assessed
last mo.

Exploit prediction

0.27% chance of exploitation in the next 30 days, higher than 19% of all scored CVEs (FIRST EPSS, 2026-11-09).

Exploits and checks

  • github.com https://github.com/qax-os/excelize/commit/be7a16390fa69c71d3ca618c741d1a2b5ed362cd referenced PoC, tagged "exploit" by a source, unverified
  • github.com https://github.com/qax-os/excelize/security/advisories/GHSA-rxcj-4pj5-74gr referenced PoC, tagged "exploit" by a source, unverified

CVSS scores

assigned by version score vector
CNA 3.1 6.5 CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:N/I:N/A:H
GitHub 3.1 6.5 CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:N/I:N/A:H

Affected packages

ecosystem package affected fixed in
go github.com/xuri/excelize/v2
>=2.7.0, <2.11.1-0.20260812075026-be7a16390fa6
2.11.1-0.20260812075026-be7a16390fa6

Affected products

  • qax-os excelize

Classification

Weakness
  • CWE-129 Improper Validation of Array Index
  • CWE-476 NULL Pointer Dereference

References

Sources

Fencer Intel keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.

CPEs and fixed versions use Anchore's correction of NVD's data: Added CPE configurations because not yet analyzed by NVD.