N8N-MCP
12 CVEs tracked. None of them is in CISA KEV.
This hub aggregates every CVE we track for N8N-MCP, a product in the operating systems space. Use it to gauge the current risk picture and drill into individual advisories.
N8N-MCP CVEs per month
| Month | CVEs |
|---|---|
| 2024-10 | 0 |
| 2024-11 | 0 |
| 2024-12 | 0 |
| 2025-01 | 0 |
| 2025-02 | 0 |
| 2025-03 | 0 |
| 2025-04 | 0 |
| 2025-05 | 0 |
| 2025-06 | 0 |
| 2025-07 | 0 |
| 2025-08 | 0 |
| 2025-09 | 0 |
| 2025-10 | 0 |
| 2025-11 | 0 |
| 2025-12 | 0 |
| 2026-01 | 0 |
| 2026-02 | 0 |
| 2026-03 | 0 |
| 2026-04 | 3 |
| 2026-05 | 7 |
| 2026-06 | 0 |
| 2026-07 | 2 |
| 2026-08 | 0 |
| 2026-09 | 0 |
Severity
How the 12 CVEs score on CVSS. Severity is not exploitation: KEV is counted above.
- Critical2
- High3
- Medium4
Latest CVEs
The 12 most recently published vulnerabilities affecting N8N-MCP.
- CVE-2026-55608n8n-MCP: Incorrect authorization can expose default-scope workflow version backups in multi-tenant HTTP mode4.2
- CVE-2026-54052n8n-MCP: Cross-tenant access to workflow version backups in multi-tenant HTTP deployments9.9
- CVE-2026-45582n8n-MCP: Workflow telemetry sanitizer could retain partial values from URL-shaped node parameters6.5
- CVE-2026-45707n8n-MCP: Multi-tenant MCP requests fall back to process-level n8n credentials when tenant headers are absent or incomplete8.1
- CVE-2026-44694n8n-MCP: Authenticated SSRF in n8n-mcp webhook and API client paths9.1
- CVE-2026-42282n8n-MCP: Sensitive MCP tool-call arguments logged on authenticated requests in HTTP mode4.3
- CVE-2026-41495n8n-MCP Logs Sensitive Request Data on Unauthorized /mcp Requests5.3
- GHSA-8g7g-hmwm-6rv2n8n-mcp affected by path traversal, redirect-following SSRF, and telemetry payload exposure—
- CVE-2026-42449n8n-MCP: IPv4-mapped IPv6 addresses bypass SSRF protection in validateUrlSync(), enabling full SSRF for SDK embedders8.5
- GHSA-75hx-xj24-mqrwn8n-mcp has unauthenticated session termination and information disclosure in HTTP transport—
- CVE-2026-39974n8n-MCP has an Authenticated SSRF via instance-URL header in multi-tenant HTTP mode8.5
- GHSA-4ggg-h7ph-26qrn8n-mcp has authenticated SSRF via instance-URL header in multi-tenant HTTP mode—
Product grouping is registry-driven, with AI assist and human review. How it works