CVE-2026-45707
Multi-tenant n8n-mcp can target operator’s instance if headers are missing.
Is CVE-2026-45707 being exploited?
Not confirmed. CVE-2026-45707 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.24% probability of exploitation in the next 30 days.
How severe is CVE-2026-45707?
CVE-2026-45707 is rated High with a CVSS score of 8.1. 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-45707?
Yes. A fix has been recorded for CVE-2026-45707. The vendor advisory is the authority on the exact fixed version — apply it from there rather than from a summary.
What does CVE-2026-45707 affect?
CVE-2026-45707 affects n8n-mcp (multi-tenant, HTTP-mode), n8n management API. Confirm the exact affected versions against the vendor advisory before deciding you are exposed.
What should I do about CVE-2026-45707?
Upgrade to 2.51.2 or later.
Exploitation status reflects CISA's KEV catalog as we last synced it. Check the catalog directly.
Authenticated MCP tenant can cause management calls to run against the operator's n8n instance instead of its own via header fallback; potential data exposure or modification.
Patch when possible
- affected< 2.51.2
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.