Is CVE-2026-107213 exploited in the wild?

No. Junglewise Threat Intelligence has no report of CVE-2026-107213 being exploited in the wild.

How severe is CVE-2026-107213?

High severity, with a CVSS score of 4, published 8 October 2026.

Which products and versions are affected?

github.com/xuri/excelize/v2 (Go) >= 2.9.0, < 2.11.1-0.20260929015830-8ffeb07ec9a3, SEMVER:introduced=2.9.0,fixed=2.11.1-0.20260929015830-8ffeb07ec9a3; Qax-Os Excelize up to v2.11.0 (commit e81f050).

Is there a fix for CVE-2026-107213?

Yes. github.com/xuri/excelize/v2 (Go): upgrade to 2.11.1-0.20260929015830-8ffeb07ec9a3 or later. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.

How is CVE-2026-107213 attacked?

It is attacked over the network, in a software library.

Am I affected by CVE-2026-107213?

Check whether you run github.com/xuri/excelize/v2 (Go) or Qax-Os Excelize at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.

CVE-2026-107213: Excelize nil-pointer dereference in GetSlicers

Q: Is there a fix for CVE-2026-107213?

Yes. github.com/xuri/excelize/v2 (Go): upgrade to 2.11.1-0.20260929015830-8ffeb07ec9a3 or later. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.

Q: How is CVE-2026-107213 attacked?

It is attacked over the network, in a software library.

Q: Am I affected by CVE-2026-107213?

Check whether you run github.com/xuri/excelize/v2 (Go) or Qax-Os Excelize at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.

CVE-2026-107213 · Severity: high · CVSS 4 · Published 2026-10-08

Excelize is a Go library for reading and writing Excel spreadsheet files. When an application uses the GetSlicers function to extract data filters from a worksheet in an untrusted .xlsx file, a specially crafted file with an empty extLst XML element can trigger a denial of service by crashing the application. No user interaction or authentication is required beyond opening the malicious file.

Technologies: github.com/xuri/excelize/v2 (Go). Vendors: Go.

Quick answers

Is CVE-2026-107213 exploited in the wild?: No. Junglewise Threat Intelligence has no report of CVE-2026-107213 being exploited in the wild.
How severe is CVE-2026-107213?: High severity, with a CVSS score of 4, published 8 October 2026.
Which products and versions are affected?: github.com/xuri/excelize/v2 (Go) >= 2.9.0, < 2.11.1-0.20260929015830-8ffeb07ec9a3, SEMVER:introduced=2.9.0,fixed=2.11.1-0.20260929015830-8ffeb07ec9a3; Qax-Os Excelize up to v2.11.0 (commit e81f050).
Is there a fix for CVE-2026-107213?: Yes. github.com/xuri/excelize/v2 (Go): upgrade to 2.11.1-0.20260929015830-8ffeb07ec9a3 or later. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
How is CVE-2026-107213 attacked?: It is attacked over the network, in a software library.
Am I affected by CVE-2026-107213?: Check whether you run github.com/xuri/excelize/v2 (Go) or Qax-Os Excelize at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.

How to fix

github.com/xuri/excelize/v2 (Go): upgrade to 2.11.1-0.20260929015830-8ffeb07ec9a3 or later
```
go get github.com/xuri/excelize/v2@v2.11.1-0.20260929015830-8ffeb07ec9a3
```

Technical details

A nil-pointer dereference (CWE-476) occurs in the GetSlicers function when a worksheet has an extLst XML element present but no Drawing element. The code checks if ExtLst is nil but then immediately dereferences ws.Drawing.RID without verifying that the Drawing pointer itself is non-nil. An attacker can craft a .xlsx file with a bare empty <extLst></extLst> tag in the worksheet XML to trigger an unhandled panic in any application that calls the public GetSlicers API on untrusted input.

Affected products

qax-os Excelize up to v2.11.0 (commit e81f050)

Identifiers

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

Timeline

2026-10-08: disclosed

This page as Markdown. Free to reuse under CC BY 4.0 with a link back.