Skip to content
Patch Next
Sign inAdd to your agent

← Actionable
High, CVSS 8.7amended

Excelize: Nil-pointer dereference in GetSlicers when a worksheet has extLst present but no drawing element

CVE-2026-107213GHSA-r7x5-4969-99p7

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.20260929015830-8ffeb07ec9a3), 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-107213: 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 GetSlicers guards only if ws.ExtLst == nil { return } (slicer.go:816-818) and then immediately dereferences ws.Drawing.RID with no nil check on ws.Drawing itself. Drawing and ExtLst are two independently optional child elements of <worksheet in xl/worksheets/sheetN.xml, populated separately by encoding/xml depending on whether each tag is present. I executed a PoC: took a plain NewFile() workbook (no drawing, no slicer), saved it, then injected a bare <extLst</extLst immediately before </worksheet in xl/worksheets/sheet1.xml (no other change, no drawing element present) and called GetSlicers. Result: runtime error: invalid memory address or nil pointer dereference, confirmed at the ws.Drawing.RID line via stack trace. Reachability / who can trigger this Unauthenticated: any application that opens an untrusted .xlsx and calls the public File.GetSlicers(sheet) API. The trigger is a single empty XML tag with no valid slicer or drawing content required at all, making it an even…

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

    Amended from ghsa record GHSA-r7x5-4969-99p7

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

  4. Revision 1 · created ·

    Published from osv record GHSA-r7x5-4969-99p7

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

Advisory: Excelize: Nil-pointer dereference in GetSlicers when a worksheet has extLst present but no drawing element
IDs: CVE-2026-107213, GHSA-r7x5-4969-99p7
Record: https://patchnext.com/advisories/cve-2026-107213 (revision 4, 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: 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.20260929015830-8ffeb07ec9a3. A vendor fix does not mean a deployment is fixed.

## Affected components
- Go github.com/xuri/excelize/v2: affected >= 2.9.0, < 2.11.1-0.20260929015830-8ffeb07ec9a3; fixed in 2.11.1-0.20260929015830-8ffeb07ec9a3

## 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-6687 (OSV record GO-2026-6687 lists affected ranges: Go github.com/xuri/excelize/v2 >=2.9.0 <2.11.1-0.20260929015830-8ffeb07ec9a3 (fixed))
- Verified: https://osv.dev/vulnerability/GHSA-r7x5-4969-99p7 (OSV record GHSA-r7x5-4969-99p7 lists affected ranges: Go github.com/xuri/excelize/v2 >=2.9.0 <2.11.1-0.20260929015830-8ffeb07ec9a3 (fixed))
- Verified: https://github.com/advisories/GHSA-r7x5-4969-99p7 (GitHub-reviewed advisory GHSA-r7x5-4969-99p7 lists affected ranges: Go github.com/xuri/excelize/v2 >=2.9.0 <2.11.1-0.20260929015830-8ffeb07ec9a3)

Commands are suggestions: review each one before running it.

Loading voting…