CVE-2026-15522 in godot-mcp
Summary
by MITRE • 07/13/2026
A security flaw has been discovered in tugcantopaloglu godot-mcp 2.0.0. Affected by this vulnerability is the function validatePath of the file build/index.js of the component run_project. The manipulation of the argument projectPath results in path traversal. Attacking locally is a requirement. The exploit has been released to the public and may be used for attacks. Upgrading to version 3.0.0 addresses this issue. The patch is identified as eb63add552aa4bd9205395cf91b40654654a3cf2. It is suggested to upgrade the affected component.
If you want to get best quality of vulnerability data, you may have to visit VulDB.
Analysis
by VulDB Data Team • 07/13/2026
The vulnerability identified in tugcantopaloglu godot-mcp version 2.0.0 represents a critical path traversal flaw within the run_project component's validatePath function located in build/index.js. This security weakness stems from inadequate input validation of the projectPath argument, allowing malicious actors to manipulate file system access through carefully crafted path sequences. The vulnerability specifically manifests when the application processes user-supplied path data without proper sanitization or validation mechanisms, creating an opportunity for unauthorized file system interactions.
The technical implementation of this flaw enables attackers to traverse directory structures beyond intended boundaries by exploiting how the validatePath function handles path manipulation. This type of vulnerability falls under CWE-23 known as "Relative Path Traversal" and aligns with ATT&CK technique T1059.007 for command and scripting interpreter usage. The attack vector requires local execution privileges, meaning an attacker must already have access to the system to exploit this weakness, but once achieved, it can potentially allow reading or writing to arbitrary files within the application's scope.
The operational impact of this vulnerability extends beyond simple file access violations as it could enable attackers to access sensitive project configurations, source code files, or even overwrite critical application components. Since the exploit has been publicly released and is actively being used for attacks, organizations running affected versions face immediate risk of data compromise or system integrity breaches. The local requirement for exploitation does not mitigate the severity, as compromised local accounts or privilege escalation opportunities can quickly turn this into a more significant threat vector.
The remediation strategy involves upgrading to version 3.0.0 which contains a patched implementation of the validatePath function at commit eb63add552aa4bd9205395cf91b40654654a3cf2. This upgrade addresses the core validation issue by implementing proper input sanitization and path resolution mechanisms that prevent traversal attacks. Organizations should prioritize this update immediately, particularly in environments where local access control is not strictly enforced. Additionally, implementing regular security audits of third-party dependencies and maintaining up-to-date vulnerability assessments will help prevent similar issues from arising in other components of the application stack.