CVE-2025-67364

HIGHNVD 7.57.5
EchelonGraph scoreMEDIUM confidence

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

Score 7.5 from GitHub Security Advisory (severity: HIGH) published 2026-01-07. NVD baseline CVSS 7.5; 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-1195 (ENISA EUVD) · GHSA-j893-m93w-jwjw (GitHub Security Advisories)Source: ENISA EUVD

7.5EG
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).
  • CISA's Vulnrichment rates exploitation as PoC; EchelonGraph holds no exploit-code reference for it
CISA-KEV: Not listedEPSS PROB: 0.6%CVSS: 7.5Exploit: 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.

fast-filesystem-mcp version 3.4.0 contains a critical path traversal vulnerability in its file operation tools including fast_read_file. This vulnerability arises from improper path validation that fails to resolve symbolic links to their actual physical paths. The safePath and isPathAllowed functions use path.resolve() which does not handle symlinks, allowing attackers to bypass directory access restrictions by creating symlinks within allowed directories that point to restricted system paths. When these symlinks are accessed through valid path references, the validation checks are circumvented, enabling access to unauthorized files.

CVSS v3
7.5
EG Score
7.5HIGHmedium confidence
EG Risk
65
EG Risk 65/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.
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: No fix is confirmed yet. Restrict network exposure of the affected system within your standard update timelines at low or medium mission impact and sooner than that at high, and watch for a fix.
EPSS PROB
0.6%
EPSS %ILE
50th
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.GitHub Security Advisory CVSS
EG Likelihood
0.6% within 30 daysSource: FIRST EPSS (model v2026.06.15, score date 2026-10-24). 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: 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).

No fix is confirmed yet. Restrict network exposure of the affected system within your standard update timelines at low or medium mission impact and sooner than that at high, and watch for a fix.

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.

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

January 7, 2026

Last Modified

June 17, 2026

Advisory Details (2)

Auto-updated Aug 6, 2026
No fix on record yet.
Web page

Security Vulnerability: Path Validation Bypass via Symlinks in File Operations · Issue #10 · efforthye/fast-filesystem-mcp · GitHub

https://github.com/efforthye/fast-filesystem-mcp/issues/10
Web page

GitHub - efforthye/fast-filesystem-mcp: A high-performance Model Context Protocol (MCP) server that provides secure filesystem access for Claude and other AI assistants. · GitHub

https://github.com/efforthye/fast-filesystem-mcp

Patch Availability(1)

Vendor / EcosystemFix (by version range) / PatchReleasedSource
npmfast-filesystem-mcp—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)
npm(1)
PackageVulnerable rangeFix by version rangeDependents
fast-filesystem-mcp—
  • every version through 3.4.0: no fix on record
—

Weakness Classification(1)

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

Data Freshness Timeline

(refreshed 10× in last 7d / 40× 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 97 of 205 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. 3 repeat rows among the latest 100 are merged into the row they repeat. The 108 oldest rows on record are not shown and were not checked, so the counts can still include repeats.

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

Frequently asked(5)

What is CVE-2025-67364?
CVE-2025-67364 is a high-severity vulnerability; its CVE record was published on January 7, 2026. fast-filesystem-mcp version 3.4.0 contains a critical path traversal vulnerability in its file operation tools including fastreadfile. This vulnerability arises from improper path validation that fails to resolve symbolic links to their actual physical paths. The safePath and isPathAllowed…
When was the CVE record for CVE-2025-67364 published?
The CVE record for CVE-2025-67364 was published on January 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 June 17, 2026; the record at its source may have been updated since.
Is CVE-2025-67364 actively exploited?
CVE-2025-67364 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.6% probability of exploitation in the next 30 days (50th percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2025-67364?
CVE-2025-67364 has a CVSS v3 base score of 7.5 (NVD).
How do I remediate CVE-2025-67364?
No fix for CVE-2025-67364 is confirmed yet. Until one is published, restrict network exposure of the affected system — for example, keep it off the internet or limit it to trusted networks — and watch for a fix.

Dependency Blast Radius

See which npm, PyPI, Go, and Maven packages are affected by CVE-2025-67364

Explore →

Is Your Infrastructure Affected by CVE-2025-67364?

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