Skip to content
HighVulnerability

GHSA-cc2g-gq8c-r332: grok-faf-mcp has an arbitrary local file read via unconfined `path` argument in FAF tools

Published
Record updated
View JSON
Affected
  • grok-faf-mcp <= 1.5.2
Fixed in
1.5.3
  • released June 11, 2026, 69 days before disclosure

Summary

grok-faf-mcp, an MCP server, has several FAF tools (refresh_faf, faf_score, faf_get_orchestration_policy, refresh_blend, faf_read, faf_write) that accept a caller-controlled path argument and read it without confinement to a trusted project directory. An MCP client, or an LLM prompt-injected through attacker-controlled content, can use absolute paths or ../ traversal to read files such as SSH keys, cloud credentials and .env files, with OS file permissions as the only remaining limit.

Mitigation

Fixed in 1.5.3, which confines every caller-supplied path before filesystem access: reads are restricted to .faf and .fafm context files, general file operations are confined to the project root (override with FAF_ALLOWED_ROOTS), paths are canonicalized through symlinks, and absolute paths and ../ escapes are rejected. Upgrade with `npm install -g grok-faf-mcp@1.5.3` or `bunx grok-faf-mcp`. If upgrading is not possible immediately, run the server only against trusted local projects and set FAF_ALLOWED_ROOTS to a single project directory.