n8n-mcp
Affected
- introduced
0, fixed2.50.1(semver)
Fixed versions
2.50.1
Fix
- Fixed version
2.50.1npm install [email protected]
Advisory
Also known as: None
n8n-mcp affected by path traversal, redirect-following SSRF, and telemetry payload exposure
Impact
n8n-mcp versions before 2.50.1 contained three independently-reported issues affecting deployments that run the n8n API integration:
DISABLED_TOOLS).Severity
CVSS 8.3 (HIGH). Exploitation requires an authenticated MCP caller and an n8n API integration configured with an n8n API key.
Patched versions
Upgrade to n8n-mcp >= 2.50.1.
Workarounds
N8N_MCP_TELEMETRY_DISABLED=true in the environment before starting the server, or run npx n8n-mcp telemetry disable once.Credit
Reported by @cybercraftsolutionsllc.
High Basis: The source's own band: HIGH
0, fixed 2.50.1 (semver)2.50.1
2.50.1npm install [email protected]Fix commands are the export's own generic commands. Ojuju never runs them. Check them against your setup first.
Check your own computer: guard packages check
Source: GitHub Advisory Database (reviewed advisories) · CC BY 4.0