CVE-2026-107224

MEDIUMPre-NVD 6.56.5
EchelonGraph scoreHIGH confidence

“—” beside the score: it is equal to the CVSS score beside it.

Score 6.5 from GitHub Security Advisory (severity: MODERATE) published 2026-10-07. A secondary CVSS source baseline 6.5; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: EPSS, GitHub Security Advisory, a secondary CVSS source
Trending — 4 sources updated this weekElevated

Also known asEUVD-2026-94555 (ENISA EUVD) · GHSA-fw94-4wwp-w8pw (GitHub Security Advisories)Source: ENISA EUVD

6.5EG
EchelonGraph verdictPlan a fixRemediate within your standard update timelines (the SSVC decision on this page).
  • CISA's Vulnrichment rates exploitation as PoC; EchelonGraph holds no exploit-code reference for it
CISA-KEV: Not listedEPSS PROB: 0.3%CVSS: 6.5Exploit: No code on recordExposed services: Not assessed

A fix is available — apply it.

Excelize is a Go language library for reading and writing Microsoft Excel spreadsheets. From 2.1.0 to 2.11.0, a Zip64 uncompressed size with the high bit set is converted from uint64 to a negative int64 before signed size-limit checks and allocation. ReadZipReader obtains UncompressedSize64 through FileInfo.Size and passes the wrapped negative value to readFile. When a crafted Zip64 entry declares an uncompressed size from 2^63 through 2^64-1 and the workbook is opened, the negative size bypasses unzip limits and reaches make as a negative capacity, allowing an attacker to panic during workbook opening. No fixed version is available as of this review.

CVSS v3
6.5
EG Score
6.5MEDIUMhigh confidence
EG Risk
45
EG Risk 45/100

EG Risk is EchelonGraph's 0–100 priority score. It fuses impact severity (EG Severity, the CVSS base score, never the KEV-floored or EPSS-lifted EG Score) with real-world exploitation and automatability, under weights EchelonGraph set by hand, so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner.

How it’s computed (value × EchelonGraph’s weight)
Severity65% × 45%
Impact severity (EG Severity): CVSS 6.5 of 10. Never the KEV-floored or EPSS-lifted EG Score.
Exploitation40% × 40%
EchelonGraph's fixed weight for EG-KEV Tier 3 (Elevated): a constant, not a probability.
Automatability0% × 15%
CISA's SSVC Automatable value: no (Vulnrichment).
SSVC (CISA's decision table, applied by EchelonGraph): Track at low or medium mission impact; Track* at high (mission-essential systems).
Exploitation public PoC (CISA Vulnrichment) · Automatable no (CISA Vulnrichment) · Technical impact partial (CISA Vulnrichment). All three are CISA's SSVC values (Vulnrichment). EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE.
Action: A fix is available. Apply it within your standard update timelines.
EPSS PROB
0.3%
EPSS %ILE
23rd
KEV
Not listed

What the EG score is made of (scorer v4.0: the three questions the 0–10 score mixes, published apart · methodology)

The EG score (6.5): severity, escalated by confirmed exploitation. This CVE's 6.5 is its impact severity (EG Severity), not escalated.

EG Severity
6.5 MEDIUMCVSS-B, impact only: no KEV listing, EPSS or EG-KEV tier raises it.GitHub Security Advisory CVSS
EG Likelihood
0.3% within 30 daysSource: FIRST EPSS (model v2026.06.15, score date 2026-10-31). FIRST's exploitation probability, not an EchelonGraph model.
Confirmed exploitation
None on record (CISA KEV, EG-KEV Tier 1)Reported apart from the likelihood: an observed fact, not a probability.
EG Priority
SSVC Track at medium mission impactTrack at low or medium mission impact; Track* at high (mission-essential systems).CISA BOD 26-04: 60 days if the affected system is publicly exposed; Fix on system upgrade if it is not.Each input and its source, and whom BOD 26-04 binds: the SSVC and BOD 26-04 blocks below.

SSVC (CISA's decision table, applied by EchelonGraph)Track at low or medium mission impact; Track* at high (mission-essential systems).

A fix is available. Apply it within your standard update timelines.

Exploitation public PoC (CISA Vulnrichment) · Automatable no (CISA Vulnrichment) · Technical impact partial (CISA Vulnrichment). All three are CISA's SSVC values (Vulnrichment). EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE. Mission impact is CISA's Mission & Well-being decision point, and only you can judge it. CISA's table makes it high when Mission Prevalence is Essential — the vulnerable component "directly provides capabilities that constitute at least one MEF for at least one entity" (MEF: mission essential function) — or when Public Well-Being Impact is Irreversible: "multiple fatalities are likely", the cyber-physical system "is likely lost or destroyed", "extreme or serious externalities" are imposed on other parties, or social systems such as elections or the financial grid "are destabilized and potentially collapse". CISA's decision table

BOD 26-04 (CISA's remediation timeline, Table 1)60 days if the affected system is publicly exposed; Fix on system upgrade if it is not.

The score's inputs: In CISA KEV no (CISA's KEV catalog) · Automatable no (CISA Vulnrichment) · Technical impact partial (CISA Vulnrichment). Whether your system is publicly exposed is yours to answer. BOD 26-04 binds US Federal Civilian Executive Branch agencies; for anyone else it is CISA's published timeline, a reference rather than an obligation. The directive · how EchelonGraph applies it

Published

October 7, 2026

Last Modified

October 13, 2026

Advisory Details (3)

Auto-updated Oct 7, 2026
Patch available. Sources: github, github_commit, github_pr.
GitHub advisoryMentions a patch (unverified)

A Zip64 uncompressed-size of 2^63 casts to a negative int64 that bypasses the unzip-size guard and reaches make([]byte, 0, negativeCap) · Advisory · qax-os/excelize · GitHub

https://github.com/qax-os/excelize/security/advisories/GHSA-fw94-4wwp-w8pw
GitHub pull request

Reject a Zip64 uncompressed size that does not fit a signed int64

Fix merged in qax-os/excelize PR #2369 on 2026-08-05 — awaiting tagged release

https://github.com/qax-os/excelize/pull/2369
GitHub commit

commit db93f8d89de7 (qax-os/excelize)

Fix landed in qax-os/excelize commit db93f8d89de7 — awaiting tagged release

https://github.com/qax-os/excelize/commit/db93f8d89de71589069a54d1b998af02e3c5f7cd

Vendor Advisories for CVE-2026-107224(1)

These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.

Patch Availability(1)

Vendor / EcosystemFix (by version range) / PatchReleasedSource
gogithub.com/xuri/excelize/v2 @ 2.11.1-0.20260805032953-db93f8d89de7 (fixes >= 2.1.0, < 2.11.1-0.20260805032953-db93f8d89de7)—ghsa

Patches are aggregated from vendor advisories (Red Hat, Microsoft, Cisco, GitHub) and package ecosystems (OSV, GHSA). Multiple rows for the same upstream release have been deduplicated.

Affected Packages

(1 across 1 ecosystem)
Go(1)
PackageVulnerable rangeFix by version rangeDependents
github.com/xuri/excelize/v2—
  • 2.1.0 up to 2.11.1-0.20260805032953-db93f8d89de7: fixed in 2.11.1-0.20260805032953-db93f8d89de7
—

Weakness Classification(2)

MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.

Data Freshness Timeline

(refreshed 10× in last 7d / 43× in last 30d)

Each row is a time one of our pipelines fetched, updated or re-scored this CVE. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. An arrow marks a change the record states ("CVSS v3 → 9.1"); EPSS and GHSA rows show the values recorded at that time, not what changed (EPSS values are rounded; hover one for the exact figures). Most recent first.

  1. 2026-11-02 16:43 UTCEPSS rescoreEPSS 0.3% · 23rd percentile
  2. 2026-11-01 16:33 UTCEPSS rescoreEPSS 0.3% · 23rd percentile
  3. 2026-11-01 08:00 UTCGHSA enrichmentGHSA-fw94-4wwp-w8pw · GitHub severity MODERATE · GitHub CVSS 6.5
  4. 2026-11-01 08:00 UTCEG score recompute
  5. 2026-10-31 16:31 UTCEPSS rescoreEPSS 0.3% · 23rd percentile
  6. 2026-10-30 16:33 UTCEPSS rescoreEPSS 0.3% · 23rd percentile
  7. 2026-10-29 16:32 UTCEPSS rescoreEPSS 0.3% · 23rd percentile
  8. 2026-10-28 16:31 UTCEPSS rescoreEPSS 0.3% · 23rd percentile
  9. 2026-10-27 16:31 UTCEPSS rescoreEPSS 0.3% · 23rd percentile
  10. 2026-10-27 11:25 UTCOSV refresh
  11. 2026-10-26 16:30 UTCEPSS rescoreEPSS 0.3% · 23rd percentile
  12. 2026-10-25 16:32 UTCEPSS rescoreEPSS 0.3% · 23rd percentile
  13. 2026-10-25 14:54 UTCEG score recompute
  14. 2026-10-24 16:32 UTCEPSS rescoreEPSS 0.3% · 22nd percentile
  15. 2026-10-23 16:31 UTCEPSS rescoreEPSS 0.3% · 22nd percentile
  16. 2026-10-22 16:33 UTCEPSS rescoreEPSS 0.3% · 22nd percentile
  17. 2026-10-21 16:32 UTCEPSS rescoreEPSS 0.3% · 22nd percentile
  18. 2026-10-20 16:32 UTCEPSS rescoreEPSS 0.3% · 22nd percentile
  19. 2026-10-19 16:31 UTCEPSS rescoreEPSS 0.3% · 22nd percentile
  20. 2026-10-18 16:31 UTCEPSS rescoreEPSS 0.3% · 21st percentile
  21. 2026-10-18 05:07 UTCEG score recompute
  22. 2026-10-17 16:33 UTCEPSS rescoreEPSS 0.3% · 21st percentile
  23. 2026-10-16 16:40 UTCEPSS rescoreEPSS 0.3% · 21st percentile
  24. 2026-10-15 16:31 UTCEPSS rescoreEPSS 0.3% · 21st percentile
  25. 2026-10-14 16:32 UTCEPSS rescoreEPSS 0.3% · 21st percentile
Show 18 more
  1. 2026-10-13 16:33 UTCEPSS rescoreEPSS 0.4% · 27th percentile
  2. 2026-10-12 16:38 UTCEG score recompute
  3. 2026-10-12 16:33 UTCEPSS rescoreEPSS 0.4% · 27th percentile
  4. 2026-10-11 20:14 UTCEG score recompute
  5. 2026-10-11 18:26 UTCEG score recompute
  6. 2026-10-11 15:00 UTCEG score recompute
  7. 2026-10-11 13:47 UTCEPSS rescoreEPSS 0.4% · 27th percentile
  8. 2026-10-10 23:14 UTCEG score recompute
  9. 2026-10-10 19:59 UTCEPSS rescoreEPSS 0.4% · 27th percentile
  10. 2026-10-09 21:55 UTCEG score recompute
  11. 2026-10-09 20:06 UTCEPSS rescoreEPSS 0.4% · 27th percentile
  12. 2026-10-08 20:37 UTCEG score recompute
  13. 2026-10-08 17:11 UTCEPSS rescoreEPSS 0.4% · 27th percentile
  14. 2026-10-07 20:22 UTCEG score recompute
  15. 2026-10-07 19:43 UTCEG score recompute
  16. 2026-10-07 19:20 UTCEG score recompute
  17. 2026-10-07 19:02 UTCEG score recomputeFirst assessed: 6.5 MEDIUM
  18. 2026-10-07 19:01 UTCMITRE cvelistV5first tracked

Related CVEs(same product + same CWE)

Frequently asked(5)

What is CVE-2026-107224?
CVE-2026-107224 is a medium-severity vulnerability; its CVE record was published on October 7, 2026. Excelize is a Go language library for reading and writing Microsoft Excel spreadsheets. From 2.1.0 to 2.11.0, a Zip64 uncompressed size with the high bit set is converted from uint64 to a negative int64 before signed size-limit checks and allocation. ReadZipReader obtains UncompressedSize64 through…
When was the CVE record for CVE-2026-107224 published?
The CVE record for CVE-2026-107224 was published on October 7, 2026. That is the record's publication date; the vulnerability itself may have been made public earlier. EchelonGraph's copy of the record carries a last-modified date of October 13, 2026; the record at its source may have been updated since.
Is CVE-2026-107224 actively exploited?
CVE-2026-107224 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.3% probability of exploitation in the next 30 days (23rd percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2026-107224?
CVE-2026-107224 has a CVSS base score of 6.5 (a secondary CVSS source that NVD displays; NVD's own analysis pending).
How do I remediate CVE-2026-107224?
A fix for CVE-2026-107224 is available: update to the fixed version the vendor names in its advisory. The vendor advisories EchelonGraph has for CVE-2026-107224 are linked in the Vendor Advisories panel on this page.

Dependency Blast Radius

See which npm, PyPI, Go, and Maven packages are affected by CVE-2026-107224

Explore →

Is Your Infrastructure Affected by CVE-2026-107224?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.

Book a Demo →Browse All CVEs