npm package report

Is grok-faf-mcp safe?

1 known vulnerability, worst severity HIGH.

cvss
7.5

how bad it is if exploited, out of 10

epss
not scored

chance of exploitation in the next 30 days

xyz score
3.3

CyberXYZ composite, out of 10

fig. 01 — GHSA-cc2g-gq8c-r332, the advisory selected below

// advisories

GHSA-cc2g-gq8c-r332

HIGH

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 permissi

Affected
>=0, <1.5.3, <= 1.5.2
Fixed in
1.5.3
Weakness
CWE-200
Published
2026-08-19
Source
osv

OSV

// dependencies

0 direct

Sign in for dependency paths and remediation

// ai model usage

Tracked for PyPI packages. HuggingFace models declare Python dependencies, so npm packages are not covered.

Checked 2026-09-22 at 00:53 UTC. The most recent advisory here was published 2026-08-19. Updated continuously from NVD, GHSA, OSV and CNA feeds.

Think a verdict here is wrong? Tell us — we respond within 2 business days.
Is grok-faf-mcp safe? npm package security report | CyberXYZ