CVE-2026-42449
SSRF in n8n-MCP SDK allows internal requests via user URL.
Is CVE-2026-42449 being exploited?
Not confirmed. CVE-2026-42449 does not appear in CISA's Known Exploited Vulnerabilities catalog, which records only exploitation that has been observed and reported publicly. That is evidence of absence of a report, not evidence the flaw is unattacked. EPSS currently estimates a 0.21% probability of exploitation in the next 30 days.
How severe is CVE-2026-42449?
CVE-2026-42449 is rated High with a CVSS score of 8.5. Severity describes how bad exploitation would be, not how likely it is: pair it with exploitation evidence before deciding what to patch first.
Is there a patch for CVE-2026-42449?
Yes. A fix has been recorded for CVE-2026-42449. The vendor advisory is the authority on the exact fixed version — apply it from there rather than from a summary.
What does CVE-2026-42449 affect?
CVE-2026-42449 affects n8n-MCP SDK (N8NDocumentationMCPServer, N8NMCPEngine) v2.47.4-2.47.13. Confirm the exact affected versions against the vendor advisory before deciding you are exposed.
What should I do about CVE-2026-42449?
Upgrade to 2.47.14+
Exploitation status reflects CISA's KEV catalog as we last synced it. Check the catalog directly.
SSRF lets attacker cause server to fetch internal/private endpoints (metadata, RFC1918, localhost) and may leak data/API key.
Patch when possible
- affected>= 2.47.4 and < 2.47.14
As published in the CVE Program record. A version outside these ranges is not a statement that it is unaffected — vendors sometimes understate a range, and distribution-backported builds carry upstream numbers that do not reflect what was patched into them.