CVE-2026-107213

waiting for further signalsZero needs more public information before it can validate it.

GHSA-r7x5-4969-99p7 ↗EUVD-2026-94530 ↗

no check availablenot proven exploitable
cve.orgpublic pocExploit code has been published by someone. Source signals can also carry a PoC (Proof of Concept).kevAttacks confirmed in the real world.
qax-os excelize >= 2.9.0, <= 2.11.0
CWE-476 NULL Pointer Dereference
ETK-2026-902, permanent identifier
pkg:golang/github.com/xuri/excelize/v2
14d 03h 28msince last run
12mAI analysisAnalysis: how long the AI spent reversing this signal.
timeline
0 = cve.org publication
trigger signal (cve.org) +0hwaiting for further signals+1h29m
0
+4h
+6h
+8h
+10h
+12h

description

Excelize 2.9.0 through 2.11.0 can terminate an application processing a malicious spreadsheet through GetSlicers. An attacker must be able to provide a workbook that is processed by that method and has extension metadata without corresponding drawing information.

mitigation

Do not call GetSlicers on untrusted workbooks, and isolate spreadsheet processing so a panic cannot terminate the main service. Restrict acceptance of untrusted spreadsheet files until a fixed Excelize release is published.

check
no
exploit
no
automationDeterministic: a check that runs on its own, the same request on every target. Contextual: an agentic technique that needs to be applied per target, for bugs that depend on contextual flows.
–
auth requiredWhether an attacker needs an account first, based on the CVSS vector's Privileges Required.
no
EPSSEstimate of the chance this CVE is exploited in the next 30 days. Refreshed daily.
0.22%11th percentile
agent run time
12m
cve.org record, t = 0The moment cve.org publishes the CVE in full.
2026-10-07 17:40Z
Δ to public pocExploit code has been published by someone. Source signals can also carry a PoC (Proof of Concept).
–
Δ to kevAttacks confirmed in the real world.
–

outcome

No artifact: an exploit or check was attempted but could not be produced at this moment.

source signals

Public signals that triggered or updated the pipeline. These are inputs for the deltas above.

  1. 2026-10-07 17:40Z
    cve_org: trigger signal, started the run

this entry in the feed

GET /api/v1/feed/CVE-2026-107213

{
  "etk_id": "ETK-2026-902",
  "cve_id": "CVE-2026-107213",
  "display_id": "CVE-2026-107213",
  "ghsa_id": "GHSA-r7x5-4969-99p7",
  "euvd_id": "EUVD-2026-94530",
  "status": "published",
  "anchor_state": "anchored",
  "title": "Nil pointer dereference in Excelize GetSlicers",
  "summary": "Excelize 2.9.0 through 2.11.0 can terminate an application processing a malicious spreadsheet through GetSlicers. An attacker must be able to provide a workbook that is processed by that method and has extension metadata without corresponding drawing information.",
  "mitigation": "Do not call GetSlicers on untrusted workbooks, and isolate spreadsheet processing so a panic cannot terminate the main service. Restrict acceptance of untrusted spreadsheet files until a fixed Excelize release is published.",
  "vendor": "qax-os",
  "product": "excelize",
  "affected": [
    {
      "affected_notes": [],
      "affected_ranges": [
        ">= 2.9.0, <= 2.11.0"
      ],
      "ecosystem": "go",
      "fixed_versions": [],
      "package_name": "github.com/xuri/excelize/v2",
      "purl": "pkg:golang/github.com/xuri/excelize/v2"
    }
  ],
  "cwes": [
    476
  ],
  "cvss_score": 8.7,
  "cvss_src": "cna_vendor",
  "cvss_vector": "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",
  "epss_score": 0.0022,
  "epss_percentile": 0.115,
  "epss_asof": "2026-10-21",
  "automation": "deterministic",
  "check": false,
  "check_confidence_basis": null,
  "exploit": false,
  "pipeline_minutes": 12.346092216666667,
  "t0_at": "2026-10-07T17:40:29.865000+00:00",
  "signals": {
    "trigger_signal": {
      "at": "2026-10-07T17:40:29.865000+00:00",
      "days": 0,
      "is_lower_bound": false,
      "measured_at": "2026-10-07T17:40:29.865000+00:00",
      "url": "https://www.cve.org/CVERecord?id=CVE-2026-107213"
    }
  }
}

published 2026-10-07 18:57Z
last change 2026-10-21 21:36Z

Need the technical details behind an entry?

Every entry here shows what we attempted and when. The technical details, the generated exploit that fired it and the evidence behind the verdict are not public. Tell us about your use case and we’ll get back to you about extended API access.