# CVE-2026-107220: Excelize: Panic in cellInRange on a worksheet with an empty mergeCell ref

> An attacker can cause a denial of service by providing a crafted Excel file with an empty mergeCell reference, triggering a panic in the Excelize library.

- **Severity:** Medium 6.5 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:N/I:N/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** A user has to click or open something
- **Fix available:** Yes
- **Published:** 7 Oct 2026
- **Updated:** 10 Oct 2026
- **Also known as:** GHSA-g27h-8qhm-6pff

## What is CVE-2026-107220?

CVE-2026-107220 is a medium-severity vulnerability in qax-os excelize, published on 7 Oct 2026. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.

### Official description

Excelize is a Go language library for reading and writing Microsoft Excel spreadsheets. From 2.7.1 to 2.11.0, mergeCellsParser leaves the cached rectangle empty for an empty mergeCell ref and then passes that empty slice to cellInRange without a length check. GetCellValue reaches mergeCellsParser, which passes an empty rectangle derived from the mergeCell ref attribute into cellInRange. When a crafted worksheet contains an empty mergeCell ref and a non-streaming cell API reads the worksheet, cellInRange indexes four positions in an empty slice, allowing an attacker to panic on the first affected cell operation. No fixed version is available as of this review.

Weakness: CWE-129 (Improper Validation of Array Index), CWE-125 (Out-of-bounds Read)

## Which versions are affected by CVE-2026-107220?

2 open source packages ship an affected version, including github.com/xuri/excelize/v2. It affects 1 product.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `github.com/xuri/excelize/v2` | Go | From 2.7.1 | 2.11.1-0.20260820023833-99903a3240e5 |
| `github.com/xuri/excelize/v2` | Go | From 2.7.1 | 2.11.1-0.20260820023833-99903a3240e5 |

Products: Excelize Excelize.

## How do I fix CVE-2026-107220?

Upgrade github.com/xuri/excelize/v2 to 2.11.1-0.20260820023833-99903a3240e5 or later.

## Is CVE-2026-107220 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-107220 exists.

## Other vulnerabilities in qax-os excelize

- [CVE-2026-107211](https://insights.sbomify.com/CVE-2026-107211/): Excelize: Unchecked pivot-cache field index in extractPivotTableFields causes unrecoverable panic (high 8.7)
- [CVE-2026-107213](https://insights.sbomify.com/CVE-2026-107213/): Excelize: Nil-pointer dereference in GetSlicers when a worksheet has extLst present but no drawing element (high 8.7)
- [CVE-2026-59161](https://insights.sbomify.com/CVE-2026-59161/): Excelize: Streaming GetRows row-bound bypass causes attacker-controlled allocation (high 8.7)
- [CVE-2026-107212](https://insights.sbomify.com/CVE-2026-107212/): Excelize: Unbounded row number in Rows.Columns makes GetRows and the Rows iterator loop for days (high 7.5)
- [CVE-2026-107214](https://insights.sbomify.com/CVE-2026-107214/): Excelize Decrypt: unrecoverable panics on malformed OLE/CFB encrypted workbooks (high 7.5)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-107220 and fix it if it is affected.

What it is: CVE-2026-107220 is a medium-severity vulnerability in qax-os excelize, published on 7 Oct 2026. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-107220 exists.

Affected packages and fixed versions:
- github.com/xuri/excelize/v2 (Go): affected from 2.7.1; fixed in 2.11.1-0.20260820023833-99903a3240e5
- github.com/xuri/excelize/v2 (Go): affected from 2.7.1; fixed in 2.11.1-0.20260820023833-99903a3240e5

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-107220/ (Markdown: https://insights.sbomify.com/CVE-2026-107220/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-107220
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-107220
- OSV: https://osv.dev/vulnerability/CVE-2026-107220

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-107220/
Summaries are generated and may contain mistakes; the official description above is the record.