Exploit discussion active in current signal (1 latest mentions)
Recommended action window: High priority (within 72h)
NVD description
n8n-MCP is an MCP server that provides AI assistants access to n8n node documentation, properties, and operations. In versions 2.47.4 through 2.47.13, the SDK embedder path (N8NDocumentationMCPServer constructor, getN8nApiClient(), and validateInstanceContext()), the synchronous URL validator in SSRFProtection.validateUrlSync() had no IPv6 checks. IPv4-mapped IPv6 addresses such as http://[::ffff:169.254.169.254] bypassed the cloud-metadata, localhost, and private-IP range checks. An attacker able to supply an n8nApiUrl value could cause the server to issue HTTP requests to cloud metadata endpoints, RFC1918 private networks, or localhost services. Response bodies are returned to the caller (non-blind SSRF), and the n8nApiKey is forwarded in the x-n8n-api-key header to the attacker-controlled target. Projects with deployments embedding n8n-mcp as an SDK using N8NDocumentationMCPServer or N8NMCPEngine with user-supplied InstanceContext are affected. The first-party HTTP server deployment was not primarily affected — it has a second async validator (validateWebhookUrl) that catches IPv6 addresses. This issue has been fixed in version 2.47.14. If users are unable to upgrade immediately as a workaround they can validate URLs before passing to the SDK, restrict egress at the network layer, and reject user-controlled n8nApiUrl values.
Priority
LOW
Exploitation
NONE
PoC
YES
Patch
AVAILABLE
Momentum
STABLE
If you run products in this scope, you should treat this CVE as relevant to your environment.
| Date | Total | Labels |
|---|
| 2026-05-08 | 2 | Disclosure1PoC1 |
| 2026-05-10 | 2 | General2 |
| 2026-07-16 | 1 | General1 |
My findings: CVE-2026-6942 (radare2-mcp, CVSS 9.8), CVE-2026-42449 (n8n-mcp, CVSS 8.5), CVE-2026-35394 (mobile-mcp, CVSS 8.3). Plus issues in GitHub MCP, Kubernetes MCP, IDA Pro MCP, Chromium DevTools MCP, and AWS Diagram MCP.
Post summary
The post lists several high‑CVSS CVEs across various MCP platforms but provides no further technical or exploitation details, patches, or evidence of active exploitation.
I bypassed an SSRF fix with 7 characters. CVE-2026-42449 (CVSS 8.5) in n8n-mcp. ❌ http://169.254.169.254 ✅ http://[::ffff:169.254.169.254] IPv6-mapped addresses. Zero validation. Full cloud metadata access. 🧵 https://t.co/eLC38gDgBv
Post summary
The author demonstrates a concise proof of concept that bypasses the SSRF mitigation for CVE-2026-42449 using IPv6-mapped addresses, exposing full cloud metadata.
CVE-2026-42449 n8n-MCP is an MCP server that provides AI assistants access to n8n node documentation, properties, and operations. In versions 2.47.4 through 2.47.13, the SDK embedde… https://www.cve.org/CVERecord?id=CVE-2026-42449
Post summary
The brief snippet references CVE-2026‑42449 with affected versions but lacks concrete details on exploitation or mitigation.
🚨*CVE* CVE-2026-42449 n8n-MCP is an MCP server that provides AI assistants access to n8n node documentation, properties, and operations. In versions 2.47.4 through 2.47.13, the SDK embedde… https://www.cve.org/CVERecord?id=CVE-2026-42449 ----- Traducción: CVE-2026-42449 n8n… http://infoflow.cloud`
Post summary
The message announces CVE-2026-42449 and references its CVE record, but provides no additional technical details, exploit code, or mitigation information.
CVE-2026-42449 Server-Side Request Forgery via IPv6 Address Bypass in n8n-MCP 2.47.4-2.47.13 https://vulmon.com/vulnerabilitydetails?qid=CVE-2026-42449
Post summary
A Server‑Side Request Forgery vulnerability was disclosed in n8n‑MCP versions 2.47.4‑2.47.13 due to an IPv6 address bypass.
1 of 1 entries
| Part | Vendor | Product | Version | Target SW | Target HW |
|---|---|---|---|---|---|
| App | n8n-mcp | n8n-mcp | - | - | - |