# 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

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

- **Identifiers:** `GHSA-8mcq-6wmr-jrjv` · `CVE-2026-107221` · `GO-2026-6676`
- **State:** Confirmed
- **Severity:** CVSS 6.5 Medium
- **Critical:** No
- **Weakness (CWE):** [CWE-787](https://cwe.mitre.org/data/definitions/787.html)
- **Tags:** [Memory corruption](https://agentprime.io/advisories/tag/memory-corruption.md)
- **Published:** 7 Oct 2026
- **Updated:** 5 Nov 2026
- **Reviewed by a person:** No

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.

## Affected packages

- `github.com/xuri/excelize/v2` (Go): affected `>=2.0.0, <2.11.1-0.20260816084418-46a5eb289448`; fixed in `2.11.1-0.20260816084418-46a5eb289448`

## 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

- 6.5 Medium, CVSS 3.1: `CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:N/I:N/A:H`, from CNA (GitHub_M)

- **CISA KEV:** Not listed.
- **EPSS:** 0.0027, the 19th percentile, on 8 Nov 2026: FIRST’s estimate of the chance of exploitation in the next 30 days.

## Timeline

- 31 Oct 2026, 14:12 UTC: First seen by agentprime
- 31 Oct 2026, 14:12 UTC: [Confirmed by OSV](https://osv.dev/vulnerability/GHSA-8mcq-6wmr-jrjv)

## Sources

- [GitHub Advisory Database: GHSA-8mcq-6wmr-jrjv](https://github.com/advisories/GHSA-8mcq-6wmr-jrjv)
- [OSV: GHSA-8mcq-6wmr-jrjv](https://osv.dev/vulnerability/GHSA-8mcq-6wmr-jrjv)
- <https://github.com/qax-os/excelize/security/advisories/GHSA-8mcq-6wmr-jrjv>
- <https://github.com/qax-os/excelize/pull/2376>
- <https://github.com/qax-os/excelize/commit/46a5eb289448e40fbc7d3294589b03861fb822f0>
- <https://github.com/qax-os/excelize>

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.

## Check whether this affects you

A Match means an installed version is in the affected range above. Most don’t affect the app; agentprime hasn’t analysed this one yet.

- With the agentprime MCP server (<https://api.agentprime.io/mcp>), ask your agent to check the project: `check_lockfile` sends a lockfile, `check_packages` a list of installed packages, and both return the Matches and the upgrades that clear them. `get_advisory` returns this record. Setup: <https://agentprime.io/mcp.md>
- In a browser: <https://agentprime.io/check/> reads your lockfile in the browser, never uploading it.
- Whether it touches your code, with file and line: the Claude Code plugin, <https://agentprime.io/plugin.md>
- As JSON: <https://api.agentprime.io/v1/advisories/GHSA-8mcq-6wmr-jrjv>, or `POST https://api.agentprime.io/v1/match` with your packages (<https://agentprime.io/api.md>)

---

The web page: <https://agentprime.io/advisories/GHSA-8mcq-6wmr-jrjv/>. Everything for agents: <https://agentprime.io/llms.txt>.