CVE-2026-107215

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

GHSA-x2q3-8cjh-766f ↗EUVD-2026-94533 ↗

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.3.1, <= 2.11.0
CWE-789 Memory Allocation with Excessive Size Value
ETK-2026-911, permanent identifier
pkg:golang/github.com/xuri/excelize/v2
13d 23h 14msince last run
14mAI analysisAnalysis: how long the AI spent reversing this signal.
timeline
0 = cve.org publication
trigger signal (cve.org) +0hwaiting for further signals+3h44m
0
+2h
+6h
+8h
+10h
+12h

description

qax-os excelize versions 2.3.1 through 2.11.0 may use untrusted OLE compound-file stream lengths when allocating memory. An attacker who can cause the application to process a crafted spreadsheet can trigger a panic or exhaust available memory.

mitigation

Do not process untrusted OLE compound spreadsheet files with affected versions, and apply resource limits or isolation to processes that handle uploads. No fixed version is recorded; monitor the project for an update.

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.23%12th percentile
agent run time
14m
cve.org record, t = 0The moment cve.org publishes the CVE in full.
2026-10-07 17:48Z
Δ 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:48Z
    cve_org: trigger signal, started the run

this entry in the feed

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

{
  "etk_id": "ETK-2026-911",
  "cve_id": "CVE-2026-107215",
  "display_id": "CVE-2026-107215",
  "ghsa_id": "GHSA-x2q3-8cjh-766f",
  "euvd_id": "EUVD-2026-94533",
  "status": "published",
  "anchor_state": "anchored",
  "title": "Unchecked allocation size denial of service in qax-os excelize",
  "summary": "qax-os excelize versions 2.3.1 through 2.11.0 may use untrusted OLE compound-file stream lengths when allocating memory. An attacker who can cause the application to process a crafted spreadsheet can trigger a panic or exhaust available memory.",
  "mitigation": "Do not process untrusted OLE compound spreadsheet files with affected versions, and apply resource limits or isolation to processes that handle uploads. No fixed version is recorded; monitor the project for an update.",
  "vendor": "qax-os",
  "product": "excelize",
  "affected": [
    {
      "affected_notes": [],
      "affected_ranges": [
        ">= 2.3.1, <= 2.11.0"
      ],
      "ecosystem": "go",
      "fixed_versions": [],
      "package_name": "github.com/xuri/excelize/v2",
      "purl": "pkg:golang/github.com/xuri/excelize/v2"
    }
  ],
  "cwes": [
    789
  ],
  "cvss_score": 7.5,
  "cvss_src": "cna_vendor",
  "cvss_vector": "CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H",
  "epss_score": 0.0023,
  "epss_percentile": 0.1269,
  "epss_asof": "2026-10-20",
  "automation": "deterministic",
  "check": false,
  "check_confidence_basis": null,
  "exploit": false,
  "pipeline_minutes": 14.483863466666667,
  "t0_at": "2026-10-07T17:48:03.233000+00:00",
  "signals": {
    "trigger_signal": {
      "at": "2026-10-07T17:48:03.233000+00:00",
      "days": 0,
      "is_lower_bound": false,
      "measured_at": "2026-10-07T17:48:03.233000+00:00",
      "url": "https://www.cve.org/CVERecord?id=CVE-2026-107215"
    }
  }
}

published 2026-10-07 21:18Z
last change 2026-10-21 19:54Z

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.