CVE-2026-40576

CRITICALNVD 9.49.4
EchelonGraph scoreMEDIUM confidence

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

Score 9.4 from GitHub Security Advisory (severity: CRITICAL) published 2026-04-14. NVD baseline CVSS 9.4; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: EPSS, GitHub Security Advisory, NVD CVSS v3
Trending — 3 sources updated this weekElevated

Also known asEUVD-2026-24177 (ENISA EUVD) · GHSA-j98m-w3xp-9f56 (GitHub Security Advisories)Source: ENISA EUVD

9.4EG
EchelonGraph verdictPlan a fixRemediate within your standard update timelines at low or medium mission impact and sooner than that at high (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.5%CVSS: 9.4Exploit: No code on recordExposed services: Not assessed

A fix is available — apply it.

excel-mcp-server is a Model Context Protocol server for Excel file manipulation. A path traversal vulnerability exists in excel-mcp-server versions up to and including 0.1.7. When running in SSE or Streamable-HTTP transport mode (the documented way to use this server remotely), an unauthenticated attacker on the network can read, write, and overwrite arbitrary files on the host filesystem by supplying crafted filepath arguments to any of the 25 exposed MCP tool handlers. The server is intended to confine file operations to a directory set by the EXCEL_FILES_PATH environment variable. The function responsible for enforcing this boundary — get_excel_path() — fails to do so due to two independent flaws: it passes absolute paths through without any check, and it joins relative paths without resolving or validating the result. Combined with zero authentication on the default network-facing transport and a default bind address of 0.0.0.0 (all interfaces), this allows trivial remote exploitation. This vulnerability is fixed in 0.1.8.

CVSS v3
9.4
EG Score
9.4CRITICALmedium confidence
EG Risk
73
EG Risk 73/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)
Severity94% × 45%
Impact severity (EG Severity): CVSS 9.4 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.
Automatability100% × 15%
CISA's SSVC Automatable value: yes (Vulnrichment).
SSVC (CISA's decision table, applied by EchelonGraph): Track at low or medium mission impact; Attend at high (mission-essential systems).
Exploitation public PoC (CISA Vulnrichment) · Automatable yes (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 at low or medium mission impact and sooner than that at high.
EPSS PROB
0.5%
EPSS %ILE
40th
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 (9.4): severity, escalated by confirmed exploitation. This CVE's 9.4 is its impact severity (EG Severity), not escalated.

EG Severity
9.4 CRITICALCVSS-B, impact only: no KEV listing, EPSS or EG-KEV tier raises it.GitHub Security Advisory CVSS
EG Likelihood
0.5% within 30 daysSource: FIRST EPSS (model v2026.06.15, score date 2026-11-01). 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; Attend at high (mission-essential systems).CISA BOD 26-04: 14 days if the affected system is publicly exposed; 60 days 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; Attend at high (mission-essential systems).

A fix is available. Apply it within your standard update timelines at low or medium mission impact and sooner than that at high.

Exploitation public PoC (CISA Vulnrichment) · Automatable yes (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)14 days if the affected system is publicly exposed; 60 days if it is not.

The score's inputs: In CISA KEV no (CISA's KEV catalog) · Automatable yes (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

April 21, 2026

Last Modified

October 26, 2026

Advisory Details (1)

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

Improper Limitation of a Pathname to a Restricted Directory ('Path Traversal') in excel-mcp-server <=0.1.7 · Advisory · haris-musa/excel-mcp-server · GitHub

https://github.com/haris-musa/excel-mcp-server/security/advisories/GHSA-j98m-w3xp-9f56

Vendor Advisories for CVE-2026-40576(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
pipexcel-mcp-server @ 0.1.8 (fixes <= 0.1.7)—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)
PyPI(1)
PackageVulnerable rangeFix by version rangeDependents
excel-mcp-server0.1.1 ... 0.1.7 (7 versions)
  • every version up to 0.1.8: fixed in 0.1.8
—

Weakness Classification(1)

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

Data Freshness Timeline

(refreshed 16× in last 7d / 59× 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.

Showing the most recent 99 of 225 refreshes on record for this CVE.

A repeat, a row identical to one the same pipeline wrote less than 10 seconds earlier, is not a separate refresh and is not counted. 1 repeat row among the latest 100 is merged into the row it repeats. The 126 oldest rows on record are not shown and were not checked, so the counts can still include repeats.

  1. 2026-11-02 11:38 UTCEG score recompute
  2. 2026-11-02 11:38 UTCGHSA enrichmentGHSA-j98m-w3xp-9f56 · GitHub severity CRITICAL · GitHub CVSS 9.4
  3. 2026-11-01 16:34 UTCEPSS rescoreEPSS 0.5% · 40th percentile
  4. 2026-11-01 13:08 UTCGHSA enrichmentGHSA-j98m-w3xp-9f56 · GitHub severity CRITICAL · GitHub CVSS 9.4
  5. 2026-11-01 07:51 UTCGHSA enrichmentGHSA-j98m-w3xp-9f56 · GitHub severity CRITICAL · GitHub CVSS 9.4
  6. 2026-11-01 07:51 UTCEG score recompute
  7. 2026-10-31 14:36 UTCEG score recompute
  8. 2026-10-30 16:34 UTCEPSS rescoreEPSS 0.5% · 40th percentile
  9. 2026-10-29 17:33 UTCEG score recompute
  10. 2026-10-29 16:33 UTCEPSS rescoreEPSS 0.5% · 40th percentile
  11. 2026-10-28 19:02 UTCEG score recompute
  12. 2026-10-28 16:32 UTCEPSS rescoreEPSS 0.5% · 40th percentile
  13. 2026-10-27 19:57 UTCEG score recompute
  14. 2026-10-27 16:31 UTCEPSS rescoreEPSS 0.5% · 40th percentile
  15. 2026-10-26 21:27 UTCEG score recompute
  16. 2026-10-26 16:31 UTCEPSS rescoreEPSS 0.4% · 32nd percentile
  17. 2026-10-25 22:35 UTCEG score recompute
  18. 2026-10-25 16:32 UTCEPSS rescoreEPSS 0.4% · 32nd percentile
  19. 2026-10-25 14:30 UTCEG score recompute
  20. 2026-10-25 00:04 UTCEG score recompute
  21. 2026-10-24 16:32 UTCEPSS rescoreEPSS 0.6% · 50th percentile
  22. 2026-10-24 01:33 UTCEG score recompute
  23. 2026-10-23 16:31 UTCEPSS rescoreEPSS 0.6% · 50th percentile
  24. 2026-10-23 03:02 UTCEG score recompute
  25. 2026-10-22 16:34 UTCEPSS rescoreEPSS 0.6% · 50th percentile
Show 74 more
  1. 2026-10-22 04:30 UTCEG score recompute
  2. 2026-10-21 16:33 UTCEPSS rescoreEPSS 0.6% · 50th percentile
  3. 2026-10-21 05:59 UTCEG score recompute
  4. 2026-10-20 16:33 UTCEPSS rescoreEPSS 0.6% · 49th percentile
  5. 2026-10-20 07:27 UTCEG score recompute
  6. 2026-10-19 16:32 UTCEPSS rescoreEPSS 0.6% · 49th percentile
  7. 2026-10-19 08:55 UTCEG score recompute
  8. 2026-10-18 16:32 UTCEPSS rescoreEPSS 0.6% · 49th percentile
  9. 2026-10-18 03:42 UTCEG score recompute
  10. 2026-10-17 16:34 UTCEPSS rescoreEPSS 0.6% · 49th percentile
  11. 2026-10-17 11:51 UTCEG score recompute
  12. 2026-10-16 16:42 UTCEPSS rescoreEPSS 0.6% · 49th percentile
  13. 2026-10-16 13:19 UTCEG score recompute
  14. 2026-10-15 16:32 UTCEPSS rescoreEPSS 0.6% · 49th percentile
  15. 2026-10-15 14:46 UTCEG score recompute
  16. 2026-10-14 16:33 UTCEPSS rescoreEPSS 0.6% · 49th percentile
  17. 2026-10-14 09:19 UTCEG score recompute
  18. 2026-10-13 16:34 UTCEPSS rescoreEPSS 0.6% · 49th percentile
  19. 2026-10-13 06:37 UTCEG score recompute
  20. 2026-10-12 16:34 UTCEPSS rescoreEPSS 0.6% · 49th percentile
  21. 2026-10-12 16:09 UTCEG score recompute
  22. 2026-10-11 19:51 UTCEG score recompute
  23. 2026-10-11 17:05 UTCEG score recompute
  24. 2026-10-11 14:31 UTCEG score recompute
  25. 2026-10-11 13:48 UTCEPSS rescoreEPSS 0.6% · 49th percentile
  26. 2026-10-11 05:55 UTCOSV refresh
  27. 2026-10-10 20:00 UTCEPSS rescoreEPSS 0.6% · 49th percentile
  28. 2026-10-09 20:07 UTCEPSS rescoreEPSS 0.6% · 49th percentile
  29. 2026-10-08 17:12 UTCEPSS rescoreEPSS 0.6% · 49th percentile
  30. 2026-10-07 23:48 UTCEPSS rescoreEPSS 0.6% · 49th percentile
  31. 2026-10-06 15:17 UTCEPSS rescoreEPSS 0.6% · 49th percentile
  32. 2026-10-05 17:43 UTCEPSS rescoreEPSS 0.6% · 48th percentile
  33. 2026-10-04 23:22 UTCEPSS rescoreEPSS 0.6% · 48th percentile
  34. 2026-10-03 14:25 UTCEPSS rescoreEPSS 0.6% · 48th percentile
  35. 2026-10-01 19:50 UTCEPSS rescoreEPSS 0.6% · 48th percentile
  36. 2026-09-30 15:03 UTCEPSS rescoreEPSS 0.6% · 48th percentile
  37. 2026-09-27 13:48 UTCEPSS rescoreEPSS 0.6% · 48th percentile
  38. 2026-09-26 15:58 UTCEPSS rescoreEPSS 0.6% · 48th percentile
  39. 2026-09-23 17:53 UTCEPSS rescoreEPSS 0.4% · 33rd percentile
  40. 2026-09-21 17:49 UTCOSV refresh
  41. 2026-09-20 20:15 UTCEPSS rescoreEPSS 0.4% · 33rd percentile
  42. 2026-09-18 19:28 UTCEPSS rescoreEPSS 0.4% · 33rd percentile
  43. 2026-09-17 19:30 UTCEPSS rescoreEPSS 0.4% · 32nd percentile
  44. 2026-09-16 14:08 UTCEPSS rescoreEPSS 0.4% · 32nd percentile
  45. 2026-09-16 05:15 UTCEPSS rescoreEPSS 0.4% · 32nd percentile
  46. 2026-09-15 03:11 UTCEPSS rescoreEPSS 0.4% · 32nd percentile
  47. 2026-09-13 16:47 UTCEPSS rescoreEPSS 0.4% · 32nd percentile
  48. 2026-09-12 15:01 UTCEPSS rescoreEPSS 0.4% · 32nd percentile
  49. 2026-09-11 14:53 UTCEPSS rescoreEPSS 0.4% · 32nd percentile
  50. 2026-09-11 09:37 UTCEPSS rescoreEPSS 0.4% · 32nd percentile
  51. 2026-09-10 09:34 UTCEPSS rescoreEPSS 0.4% · 32nd percentile
  52. 2026-09-08 22:00 UTCEPSS rescoreEPSS 0.4% · 32nd percentile
  53. 2026-09-07 16:01 UTCEPSS rescoreEPSS 0.4% · 32nd percentile
  54. 2026-09-06 13:47 UTCEPSS rescoreEPSS 0.4% · 32nd percentile
  55. 2026-09-04 05:06 UTCEPSS rescoreEPSS 0.4% · 32nd percentile
  56. 2026-09-02 15:01 UTCOSV refresh
  57. 2026-09-02 14:12 UTCEPSS rescoreEPSS 0.4% · 32nd percentile
  58. 2026-09-01 13:53 UTCEPSS rescoreEPSS 0.4% · 32nd percentile
  59. 2026-09-01 04:39 UTCEPSS rescoreEPSS 0.4% · 32nd percentile
  60. 2026-08-30 19:17 UTCEPSS rescoreEPSS 0.4% · 32nd percentile
  61. 2026-08-30 01:22 UTCEPSS rescoreEPSS 0.4% · 32nd percentile
  62. 2026-08-28 21:41 UTCEPSS rescoreEPSS 0.4% · 31st percentile
  63. 2026-08-27 14:25 UTCEPSS rescoreEPSS 0.4% · 32nd percentile
  64. 2026-08-26 14:46 UTCEPSS rescoreEPSS 0.4% · 31st percentile
  65. 2026-08-25 13:49 UTCEPSS rescoreEPSS 0.4% · 31st percentile
  66. 2026-08-23 00:19 UTCEPSS rescoreEPSS 0.4% · 32nd percentile
  67. 2026-08-21 23:49 UTCEPSS rescoreEPSS 0.4% · 32nd percentile
  68. 2026-08-20 22:55 UTCEPSS rescoreEPSS 0.4% · 32nd percentile
  69. 2026-08-19 17:03 UTCEPSS rescoreEPSS 0.4% · 32nd percentile
  70. 2026-08-18 13:48 UTCEPSS rescoreEPSS 0.4% · 32nd percentile
  71. 2026-08-17 13:47 UTCEPSS rescoreEPSS 0.4% · 32nd percentile
  72. 2026-08-16 14:56 UTCEPSS rescoreEPSS 0.4% · 32nd percentile
  73. 2026-08-16 06:17 UTCEG score recompute
  74. 2026-08-16 02:14 UTCEPSS rescoreEPSS 0.4% · 32nd percentile

Frequently asked(5)

What is CVE-2026-40576?
CVE-2026-40576 is a critical-severity vulnerability; its CVE record was published on April 21, 2026. excel-mcp-server is a Model Context Protocol server for Excel file manipulation. A path traversal vulnerability exists in excel-mcp-server versions up to and including 0.1.7. When running in SSE or Streamable-HTTP transport mode (the documented way to use this server remotely), an unauthenticated…
When was the CVE record for CVE-2026-40576 published?
The CVE record for CVE-2026-40576 was published on April 21, 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 26, 2026; the record at its source may have been updated since.
Is CVE-2026-40576 actively exploited?
CVE-2026-40576 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.5% probability of exploitation in the next 30 days (40th percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2026-40576?
CVE-2026-40576 has a CVSS v3 base score of 9.4 (NVD).
How do I remediate CVE-2026-40576?
A fix for CVE-2026-40576 is available: update to the fixed version the vendor names in its advisory. The vendor advisories EchelonGraph has for CVE-2026-40576 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-40576

Explore →

Is Your Infrastructure Affected by CVE-2026-40576?

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