grok-faf-mcp has an arbitrary local file read via unconfined path argument in FAF tools

Exploitation

No confirmed exploitation recorded. Patch Next marks exploitation only from CISA KEV.

CVSS

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

EPSS

No dated EPSS signal available.

As published by the source; long descriptions are shortened.

Summary 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. Affected tools refreshfaf, fafscore, fafgetorchestrationpolicy, refreshblend (and the shared getProjectPath() chokepoint feeding the .faf tools), plus the general-purpose fafread / fafwrite file tools (denylist-only; an absolute path still reached home-directory secrets, and fafwrite could write outside the project). refreshfaf echoes the file contents verbatim back to the caller as "fresh DNA"; fafgetorchestrationpolicy reflects values parsed out of the attacker-chosen file and echoes the resolved absolute path — confirming the read. Impact An MCP client — or an LLM…

Published by the source

19 Aug 2026, 19:15 UTC

Last modified by the source

19 Aug 2026, 19:15 UTC

Source last checked

26 Oct 2026, 13:01 UTC

1. Revision 1 · created · 26 Oct 2026

   Published from ghsa record GHSA-cc2g-gq8c-r332

Preview the exact text before you copy it. Commands are read-only suggestions; review them before running anything.

# Patch Next advisory brief: GHSA-cc2g-gq8c-r332

Advisory: grok-faf-mcp has an arbitrary local file read via unconfined `path` argument in FAF tools
IDs: GHSA-cc2g-gq8c-r332
Record: https://patchnext.com/advisories/ghsa-cc2g-gq8c-r332 (revision 1, source checked 26 Oct 2026, 13:01 UTC)
Inventory: none attached. This brief comes from a public page and does not say whether any deployment is affected.
Severity: High (CVSS 7.5)
Exploitation: no confirmed exploitation recorded. Patch Next confirms exploitation only from CISA KEV.
Vendor response: Vendor fix available; fixed versions by package: grok-faf-mcp 1.5.3. A vendor fix does not mean a deployment is fixed.

## Affected components
- npm grok-faf-mcp: affected <= 1.5.2; fixed in 1.5.3

## Suggested inspection (read-only)
- `npm ls grok-faf-mcp --all`: lists every installed copy and version, including transitive ones. Run in the project root after `npm ci`.

## Supported action
Upgrade each affected component to a fixed version on its release line. For a transitive dependency, upgrade the parent package or add an override or constraint, then regenerate the lockfile. Redeploy every environment that ran an affected version.

## Required regression checks
- Run the test suite and a production build.
- Exercise the features that depend on grok-faf-mcp.
- Repeat the inspection and confirm that only fixed versions remain installed.

## Rollback considerations
- Keep the previous lockfile and deployment artifact. Rolling back reinstates the vulnerable version, so apply any documented mitigation while you fix forward.

## Unresolved questions
- Which deployments run an affected version?
- Exploitation status can change. Check again before lowering the priority.
- Mark the work resolved only after the fixed version is verified in production.

## Sources
- Verified: https://github.com/advisories/GHSA-cc2g-gq8c-r332 (GitHub-reviewed advisory GHSA-cc2g-gq8c-r332 lists affected ranges: npm grok-faf-mcp >=0 <=1.5.2)

Commands are suggestions: review each one before running it.