npm/n8n-mcp

n8n-MCP: Incorrect authorization can expose default-scope workflow version backups in multi-tenant HTTP mode

Modified: 7/14/2026

n8n-mcp has authenticated SSRF via instance-URL header in multi-tenant HTTP mode

Modified: 4/9/2026

n8n-mcp's IPv4-mapped IPv6 addresses bypass SSRF protection in validateUrlSync(), enabling full SSRF for SDK embedders

Modified: 5/11/2026

n8n-mcp has unauthenticated session termination and information disclosure in HTTP transport

Modified: 4/10/2026

n8n-mcp affected by path traversal, redirect-following SSRF, and telemetry payload exposure

Modified: 5/8/2026

n8n-mcp webhook and API client paths has an authenticated SSRF

Modified: 5/13/2026

n8n-MCP: Workflow telemetry sanitizer could retain partial values from URL-shaped node parameters

Modified: 6/9/2026

n8n-MCP: Cross-tenant access to workflow version backups in multi-tenant HTTP deployments

Modified: 7/14/2026

n8n-MCP: Multi-tenant MCP requests fall back to process-level n8n credentials when tenant headers are absent or incomplete

Modified: 6/9/2026

n8n-MCP Logs Sensitive Request Data on Unauthorized /mcp Requests

Modified: 5/13/2026

n8n-MCP: Sensitive MCP tool-call arguments logged on authenticated requests in HTTP mode

Modified: 5/13/2026