CVE-2026-10278

MEDIUMPre-NVD 6.36.3
EchelonGraph scoreMEDIUM confidence

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

Score 6.3 from GitHub Security Advisory (severity: LOW) published 2026-06-01. A secondary CVSS source baseline 6.3; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: EPSS, GitHub Security Advisory, a secondary CVSS source
Elevated
6.3EG
EchelonGraph verdictPlan mitigationRemediate 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.3Exploit: No code on recordExposed services: Not assessed

No fix is confirmed yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for the fix.

The CVE record's description, written by its CNA (VulDB), states the affected versions: "A vulnerability was determined in ishayoyo excel-mcp up to 1.0.2." No release containing a fix is confirmed on record.

A vulnerability was determined in ishayoyo excel-mcp up to 1.0.2. Impacted is an unknown function of the file src/index.ts of the component read_file/write_file. Executing a manipulation of the argument filePath/outputPath can lead to path traversal. It is possible to launch the attack remotely. The exploit has been publicly disclosed and may be utilized. The project was informed of the problem early through an issue report but has not responded yet.

CVSS v3
6.3
EG Score
6.3MEDIUMmedium confidence
EG Risk
44
EG Risk 44/100

EG Risk is EchelonGraph's 0–100 priority score: it fuses intrinsic severity with real-world exploitation and automatability so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner. Distinct from the 0–10 EG Score (severity).

How it’s computed (value × EchelonGraph’s weight)
Severity63% × 45%
The EG Score, 6.3 of 10.
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: No fix is confirmed yet. Restrict network exposure of the affected system or apply the vendor's mitigation within your standard update timelines, and watch the vendor's advisory for the fix.
EPSS PROB
0.3%
EPSS %ILE
19th
KEV
Not listed

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

No fix is confirmed yet. Restrict network exposure of the affected system or apply the vendor's mitigation within your standard update timelines, and watch the vendor's advisory for the fix.

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.

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

June 1, 2026

Last Modified

July 22, 2026

Advisory Details (2)

Auto-updated Jun 13, 2026
No fix on record yet.
Web page

Arbitrary File Read and Write Vulnerability in excel-mcp · Issue #6 · ishayoyo/excel-mcp · GitHub

https://github.com/ishayoyo/excel-mcp/issues/6
Web page

GitHub - ishayoyo/excel-mcp · GitHub

https://github.com/ishayoyo/excel-mcp/

Vendor Advisories for CVE-2026-10278(1)

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

Weakness Classification(1)

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

Data Freshness Timeline

(refreshed 11× in last 7d / 26× 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 100 of 210 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. None are among the latest 100 rows. The 110 oldest rows on record are not shown and were not checked, so the counts can still include repeats.

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

Related CVEs(same CWE)

Frequently asked(5)

What is CVE-2026-10278?
CVE-2026-10278 is a medium-severity vulnerability; its CVE record was published on June 1, 2026. A vulnerability was determined in ishayoyo excel-mcp up to 1.0.2. Impacted is an unknown function of the file src/index.ts of the component readfile/writefile. Executing a manipulation of the argument filePath/outputPath can lead to path traversal. It is possible to launch the attack remotely. The…
When was the CVE record for CVE-2026-10278 published?
The CVE record for CVE-2026-10278 was published on June 1, 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 July 22, 2026; the record at its source may have been updated since.
Is CVE-2026-10278 actively exploited?
CVE-2026-10278 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.3% probability of exploitation in the next 30 days (19th percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2026-10278?
CVE-2026-10278 has a CVSS base score of 6.3 (a secondary CVSS source that NVD displays; NVD's own analysis pending).
How do I remediate CVE-2026-10278?
No fix for CVE-2026-10278 is confirmed yet. Until one is published, restrict network exposure of the affected system or apply the vendor's mitigation — for example, keep it off the internet or limit it to trusted networks — and watch the vendor's advisory for the fix. The CVE record's description, written by its CNA (VulDB), states the affected versions: "A vulnerability was determined in ishayoyo excel-mcp up to 1.0.2." No release containing a fix is confirmed on record. The vendor advisories EchelonGraph has for CVE-2026-10278 are linked in the Vendor Advisories panel on this page.

Dependency Blast Radius

Explore the affected products and dependency analysis for CVE-2026-10278

Explore →

Is Your Infrastructure Affected by CVE-2026-10278?

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

Book a Demo →Browse All CVEs