Technical impact
A path traversal flaw in the validatePath function of godot‑mcp version 2.0.0 permits a local attacker to provide a crafted projectPath argument that resolves to files outside the intended working directory. The code fails to sanitize the supplied path, allowing direct access to arbitrary files on the host system. This is a classic directory traversal weakness (CWE‑22). If the process runs with elevated permissions, a malicious attacker could read or modify sensitive files, potentially leading to privilege escalation or system compromise. Local non‑privileged users can still read or tamper with files that are not protected by OS permissions.
Affected Systems
Affected product: godot‑mcp, version 2.0.0, developed by tugcantopaloglu. The flaw resides in the run_project component’s build/index.js validatePath method. The fix was introduced in version 3.0.0, released with commit eb63add552aa4bd9205395cf91b40654654a3cf2.
Risk and Exploitability
With a CVSS score of 4.8 the vulnerability carries a moderate severity rating, while the EPSS score is below 1 %, indicating a low probability of exploitation in the wild. The vulnerability is not listed in the CISA KEV catalog, but the publicly released exploit and local‑access requirement mean that any user able to run godot‑mcp on the host can abuse the flaw. The risk escalates if the tool is executed with higher privileges, transforming a local read/write flaw into a potential privilege‑escalation vector. Prompt remediation is therefore advised.
