VulnSocial

CVE-2026-107213

LOWCVSS 8.7 · HIGH

Signal is active with 1 mentions in latest observed window

Immediate actions

  • Track advisory updates for patch or workaround availability

Recommended action window: Monitor and triage in normal cycle

NVD description

Excelize is a Go language library for reading and writing Microsoft Excel spreadsheets. From 2.9.0 to 2.11.0, GetSlicers checks for ExtLst but dereferences ws.Drawing without checking whether the independently optional drawing element exists. File.GetSlicers reads ws.Drawing.RID after seeing a worksheet extLst element even when the independently optional worksheet drawing element is absent. When a crafted worksheet contains an extLst element without a drawing element and the application calls GetSlicers, the nil ws.Drawing pointer is dereferenced while resolving the drawing relationship, allowing an attacker to panic and terminate an unprotected process. No fixed version is available as of this review.

Back to dashboard
0.0/ 10 priority

Sources & remediation

Other references
Weakness type (CWE)
CWE-476

Priority

LOW

Exploitation

NONE

PoC

NONE

Patch

NONE

Momentum

NONE

Threat summary

  • 1 mentions across 1 observed day

What's happening

  • 1 total mentions across 1 day

Deep dive

Activity timeline1 mentions / 1d
00111Mentions · 2026-10-09: 110-09
Referenced assets2 URLs
By indicator
Full discourse1 post
  • Upwind Security MDR@UpwindMDR

    🚨High - Excelize Crafted XLSX Panic DoS (CVE-2026-107211, CVE-2026-107213) Two flaws in http://github.com/xuri/excelize/v2 let a crafted spreadsheet crash any Go process that reads it: CVE-2026-107211: GetPivotTables indexes the pivot-cache field list with attacker-controlled field indices from a separate pivot-table part, with no bounds check, causing an index-out-of-range panic. CVE-2026-107213: GetSlicers checks only that extLst exists, then dereferences the worksheet's drawing element without a nil check, causing a nil-pointer panic. 👉Affected: Excelize 2.8.1 – 2.11.0 (CVE-2026-107211), 2.9.0 – 2.11.0 (CVE-2026-107213). Fixed only in master commits, no tagged release yet.

    0001093
    315 followersView on X

Explore more

Back to dashboard