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

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-107220: 0.26% estimated exploitation activity in the next 30 days; percentile 18.40 (FIRST EPSS, 2026-11-03). This is a model estimate, not proof of exploitation or customer exposure.

As published by the source; long descriptions are shortened.

Summary A worksheet containing <mergeCell ref=""/ makes mergeCellsParser leave the cached rectangle empty, and cellInRange then indexes that empty slice without a length check. Every non-streaming cell API panics with index out of range [0] with length 0 on the first cell read after opening the file. Where it is cell.go, cellInRange func cellInRange(cell, ref []int) bool { return cell[0] = ref[0] && cell[0] <= ref[2] && cell[1] = ref[1] && cell[1] <= ref[3] } ref is indexed at four positions with no bounds check. The caller that can hand it an empty slice, mergeCellsParser if ref := ws.MergeCells.Cells[i].Ref; len(ws.MergeCells.Cells[i].rect) == 0 && ref != "" { if strings.Count(ref, ":") != 1 { ref += ":" + ref } rect, err := rangeRefToCoordinates(ref) if err != nil { return cell, err } = sortCoordinates(rect) ws.MergeCells.Cells[i].rect = rect } if cellInRange([]int{col, row}, ws.MergeCells.Cells[i].rect) { The ref != "" condition means an empty ref skips the block that populates…

Published by the source

7 Oct 2026, 20:23 UTC

Last modified by the source

7 Oct 2026, 20:30 UTC

Source last checked

26 Oct 2026, 15:29 UTC

1. Revision 2 · amended · 26 Oct 2026

   Amended from ghsa record GHSA-g27h-8qhm-6pff

2. Revision 1 · created · 24 Oct 2026

   Published from osv record GHSA-g27h-8qhm-6pff

Preview the exact text before you copy it. Commands are read-only suggestions; review them before running anything.

# Patch Next advisory brief: CVE-2026-107220

Advisory: Excelize: Panic in cellInRange on a worksheet with an empty mergeCell ref
IDs: CVE-2026-107220, GHSA-g27h-8qhm-6pff
Record: https://patchnext.com/advisories/cve-2026-107220 (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.20260820023833-99903a3240e5. A vendor fix does not mean a deployment is fixed.

## Affected components
- Go github.com/xuri/excelize/v2: affected >= 2.7.1, < 2.11.1-0.20260820023833-99903a3240e5; fixed in 2.11.1-0.20260820023833-99903a3240e5

## 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-g27h-8qhm-6pff (OSV record GHSA-g27h-8qhm-6pff lists affected ranges: Go github.com/xuri/excelize/v2 >=2.7.1 <2.11.1-0.20260820023833-99903a3240e5 (fixed))
- Verified: https://github.com/advisories/GHSA-g27h-8qhm-6pff (GitHub-reviewed advisory GHSA-g27h-8qhm-6pff lists affected ranges: Go github.com/xuri/excelize/v2 >=2.7.1 <2.11.1-0.20260820023833-99903a3240e5)

Commands are suggestions: review each one before running it.