CVE-2026-107223

HIGHNVD 7.57.5
EchelonGraph scoreMEDIUM confidence

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

This high-severity CVE scores 7.5 under NVD CVSS v3. EPSS exploit probability: 0.4% (30th percentile of EPSS-scored CVEs). No GitHub Security Advisory CVSS is on record for this CVE.

Triggered by: Headline CVSS from NVD CVSS v3
Sources: EPSS, NVD CVSS v3
Trending — 3 sources updated this week

Also known asEUVD-2026-94554 (ENISA EUVD) · GHSA-fq3v-74gv-27gm (GitHub Security Advisories)Source: ENISA EUVD

7.5EG
EchelonGraph verdictPlan a fixRemediate within your standard update timelines (the SSVC decision on this page).
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 0.4%CVSS: 7.5Exploit: None knownExposed 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, flatCols expands file-loaded column ranges without validating Min and Max against the worksheet column limit. SetColWidth reaches flatCols, which expands xlsxCol.Min through xlsxCol.Max without enforcing MaxColumns. When a crafted worksheet supplies an oversized col max attribute and the application invokes a column mutator, flatCols performs a deep copy and append for every attacker-selected column number, allowing an attacker to consume excessive CPU and memory or trigger OOM. No fixed version is available as of this review.

CVSS v3
7.5
EG Score
7.5HIGHmedium confidence
EG Risk
34
EG Risk 34/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)
Severity75% × 45%
Impact severity (EG Severity): CVSS 7.5 of 10. Never the KEV-floored or EPSS-lifted EG Score.
Exploitation0.4% × 40%
FIRST EPSS: the 30-day exploitation probability when EchelonGraph scored this CVE.
Automatability0% × 15%
CISA's SSVC Automatable value: no (Vulnrichment).
SSVC (CISA's decision table, applied by EchelonGraph): Track at every mission impact level.
Exploitation none (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.4%
EPSS %ILE
30th
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 (7.5): severity, escalated by confirmed exploitation. This CVE's 7.5 is its impact severity (EG Severity), not escalated.

EG Severity
7.5 HIGHCVSS-B, impact only: no KEV listing, EPSS or EG-KEV tier raises it.NVD CVSS v3 · CVSS v3.0 or v3.1
EG Likelihood
0.4% 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 every mission impact level.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 every mission impact level.

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

Exploitation none (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_commit, github_pr, github.
GitHub advisoryMentions a patch (unverified)

Unbounded <col max> attribute is loaded with no MaxColumns check and expanded per-column by flatCols(), so any column mutator hangs or OOMs the process · Advisory · qax-os/excelize · GitHub

https://github.com/qax-os/excelize/security/advisories/GHSA-fq3v-74gv-27gm
GitHub pull request

Bound flatCols to MaxColumns when flattening worksheet columns

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

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

commit a54c578af309 (qax-os/excelize)

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

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

Vendor Advisories for CVE-2026-107223(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.20260807015645-a54c578af309 (fixes >= 2.1.0, < 2.11.1-0.20260807015645-a54c578af309)—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.20260807015645-a54c578af309: fixed in 2.11.1-0.20260807015645-a54c578af309
—

Weakness Classification(1)

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

Data Freshness Timeline

(refreshed 10× in last 7d / 46× 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.4% · 30th percentile
  2. 2026-11-01 16:33 UTCEPSS rescoreEPSS 0.4% · 30th percentile
  3. 2026-11-01 08:00 UTCGHSA enrichmentGHSA-fq3v-74gv-27gm · GitHub severity HIGH
  4. 2026-11-01 08:00 UTCEG score recompute
  5. 2026-10-31 16:31 UTCEPSS rescoreEPSS 0.4% · 30th percentile
  6. 2026-10-30 16:33 UTCEPSS rescoreEPSS 0.4% · 30th percentile
  7. 2026-10-29 16:32 UTCEPSS rescoreEPSS 0.4% · 30th percentile
  8. 2026-10-28 16:31 UTCEPSS rescoreEPSS 0.4% · 30th percentile
  9. 2026-10-27 20:38 UTCEG score recompute
  10. 2026-10-27 16:31 UTCEPSS rescoreEPSS 0.4% · 30th percentile
  11. 2026-10-26 16:30 UTCEPSS rescoreEPSS 0.4% · 30th percentile
  12. 2026-10-25 16:32 UTCEPSS rescoreEPSS 0.4% · 30th percentile
  13. 2026-10-25 14:54 UTCEG score recompute
  14. 2026-10-24 16:32 UTCEPSS rescoreEPSS 0.3% · 26th percentile
  15. 2026-10-23 16:31 UTCEPSS rescoreEPSS 0.3% · 26th percentile
  16. 2026-10-22 16:33 UTCEPSS rescoreEPSS 0.3% · 26th percentile
  17. 2026-10-21 16:32 UTCEPSS rescoreEPSS 0.3% · 26th percentile
  18. 2026-10-20 19:12 UTCEG score recompute
  19. 2026-10-20 16:32 UTCEPSS rescoreEPSS 0.3% · 26th percentile
  20. 2026-10-19 16:31 UTCEPSS rescoreEPSS 0.3% · 26th percentile
  21. 2026-10-18 16:31 UTCEPSS rescoreEPSS 0.3% · 26th percentile
  22. 2026-10-18 05:07 UTCEG score recompute
  23. 2026-10-17 16:33 UTCEPSS rescoreEPSS 0.3% · 26th percentile
  24. 2026-10-16 16:40 UTCEPSS rescoreEPSS 0.3% · 26th percentile
  25. 2026-10-15 16:31 UTCEPSS rescoreEPSS 0.3% · 26th percentile
Show 21 more
  1. 2026-10-14 16:32 UTCEPSS rescoreEPSS 0.3% · 26th percentile
  2. 2026-10-13 16:33 UTCEPSS rescoreEPSS 0.3% · 22nd percentile
  3. 2026-10-13 14:28 UTCEG score recompute▲ 0.40
  4. 2026-10-13 14:24 UTCNVD updateCVSS v3 → 7.5
  5. 2026-10-12 16:38 UTCEG score recompute
  6. 2026-10-12 16:33 UTCEPSS rescoreEPSS 0.3% · 22nd percentile
  7. 2026-10-11 20:14 UTCEG score recompute
  8. 2026-10-11 17:56 UTCEG score recompute
  9. 2026-10-11 15:00 UTCEG score recompute
  10. 2026-10-11 13:47 UTCEPSS rescoreEPSS 0.3% · 22nd percentile
  11. 2026-10-11 06:22 UTCEG score recompute
  12. 2026-10-10 19:59 UTCEPSS rescoreEPSS 0.3% · 22nd percentile
  13. 2026-10-10 07:15 UTCEG score recompute
  14. 2026-10-09 20:06 UTCEPSS rescoreEPSS 0.3% · 22nd percentile
  15. 2026-10-08 20:37 UTCEG score recompute
  16. 2026-10-08 17:11 UTCEPSS rescoreEPSS 0.3% · 22nd percentile
  17. 2026-10-07 23:28 UTCEG score recompute
  18. 2026-10-07 22:17 UTCEG score recompute
  19. 2026-10-07 19:20 UTCEG score recompute
  20. 2026-10-07 19:02 UTCEG score recomputeFirst assessed: 7.1 HIGH
  21. 2026-10-07 19:01 UTCMITRE cvelistV5first tracked

Related CVEs(same product + same CWE)

Frequently asked(5)

What is CVE-2026-107223?
CVE-2026-107223 is a high-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, flatCols expands file-loaded column ranges without validating Min and Max against the worksheet column limit. SetColWidth reaches flatCols, which expands xlsxCol.Min through xlsxCol.Max…
When was the CVE record for CVE-2026-107223 published?
The CVE record for CVE-2026-107223 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-107223 actively exploited?
CVE-2026-107223 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.4% probability of exploitation in the next 30 days (30th percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2026-107223?
CVE-2026-107223 has a CVSS v3 base score of 7.5 (NVD).
How do I remediate CVE-2026-107223?
A fix for CVE-2026-107223 is available: update to the fixed version the vendor names in its advisory. The vendor advisories EchelonGraph has for CVE-2026-107223 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-107223

Explore →

Is Your Infrastructure Affected by CVE-2026-107223?

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

Book a Demo →Browse All CVEs