CVE-2026-30618

CRITICALPre-NVD 9.89.8
EchelonGraph scoreMEDIUM confidence

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

Score 9.8 from GitHub Security Advisory (severity: CRITICAL) published 2026-07-16. CISA-ADP (Vulnrichment) CVSS v3.1 baseline 9.8; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: CISA-ADP (Vulnrichment) CVSS v3.1, EPSS, GitHub Security Advisory
Trending — 3 sources updated this week
9.8EG
EchelonGraph verdictPlan mitigationRemediate within your standard update timelines at low or medium mission impact and sooner than that at high (the SSVC decision on this page).
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 1.2%CVSS: 9.8Exploit: None knownExposed services: Not assessed

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

xszyou Fay 4.3.1 contains a remote code execution vulnerability in its MCP STDIO server management and command execution handling. A remote attacker can access the publicly exposed MCP management interface and configure an MCP STDIO server with attacker-controlled commands and parameters, resulting in execution of arbitrary commands on the server. Successful exploitation allows arbitrary command execution within the context of the Fay service.

CVSS v3
9.8
EG Score
9.8CRITICALmedium confidence
EG Risk
60
EG Risk 60/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)
Severity98% × 45%
The EG Score, 9.8 of 10.
Exploitation1.2% × 40%
FIRST EPSS: the 30-day exploitation probability when EchelonGraph scored this CVE.
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 none (CISA Vulnrichment) · Automatable yes (CISA Vulnrichment) · Technical impact total (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 at low or medium mission impact and sooner than that at high, and watch the vendor's advisory for the fix.
EPSS PROB
1.2%
EPSS %ILE
67th
KEV
Not listed

SSVC (CISA's decision table, applied by EchelonGraph)Track at low or medium mission impact; Attend 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 at low or medium mission impact and sooner than that at high, and watch the vendor's advisory for the fix.

Exploitation none (CISA Vulnrichment) · Automatable yes (CISA Vulnrichment) · Technical impact total (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)3 days if the affected system is publicly exposed; 60 days if it is not.

In CISA KEV no (CISA's KEV catalog) · Automatable yes (CISA Vulnrichment) · Technical impact total (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

July 15, 2026

Last Modified

July 16, 2026

Advisory Details (2)

Auto-updated Oct 10, 2026
No fix on record yet.
Web page

MCP STDIO Command Injection: Full Vulnerability Advisory

https://www.ox.security/blog/mcp-supply-chain-advisory-rce-vulnerabilities-across-the-ai-ecosystem/
Web page

GitHub - xszyou/Fay: fay是一个帮助数字人（2.5d、3d、移动、pc、网页）或大语言模型（openai兼容、deepseek）连通业务系统的agent框架。 · GitHub

https://github.com/xszyou/Fay

Vendor Advisories for CVE-2026-30618(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 16× in last 7d / 45× 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 96 of 360 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. 4 repeat rows among the latest 100 are merged into the row they repeat. The 264 oldest rows on record are not shown and were not checked, so the counts can still include repeats.

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

Related CVEs(same CWE)

Frequently asked(5)

What is CVE-2026-30618?
CVE-2026-30618 is a critical-severity vulnerability; its CVE record was published on July 15, 2026. xszyou Fay 4.3.1 contains a remote code execution vulnerability in its MCP STDIO server management and command execution handling. A remote attacker can access the publicly exposed MCP management interface and configure an MCP STDIO server with attacker-controlled commands and parameters, resulting…
When was the CVE record for CVE-2026-30618 published?
The CVE record for CVE-2026-30618 was published on July 15, 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 16, 2026; the record at its source may have been updated since.
Is CVE-2026-30618 actively exploited?
CVE-2026-30618 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 1.2% probability of exploitation in the next 30 days (67th percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2026-30618?
CVE-2026-30618 has a CVSS v3.1 base score of 9.8 (CISA-ADP / Vulnrichment enrichment; NVD's own analysis pending).
How do I remediate CVE-2026-30618?
No fix for CVE-2026-30618 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 vendor advisories EchelonGraph has for CVE-2026-30618 are linked in the Vendor Advisories panel on this page.

Dependency Blast Radius

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

Explore →

Is Your Infrastructure Affected by CVE-2026-30618?

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

Book a Demo →Browse All CVEs