Advisory Database
  • Advisories
  • Dependency Scanning
  1. npm
  2. ›
  3. grok-faf-mcp
  4. ›
  5. GHSA-cc2g-gq8c-r332

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

August 19, 2026

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. The only remaining limit is OS file permissions.

References

  • github.com/Wolfe-Jam/grok-faf-mcp/releases/tag/v1.5.3
  • github.com/Wolfe-Jam/grok-faf-mcp/security/advisories/GHSA-cc2g-gq8c-r332
  • github.com/advisories/GHSA-cc2g-gq8c-r332

Code Behaviors & Features

Detect and mitigate GHSA-cc2g-gq8c-r332 with GitLab Dependency Scanning

Secure your software supply chain by verifying that all open source dependencies used in your projects contain no disclosed vulnerabilities. Learn more about Dependency Scanning →

Affected versions

All versions before 1.5.3

Fixed versions

  • 1.5.3

Solution

Upgrade to version 1.5.3 or above.

Impact 7.5 HIGH

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N

Learn more about CVSS

Weakness

  • CWE-200: Exposure of Sensitive Information to an Unauthorized Actor
  • CWE-22: Improper Limitation of a Pathname to a Restricted Directory ('Path Traversal')
  • CWE-73: External Control of File Name or Path

Source file

npm/grok-faf-mcp/GHSA-cc2g-gq8c-r332.yml

Spotted a mistake? Edit the file on GitLab.

  • Site Repo
  • About GitLab
  • Terms
  • Privacy Statement
  • Contact

Page generated Tue, 22 Sep 2026 12:20:55 +0000.