Description
Several grok-faf-mcp MCP tools accept a caller-controlled path argument and resolve it (~ expansion + path.resolve()) straight into a filesystem read without confining it to a trusted project directory. An absolute path or ../ traversal is resolved and used as-is, so the server process can be made to read files outside the intended .faf project context.
Recommendation
Update the grok-faf-mcp package to the latest compatible version. Followings are version details:
- Affected version(s): <= 1.5.2
- Patched version(s): 1.5.3
References
Could your website be exposed too?
SmartScanner can check your website for grok-faf-mcp has an arbitrary local file read via unconfined `path` argument in FAF tools and gives you actionable findings to investigate.
Start a free scanRelated Issues
- @rhinostone/swig: arbitrary local file read via include/extends path traversal - @rhinostone/swig-twig - Vulnerability
- obsidian-local-rest-api: Authenticated path traversal via URL-encoded %2F in /vault/{path} — arbitrary host file read/wr - Vulnerability
- @rhinostone/swig: arbitrary local file read via include/extends path traversal - Vulnerability
- @rhinostone/swig: arbitrary local file read via include/extends path traversal - @rhinostone/swig - Vulnerability
You might also like:
See something that needs correcting? Let us knowUpdated August 19, 2026