# Excelize: Panic in cellInRange on a worksheet with an empty mergeCell ref

Advisory record · `GHSA-g27h-8qhm-6pff`

- **Identifiers:** `GHSA-g27h-8qhm-6pff` · `CVE-2026-107220` · `GO-2026-6680`
- **State:** Confirmed
- **Severity:** CVSS 6.5 Medium
- **Critical:** No
- **Weakness (CWE):** [CWE-125](https://cwe.mitre.org/data/definitions/125.html) · [CWE-129](https://cwe.mitre.org/data/definitions/129.html)
- **Tags:** [Memory corruption](https://agentprime.io/advisories/tag/memory-corruption.md) · [CWE-129](https://agentprime.io/advisories/tag/cwe-129.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.7.1, <2.11.1-0.20260820023833-99903a3240e5`; fixed in `2.11.1-0.20260820023833-99903a3240e5`

## Machine-written summary

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

> Excelize (github.com/xuri/excelize/v2) versions 2.7.1 up to 2.11.1-0.20260820023833-99903a3240e5 are affected. A workbook containing a merge cell with an empty ref attribute causes a panic when any non-streaming cell API reads a cell, such as GetCellValue, and the panic crashes the process unless the caller recovers from it. An attacker needs only to get an untrusted .xlsx file opened by the consuming application; no options or special configuration are involved. Upgrade to 2.11.1-0.20260820023833-99903a3240e5 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.0026, the 18th percentile, on 6 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-g27h-8qhm-6pff)

## Sources

- [GitHub Advisory Database: GHSA-g27h-8qhm-6pff](https://github.com/advisories/GHSA-g27h-8qhm-6pff)
- [OSV: GHSA-g27h-8qhm-6pff](https://osv.dev/vulnerability/GHSA-g27h-8qhm-6pff)
- <https://github.com/qax-os/excelize/security/advisories/GHSA-g27h-8qhm-6pff>
- <https://github.com/qax-os/excelize/pull/2379>
- <https://github.com/qax-os/excelize/commit/99903a3240e58a47ff28fb8e05a03bd9d496ec24>
- <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-g27h-8qhm-6pff>, or `POST https://api.agentprime.io/v1/match` with your packages (<https://agentprime.io/api.md>)

---

The web page: <https://agentprime.io/advisories/GHSA-g27h-8qhm-6pff/>. Everything for agents: <https://agentprime.io/llms.txt>.