Excelize: GetConditionalFormats indexes conditional-formatting rule sub-elements with no length or nil check
CVE-2026-107222GHSA-rxcj-4pj5-74gr
What to do
Vendor fix available. Upgrade each affected package to the fixed version on its release line (github.com/xuri/excelize/v2 2.11.1-0.20260812075026-be7a16390fa6), redeploy, then verify what is actually installed.
This page has no inventory attached, so it cannot say whether you are affected. A vendor fix is not proof that your deployment is fixed.
Affected packages
Go github.com/xuri/excelize/v2
- Affected
- >= 2.7.0, < 2.11.1-0.20260812075026-be7a16390fa6
- Fixed in
- 2.11.1-0.20260812075026-be7a16390fa6
Sources
- Open Source Vulnerabilities (OSV.dev), including the GitHub Advisory Database
OSV record GHSA-rxcj-4pj5-74gr lists affected ranges: Go github.com/xuri/excelize/v2 >=2.7.0 <2.11.1-0.20260812075026-be7a16390fa6 (fixed)
VerifiedObserved Structured OSV record; GitHub-reviewed advisory.
- GitHub Advisory Database and maintainer security advisories on GitHub
GitHub-reviewed advisory GHSA-rxcj-4pj5-74gr lists affected ranges: Go github.com/xuri/excelize/v2 >=2.7.0 <2.11.1-0.20260812075026-be7a16390fa6
VerifiedObserved Structured GitHub Advisory Database record (type=reviewed) from the GitHub REST API.
Severity and exploitation
- Exploitation
- No confirmed exploitation recorded. Patch Next marks exploitation only from CISA KEV.
- CVSS
- 6.5 · CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:N/I:N/A:H
- EPSS
- CVE-2026-107222: 0.27% estimated exploitation activity in the next 30 days; percentile 19.24 (FIRST EPSS, 2026-11-03). This is a model estimate, not proof of exploitation or customer exposure.
Source description
As published by the source; long descriptions are shortened.
Summary GetConditionalFormats reads sub-elements of a <cfRule straight out of xl/worksheets/sheetN.xml and indexes them without checking length, and in one case without checking for nil. Three rule types are affected: cellIs, dataBar and colorScale. A workbook with a rule that is missing a child a real Excel file would always have panics the call. Where it is All three sinks are in styles.go, at the same line numbers in v2.11.0 and on master d552a7e. All three are reached from GetConditionalFormats through styles.go:3271. styles.go:3003, in extractCondFmtCellIs: The branch above it handles len(c.Formula) == 2; this one is the fallback and does not check that there is a formula at all, so a cellIs rule with no <formula child indexes an empty slice. styles.go:3132, in the colorScale extractor: c.ColorScale is a xlsxColorScale and is nil when the <cfRule type="colorScale" element has no <colorScale child. Lines 3148 and 3153 then index Cfvo[1] and Cfvo[2] in the three-colour branch with…
Dates and revisions
- Published by the source
- Last modified by the source
- Source last checked
- Revision 2 · amended ·
Amended from ghsa record GHSA-rxcj-4pj5-74gr
- Revision 1 · created ·
Published from osv record GHSA-rxcj-4pj5-74gr
Agent brief
Preview the exact text before you copy it. Commands are read-only suggestions; review them before running anything.
# Patch Next advisory brief: CVE-2026-107222 Advisory: Excelize: GetConditionalFormats indexes conditional-formatting rule sub-elements with no length or nil check IDs: CVE-2026-107222, GHSA-rxcj-4pj5-74gr Record: https://patchnext.com/advisories/cve-2026-107222 (revision 2, source checked 26 Oct 2026, 15:29 UTC) Inventory: none attached. This brief comes from a public page and does not say whether any deployment is affected. Severity: Medium (CVSS 6.5) Exploitation: no confirmed exploitation recorded. Patch Next confirms exploitation only from CISA KEV. Vendor response: Vendor fix available; fixed versions by package: github.com/xuri/excelize/v2 2.11.1-0.20260812075026-be7a16390fa6. A vendor fix does not mean a deployment is fixed. ## Affected components - Go github.com/xuri/excelize/v2: affected >= 2.7.0, < 2.11.1-0.20260812075026-be7a16390fa6; fixed in 2.11.1-0.20260812075026-be7a16390fa6 ## Suggested inspection (read-only) - Go github.com/xuri/excelize/v2: check the installed version with your package manager. ## Supported action Upgrade each affected component to a fixed version on its release line. For a transitive dependency, upgrade the parent package or add an override or constraint, then regenerate the lockfile. Redeploy every environment that ran an affected version. ## Required regression checks - Run the test suite and a production build. - Exercise the features that depend on github.com/xuri/excelize/v2. - Repeat the inspection and confirm that only fixed versions remain installed. ## Rollback considerations - Keep the previous lockfile and deployment artifact. Rolling back reinstates the vulnerable version, so apply any documented mitigation while you fix forward. ## Unresolved questions - Which deployments run an affected version? - Exploitation status can change. Check again before lowering the priority. - Mark the work resolved only after the fixed version is verified in production. ## Sources - Verified: https://osv.dev/vulnerability/GHSA-rxcj-4pj5-74gr (OSV record GHSA-rxcj-4pj5-74gr lists affected ranges: Go github.com/xuri/excelize/v2 >=2.7.0 <2.11.1-0.20260812075026-be7a16390fa6 (fixed)) - Verified: https://github.com/advisories/GHSA-rxcj-4pj5-74gr (GitHub-reviewed advisory GHSA-rxcj-4pj5-74gr lists affected ranges: Go github.com/xuri/excelize/v2 >=2.7.0 <2.11.1-0.20260812075026-be7a16390fa6) Commands are suggestions: review each one before running it.
Loading voting…