CVE-2026-42449: fallo de gravedad alta en czlonkowski n8n-mcp
n8n-MCP: IPv4-mapped IPv6 addresses bypass SSRF protection in validateUrlSync(), enabling full SSRF for SDK embedders
Publicada el · Actualizada el
Aviso por correo cuando entre en el KEV, tenga PoC pública o suba de nota.
21Vexday Risk Score
Sin señal de explotación. Ningún artefacto público de explotación conocido hasta ahora.
ssvc Trackcvss 8.5epss 0.2%
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.
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:H/I:L/A:N
Productos afectados
czlonkowski · n8n-mcpCVEs relacionadas — czlonkowski n8n-mcp
En el mismo producto, de las más peligrosas a las menos.
CVE-2026-54052CRITICALn8n-MCP: Cross-tenant access to workflow version backups in multi-tenant HTTP deploymentsEPSS 0.4%CVE-2026-39974HIGHn8n-MCP has an Authenticated SSRF via instance-URL header in multi-tenant HTTP modeEPSS 0.3%CVE-2026-55608MEDIUMn8n-MCP: Incorrect authorization can expose default-scope workflow version backups in multi-tenant HTTP modeEPSS 0.3%CVE-2026-45582MEDIUMn8n-MCP: Workflow telemetry sanitizer could retain partial values from URL-shaped node parametersEPSS 0.3%CVE-2026-41495MEDIUMn8n-MCP Logs Sensitive Request Data on Unauthorized /mcp RequestsEPSS 0.3%CVE-2026-42282MEDIUMn8n-MCP: Sensitive MCP tool-call arguments logged on authenticated requests in HTTP modeEPSS 0.3%