n8n-mcp versions before 2.50.1 have three security issues: path traversal via unvalidated workflow IDs allowing unauthorized API access, redirect-following SSRF through validated trigger URLs, and exposure of sensitive data in telemetry payloads. These issues require an authenticated MCP caller and an n8n API key. The vulnerabilities have been fixed in version 2.50.1.