Skip to content
Patch Next
Sign inAdd to your agent

← Actionable
High, CVSS 8.7amended

Excelize: Unchecked pivot-cache field index in extractPivotTableFields causes unrecoverable panic

CVE-2026-107211GHSA-mx22-3794-2vpv

What to do

Vendor fix available. Upgrade each affected package to the fixed version on its release line (github.com/xuri/excelize/v2 2.11.1-0.20261003002531-6258dcebc4e2), redeploy, then verify what is actually installed.

This page has no inventory attached, so it cannot say whether you are affected. A vendor fix is not proof that your deployment is fixed.

Add to your agent

Affected packages

Sources

Severity and exploitation
Exploitation
No confirmed exploitation recorded. Patch Next marks exploitation only from CISA KEV.
CVSS 4.0
8.7 · CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:N/VI:N/VA:H/SC:N/SI:N/SA:N · score source
EPSS
  • CVE-2026-107211: 0.23% estimated exploitation activity in the next 30 days; percentile 14.38 (FIRST EPSS, 2026-11-03). This is a model estimate, not proof of exploitation or customer exposure.
Source description

As published by the source; long descriptions are shortened.

Summary extractPivotTableFields builds order := pc.getPivotCacheFieldsName() from xl/pivotCache/pivotCacheDefinitionN.xml's <cacheFields list, then indexes it with values taken from a separately parsed xl/pivotTables/pivotTableN.xml part with zero cross-validation: order[field.Fld] where field.Fld is a raw attacker-controlled int from the <dataField fld="N" attribute, and order[fieldIdx] where fieldIdx is a loop index over pt.PivotFields.PivotField that need not match the cache's field count. I executed two independent PoCs against the current HEAD: (1) trimmed the pivot cache's <cacheFields to count=0 while leaving the pivot table's 2 pivotFields untouched - runtime error: index out of range [0] with length 0 at pivotTable.go:1431; (2) left the 2 cache fields completely intact and only changed one attribute, fld="1" - fld="99999", in xl/pivotTables/pivotTable1.xml - runtime error: index out of range [99999] with length 2 at pivotTable.go:1443. Both stack traces confirmed via…

Dates and revisions
Published by the source
Last modified by the source
Source last checked
  1. Revision 4 · amended ·

    Amended from ghsa record GHSA-mx22-3794-2vpv

  2. Revision 3 · amended ·

    Reviewed OSV alias/range/CVSS4 correction; package source scopes and original publication preserved. No customer finding resolved.

  3. Revision 2 · amended ·

    Amended from osv record GO-2026-6695

  4. Revision 1 · created ·

    Published from osv record GHSA-mx22-3794-2vpv

Agent brief

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

# Patch Next advisory brief: CVE-2026-107211

Advisory: Excelize: Unchecked pivot-cache field index in extractPivotTableFields causes unrecoverable panic
IDs: CVE-2026-107211, GHSA-mx22-3794-2vpv
Record: https://patchnext.com/advisories/cve-2026-107211 (revision 4, source checked 26 Oct 2026, 15:32 UTC)
Inventory: none attached. This brief comes from a public page and does not say whether any deployment is affected.
Severity: High (CVSS 8.7)
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.20261003002531-6258dcebc4e2. A vendor fix does not mean a deployment is fixed.

## Affected components
- Go github.com/xuri/excelize/v2: affected >= 2.8.1, < 2.11.1-0.20261003002531-6258dcebc4e2; fixed in 2.11.1-0.20261003002531-6258dcebc4e2

## 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/GO-2026-6695 (OSV record GO-2026-6695 lists affected ranges: Go github.com/xuri/excelize/v2 >=2.8.1 <2.11.1-0.20261003002531-6258dcebc4e2 (fixed))
- Verified: https://osv.dev/vulnerability/GHSA-mx22-3794-2vpv (OSV record GHSA-mx22-3794-2vpv lists affected ranges: Go github.com/xuri/excelize/v2 >=2.8.1 <2.11.1-0.20261003002531-6258dcebc4e2 (fixed))
- Verified: https://github.com/advisories/GHSA-mx22-3794-2vpv (GitHub-reviewed advisory GHSA-mx22-3794-2vpv lists affected ranges: Go github.com/xuri/excelize/v2 >=2.8.1 <2.11.1-0.20261003002531-6258dcebc4e2)

Commands are suggestions: review each one before running it.

Loading voting…