CVE-2026-39974: n8n-mcp has authenticated SSRF via instance-URL header in multi-tenant HTTP mode
Affects n8n-mcpSource GCVE Database
Not known to be exploited · CVSS 8.5 High : upgrade to 2.47.4 soon.
Data as of 26 Oct 2026, 17:16 UTC
- EPSS
- 0.3% chance of exploitation in 30 days – higher than 24% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
- Patch
- Available – fixed in 2.47.4
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:H/I:L/A:NExploitation evidence
Disclosed: evidence found.
CVE published 9 Apr 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponised: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors
A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 26 Oct 2026.
What to do
Upgrade n8n-mcp to 2.47.4.
Affected software
| Product | Affected | Fixed in |
|---|---|---|
Homebrewn8n-mcppkg:brew/n8n-mcpOther threats | Affected
| Fixed in
|
Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.
AI-suggested
Upgrade n8n-mcp to version 2.47.4 or later, which includes a fix that validates and normalizes URLs to prevent SSRF. If immediate upgrade is not possible, implement egress network filtering to block outbound traffic to internal IP ranges (RFC1918, link-local, and other internal networks), disable multi-tenant headers by unsetting ENABLE_MULTI_TENANT and blocking x-n8n-url/x-n8n-key headers at the reverse proxy, and restrict AUTH_TOKEN distribution to trusted operators only.
Description
An authenticated Server-Side Request Forgery (SSRF) vulnerability exists in n8n-mcp versions up to 2.47.3. An attacker with a valid AUTH_TOKEN can cause the server to make HTTP requests to arbitrary URLs via multi-tenant HTTP headers, potentially accessing sensitive internal resources such as cloud metadata endpoints and internal network services. The issue affects multi-tenant HTTP deployments and is fixed in version 2.47.4.
References
- github.com/czlonkowski/n8n-mcp/security/advisories/GHSA-4ggg-h7ph-26qr (opens in a new tab)
- nvd.nist.gov/vuln/detail/CVE-2026-39974 (opens in a new tab)
- github.com/czlonkowski/n8n-mcp/commit/d9d847f230923d96e0857ccecf3a4dedcc9b0096 (opens in a new tab)
- github.com/czlonkowski/n8n-mcp (opens in a new tab)
- github.com/czlonkowski/n8n-mcp/releases/tag/v2.47.4 (opens in a new tab)