HighVulnerability
GHSA-j4r7-8ph4-43g3: faf-mcp has an arbitrary local file read/write via unconfined `path` argument in FAF tools
- Identifier
- GHSA-j4r7-8ph4-43g3
- Published
- Record updated
- Affected
- faf-mcp <= 2.1.2
- Fixed in
- 2.1.3
- released June 11, 2026, 69 days before disclosure
Summary
faf-mcp versions before 2.1.3 accept a caller-controlled `path` argument in the shared `getProjectPath()` chokepoint and the `faf_read` and `faf_write` tools, resolving it without confinement to a project directory. An MCP client, or a prompt-injected LLM issuing a tool call, can read files such as SSH keys, cloud credentials and `.env` files, and `faf_write` can write outside the project (CWE-200).
Mitigation
Fixed in 2.1.3, which confines every caller-supplied `path` before filesystem access. Upgrade with `npm install -g faf-mcp@2.1.3` or `npx faf-mcp`. If upgrading is not possible immediately, run the server only against trusted local projects and set `FAF_ALLOWED_ROOTS` (patched versions) to a single project directory.
Topics
Related items
- MediumCVE-2026-124248: GPTranslate WordPress plugin stored cross-site scripting via comment parameterSimilar attack · NVD/CVE Database
- MediumAmazon: China-Linked Hackers’ AI Agents Exploited Medical Software Zero-DaySimilar attack · SecurityWeek
- MediumAttackers' AI Agents Found a Zero-Day in Medical-Imaging Software and Gained Root AccessSimilar attack · The Hacker News
- MediumCVE-2026-54026: LibreChat message injection via conversationId in request bodySimilar attack · NVD/CVE Database
- MediumCVE-2026-54046: LibreChat unauthenticated account enumeration via /api/user/verifySimilar attack · NVD/CVE Database