GHSA-j4r7-8ph4-43g3: faf-mcp has an arbitrary local file read/write via unconfined `path` argument in FAF tools
Summary
faf-mcp (a tool that helps AI assistants work with files) had a security flaw where it accepted file paths from callers without properly restricting access to a safe directory. This meant an attacker could trick the system into reading sensitive files like SSH keys or cloud credentials, or writing files outside the intended project folder, by using absolute paths or directory-traversal tricks (like `../`). The vulnerability could be exploited through prompt injection (hiding malicious instructions in user-provided content that an AI processes).
Solution / Mitigation
Fixed in version 2.1.3 by adding path confinement: reads are restricted to `.faf` / `.fafm` context files only, general file operations are confined to the project root (with an optional `FAF_ALLOWED_ROOTS` environment variable to override), symlink bypasses are closed, and absolute paths and `../` escapes are rejected. Upgrade with `npm install -g faf-mcp@2.1.3` or use `npx faf-mcp`. If you cannot upgrade immediately, run the server only on trusted local projects and set `FAF_ALLOWED_ROOTS` to a single project directory for a hard boundary.
Classification
Affected Vendors
Affected Packages
Related Issues
GHSA-382c-vx95-w3p5: Gittensory: Missing contributor-scoped access control on profile endpoint and MCP tool leaks miner financial data
CVE-2026-34371: LibreChat is a ChatGPT clone with additional features. Prior to 0.8.4, LibreChat trusts the name field returned by the e
Original source: https://github.com/advisories/GHSA-j4r7-8ph4-43g3
First tracked: August 19, 2026 at 08:01 PM
Classified by LLM (prompt v3) · confidence: 92%