Is CVE-2026-107214 exploited in the wild?

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

How severe is CVE-2026-107214?

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

Which products and versions are affected?

github.com/360EntSecGroup-Skylar/excelize/v2 (Go) SEMVER:introduced=2.3.1; github.com/xuri/excelize/v2 (Go) >= 2.3.1, < 2.11.1-0.20260915055537-22f76f9acb94, SEMVER:introduced=0,fixed=2.11.1-0.20260915055537-22f76f9acb94, SEMVER:introduced=2.3.1,fixed=2.11.1-0.20260915055537-22f76f9acb94; Xuri Excelize before fix.

How is CVE-2026-107214 attacked?

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

Am I affected by CVE-2026-107214?

Check whether you run github.com/360EntSecGroup-Skylar/excelize/v2 (Go), github.com/xuri/excelize/v2 (Go) or Xuri 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-107214: Excelize Decrypt panic on malformed OLE encrypted workbooks

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

Yes. github.com/xuri/excelize/v2 (Go): upgrade to 2.11.1-0.20260915055537-22f76f9acb94 or later. Until then: A recover() boundary in the Decrypt function mapping panics to ErrWorkbookFileFormat error is the primary fix. Per-site length validation of OLE encryption structures is recommended as defense in depth. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.

Q: How is CVE-2026-107214 attacked?

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

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

Check whether you run github.com/360EntSecGroup-Skylar/excelize/v2 (Go), github.com/xuri/excelize/v2 (Go) or Xuri 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-107214 · Severity: high · CVSS 7.5 · Published 2026-10-08

Excelize is a Go library for reading and writing Excel spreadsheets. An attacker can craft a malformed encrypted spreadsheet file that causes the library to crash with an unrecovered panic when processing uploads or conversions, disrupting service availability without requiring authentication or a valid password.

Technologies: github.com/360EntSecGroup-Skylar/excelize/v2 (Go), github.com/xuri/excelize/v2 (Go), Xuri Excelize. Vendors: Go, Xuri.

Quick answers

Is CVE-2026-107214 exploited in the wild?: No. Junglewise Threat Intelligence has no report of CVE-2026-107214 being exploited in the wild.
How severe is CVE-2026-107214?: High severity, with a CVSS score of 7.5, published 8 October 2026.
Which products and versions are affected?: github.com/360EntSecGroup-Skylar/excelize/v2 (Go) SEMVER:introduced=2.3.1; github.com/xuri/excelize/v2 (Go) >= 2.3.1, < 2.11.1-0.20260915055537-22f76f9acb94, SEMVER:introduced=0,fixed=2.11.1-0.20260915055537-22f76f9acb94, SEMVER:introduced=2.3.1,fixed=2.11.1-0.20260915055537-22f76f9acb94; Xuri Excelize before fix.
Is there a fix for CVE-2026-107214?: Yes. github.com/xuri/excelize/v2 (Go): upgrade to 2.11.1-0.20260915055537-22f76f9acb94 or later. Until then: A recover() boundary in the Decrypt function mapping panics to ErrWorkbookFileFormat error is the primary fix. Per-site length validation of OLE encryption structures is recommended as defense in depth. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
How is CVE-2026-107214 attacked?: It is attacked over the network, in a software library.
Am I affected by CVE-2026-107214?: Check whether you run github.com/360EntSecGroup-Skylar/excelize/v2 (Go), github.com/xuri/excelize/v2 (Go) or Xuri 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.20260915055537-22f76f9acb94 or later
```
go get github.com/xuri/excelize/v2@v2.11.1-0.20260915055537-22f76f9acb94
```

A recover() boundary in the Decrypt function mapping panics to ErrWorkbookFileFormat error is the primary fix. Per-site length validation of OLE encryption structures is recommended as defense in depth.

Technical details

The vulnerability exists in the Decrypt function and its callees (standardDecrypt, agileDecrypt), which process OLE compound-file encrypted workbooks. Multiple code paths perform slice accesses without prior validation of buffer lengths and structure fields, including zero-valued KeySize and missing EncryptedPackage streams. Attackers can trigger panics during the initial structural parsing phase before any legitimate decryption occurs; panics bypass the documented error-handling contract and terminate the process.

Affected products

xuri Excelize before fix

Identifiers

CVE-2026-107214
GHSA-2j4c-ffch-9f23
GO-2026-6684

Timeline

2026-10-08: disclosed

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