Skip to content
Patch Next
Sign inAdd to your agent

← Actionable
High, CVSS 7.5amended

Excelize Decrypt: unrecoverable panics on malformed OLE/CFB encrypted workbooks

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

What to do

Partial vendor fix. Follow the primary source's mitigation guidance and check back for a fix.

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

  • Go github.com/360EntSecGroup-Skylar/excelize/v2

    Affected
    >= 2.3.1
    Fixed in
    no fixed version recorded

  • Go github.com/xuri/excelize/v2

    Affected
    >= 2.3.1, < 2.11.1-0.20260915055537-22f76f9acb94
    Fixed in
    2.11.1-0.20260915055537-22f76f9acb94

Sources

Severity and exploitation
Exploitation
No confirmed exploitation recorded. Patch Next marks exploitation only from CISA KEV.
CVSS
7.5 · CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H
EPSS
  • CVE-2026-107214: 0.24% estimated exploitation activity in the next 30 days; percentile 15.24 (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 Any file whose first 8 bytes are the OLE compound-file signature (D0 CF 11 E0 A1 B1 1A E1) is routed by OpenFile/OpenReader/OpenBytes → openReaderAt → Decrypt. The version dispatch only guarantees len(EncryptionInfo) = 4 before handing attacker-controlled EncryptionInfo/EncryptedPackage buffers to standardDecrypt/agileDecrypt, and no callee validates structure. Malformed but version-valid content therefore fails as an unrecovered runtime panic instead of an error, terminating the calling process. Details All panic classes below were execution-confirmed against pristine master (ecd99d761fe0, 2026-09-08). excelize.go:211-213 maps Decrypt errors to ErrWorkbookFileFormat, but panics bypass that path and kill the process. |

| Malformed input | Panic | Site | |---|---|---|---| | 1 | standard, len(EncryptionInfo) 4–11 | slice bounds [:12] | crypt.go:238 | | 2 | standard, attacker-controlled headerSize uint32 | slice bounds [12:12+headerSize] / fixed-offset header reads |…

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

    Amended from ghsa record GHSA-2j4c-ffch-9f23

  2. Revision 2 · amended ·

    Amended from osv record GO-2026-6684

  3. Revision 1 · created ·

    Published from osv record GHSA-2j4c-ffch-9f23

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

Advisory: Excelize Decrypt: unrecoverable panics on malformed OLE/CFB encrypted workbooks
IDs: CVE-2026-107214, GHSA-2j4c-ffch-9f23
Record: https://patchnext.com/advisories/cve-2026-107214 (revision 3, 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 7.5)
Exploitation: no confirmed exploitation recorded. Patch Next confirms exploitation only from CISA KEV.
Vendor response: Partial vendor fix; fixed versions by package: github.com/xuri/excelize/v2 2.11.1-0.20260915055537-22f76f9acb94. A vendor fix does not mean a deployment is fixed.

## Affected components
- Go github.com/360EntSecGroup-Skylar/excelize/v2: affected >= 2.3.1
- Go github.com/xuri/excelize/v2: affected >= 2.3.1, < 2.11.1-0.20260915055537-22f76f9acb94; fixed in 2.11.1-0.20260915055537-22f76f9acb94

## Suggested inspection (read-only)
- Go github.com/360EntSecGroup-Skylar/excelize/v2: check the installed version with your package manager.
- Go github.com/xuri/excelize/v2: check the installed version with your package manager.

## Supported action
No complete vendor fix is recorded. Follow the primary source's mitigation guidance and check this record again before closing anything.

## Required regression checks
- Run the test suite and a production build.
- Exercise the features that depend on github.com/360EntSecGroup-Skylar/excelize/v2, 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-6684 (OSV record GO-2026-6684 lists affected ranges: Go github.com/360EntSecGroup-Skylar/excelize/v2 >=2.3.1; Go github.com/xuri/excelize/v2 >=0 <2.11.1-0.20260915055537-22f76f9acb94 (fixed))
- Verified: https://osv.dev/vulnerability/GHSA-2j4c-ffch-9f23 (OSV record GHSA-2j4c-ffch-9f23 lists affected ranges: Go github.com/xuri/excelize/v2 >=2.3.1 <2.11.1-0.20260915055537-22f76f9acb94 (fixed))
- Verified: https://github.com/advisories/GHSA-2j4c-ffch-9f23 (GitHub-reviewed advisory GHSA-2j4c-ffch-9f23 lists affected ranges: Go github.com/xuri/excelize/v2 >=2.3.1 <2.11.1-0.20260915055537-22f76f9acb94)

Commands are suggestions: review each one before running it.

Loading voting…