Advisory record · GHSA-8mcq-6wmr-jrjv

Excelize: a row whose earlier cell has a higher column reference than its last cell panics index out of range on almost every worksheet read API

CVSS 6.5 MediumEPSS 0.0027 · 19th percentile

Published by the GitHub Advisory Database at 7 Oct 2026, 20:23 UTC. agentprime has not analysed this yet, so whether it affects any app is not known.

PackageEcosystemAffectedFixed in
github.com/xuri/excelize/v2Go>=2.0.0, <2.11.1-0.20260816084418-46a5eb2894482.11.1-0.20260816084418-46a5eb289448
Identifiers
GHSA-8mcq-6wmr-jrjv · CVE-2026-107221 · GO-2026-6676
Weakness (CWE)
CWE-787
Published
7 Oct 2026
Updated
5 Nov 2026

Machine-written summary

Summary written by Claude Haiku from the source advisory. Not reviewed by a person.

Excelize (github.com/xuri/excelize/v2) versions from 2.0.0 before 2.11.1-0.20260816084418-46a5eb289448 are affected. A specially crafted worksheet in an XLSX file, where a row's cells are out of column order and an earlier cell references a higher column than the last cell, causes an index-out-of-range panic when the file is read through most non-streaming worksheet APIs, crashing the process. An attacker only needs to get an untrusted spreadsheet opened by the application; no authentication is required. Upgrade to 2.11.1-0.20260816084418-46a5eb289448 or later.

Written 1 Nov 2026.

Not analysed yet

We haven’t published our analysis of this Advisory yet. Once a person has reviewed it, this page will say what’s vulnerable, what has to be true for your app to be affected, and how to check.

Severity and exploitation

ScoreRatingCVSSVectorSource
6.5 Medium 3.1 CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:N/I:N/A:H CNA (GitHub_M)
  • CISA KEV Not listed.
  • EPSS 0.0027, the 19th percentile, on 7 Nov 2026: FIRST’s estimate of the chance of exploitation in the next 30 days.

Timeline

  1. 31 Oct 2026, 14:12 UTC First seen by agentprime
  2. 31 Oct 2026, 14:12 UTC Confirmed by OSV

Sources

Facts on this page come from the GitHub Advisory Database (CC-BY 4.0), OSV and the other sources listed, as published. We don’t reproduce full advisory descriptions, which can contain exploit code.