Docker
CVE-2026-42449
HIGH
GHSA-56c3-vfp2-5qqj
Vulnerability Assessment
| Weakness |
CWE
OWASP Top 10:2025
A01:2025 - Broken Access Control
ASVS 5.0
V4 - API and Web Service URL allowlisting, SSRF prevention
MITRE ATT&CK
2 techniques across 2 tactics: Initial Access, Credential Access The technique list with ATT&CK links and the kill-chain view is part of the Basic plan and up. |
Get an e-mail when this CVE is exploited, patched or re-scored. Free account.
Alert meAnalysisAIv1 – Apr 30, 2026
Server-Side Request Forgery (SSRF) in n8n-mcp SDK allows authenticated remote attackers to access cloud metadata endpoints and internal network resources via IPv4-mapped IPv6 address bypass. Versions 2.47.4 through 2.47.13 fail to validate IPv6 addresses in the synchronous URL validator (SSRFProtection.validateUrlSync()), enabling attackers who control the n8nApiUrl parameter to bypass RFC1918, localhost, and cloud metadata protections using addresses like [::ffff:169.254.169.254]. The vulnerability is non-blind SSRF returning response bodies to the attacker, and forwards the n8nApiKey in the x-n8n-api-key header to attacker-controlled targets. Confirmed actively exploited (CISA KEV). Vendor-released patch: version 2.47.14. EPSS exploitation probability not provided but risk is elevated given KEV status and availability of exploit code in the GitHub advisory.
Affected Packages
Source: OSV (Open Source Vulnerabilities)
Affects your stack
Affects 1 package in npm
Checking this CVE against your own stacks and servers is part of the Basic plan and up.
Know when Docker gets its next vulnerability
- Watch products and get an email when something new is published
- Check this CVE against your own stack and servers
- Exploit and PoC references, threat intelligence from 22 sources
No credit card · 7-day full trial
Severity by source
AV:N/AC:L/PR:L/UI:N/S:C/C:H/I:L/A:N
Primary rating from Vendor (https://github.com/czlonkowski/n8n-mcp) · only source for this CVE.
CVSS VectorVendor: https://github.com/czlonkowski/n8n-mcp
Lifecycle Timeline
2DescriptionCVE.org
Impact
In 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 (AWS IMDS, GCP, Azure, Alibaba, Oracle), 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.
The first-party HTTP server deployment was not primarily affected - it has a second async validator (validateWebhookUrl) that catches IPv6 addresses.
Impact category: CWE-918 (Server-Side Request Forgery).
Affected
Deployments embedding n8n-mcp as an SDK using N8NDocumentationMCPServer or N8NMCPEngine with user-supplied InstanceContext on versions v2.47.4 through v2.47.13.
Patched
v2.47.14 and later.
- npm:
npx n8n-mcp@latest(or pin to>= 2.47.14) - Docker:
docker pull ghcr.io/czlonkowski/n8n-mcp:latest
Workarounds
If developers cannot upgrade immediately:
- Validate URLs before passing to the SDK - reject any
n8nApiUrlwhose hostname is an IP literal (bracketed IPv6 or dotted IPv4) before callingN8NDocumentationMCPServer/getN8nApiClient(). Accept only URLs with DNS-resolvable hostnames. - Restrict egress at the network layer - block outbound traffic from the n8n-mcp process to RFC1918 ranges (10.0.0.0/8, 172.16.0.0/12, 192.168.0.0/16), link-local
169.254.0.0/16, and cloud metadata endpoints. Defense-in-depth against this class of issue and recommended even after upgrading. - Do not accept user-controlled
n8nApiUrlvalues - if the project's integration derives the URL from internal configuration only, this vulnerability is not reachable.
Upgrading to v2.47.14 is still strongly recommended.
Credit
Reported by @manthanghasadiya.
Executive ViewAI
The n8n-mcp SDK versions 2.47.4-2.47.13 contain a server-side request forgery (SSRF) vulnerability that allows authenticated attackers to bypass security controls and access internal cloud metadata and network resources, potentially exposing API credentials and sensitive infrastructure details. This vulnerability is confirmed actively exploited in the wild, making immediate patching critical to prevent unauthorized access to internal systems and credential compromise.
Within 24 hours: Identify all instances of n8n-mcp SDK versions 2.47.4 through 2.47.13 in your environment using software inventory tools and dependency scanners. Within 7 days: Upgrade all affected instances to version 2.47.14 or later; prioritize production and cloud-connected deployments. Verify that n8nApiUrl parameters are controlled by trusted administrators only and audit recent access logs for suspicious internal resource requests. Within 30 days: Conduct a forensic review of logs for the past 90 days to detect potential exploitation; rotate any n8n API keys that may have been exposed; and implement network segmentation to restrict n8n instances from accessing cloud metadata endpoints and internal services.
Apply vendor patch. Until patching is complete, implement network-level controls: disable n8n instances' outbound access to 169.254.169.254 (AWS metadata), 169.254.169.253 (Azure metadata), and internal RFC1918 ranges via firewall rules; restrict n8nApiUrl parameter input to a whitelist of approved values; and enforce mutual TLS authentication to limit lateral movement if credentials are compromised.
Threat Intelligence Overview
NVD
CVE.org
EPSS
How this decision was reached
The engine reads each signal below and applies a fixed list of rules from top to bottom. The first rule that matches sets the recommended action – like a statement, every line is shown.
What every action level means
SSVC AssessmentENISA
Priority Score
Attack Technique
Server-Side Request Forgery exploits applications that fetch remote resources based on user-supplied URLs.
Affected Products (CPE)CVE.org
An issue was discovered in Appsmith before 1.52. Rated critical severity (CVSS 9.8), this vulnerability is remotely expl
runc through version 1.0-rc6 (used in Docker before 18.09.2) contains a container escape vulnerability that allows attac
Netmaker makes networks with WireGuard. Rated high severity (CVSS 7.5), this vulnerability is remotely exploitable, no a
Unauthenticated remote code execution in Marimo ≤0.20.4 allows attackers to execute arbitrary system commands via the `/
The News & Blog Designer Pack - WordPress Blog Plugin - (Blog Post Grid, Blog Post Slider, Blog Post Carousel, Blog Post
Path traversal in JFrog Artifactory (CWE-22) enables an authenticated low-privilege user to write data outside the inten
Docker 1.3.2 allows remote attackers to execute arbitrary code with root privileges via a crafted (1) image or (2) build
Remote code execution in Gogs through 0.14.2 allows authenticated users (and unauthenticated attackers on default-config
Unauthenticated remote command injection in SGWBOX N3 firmware 2.0.25 lets attackers execute arbitrary operating-system
Remote code execution in Flowise before 3.1.2 allows any authenticated user (or API caller with chatflow view/update per
Remote code execution in NocoBase Workflow Script Node (npm @nocobase/plugin-workflow-javascript) allows authenticated l
Docker Desktop Community Edition before 2.1.0.1 allows local users to gain privileges by placing a Trojan horse docker-c
Exploit-DB