Skip to content
Applications

CVE-2026-54052

9.9
Critical
EPSS 0.39%Patch availableJul 16, 2026

Authenticated tenant can read and delete other tenants' n8n workflow backups.

common questions

Is CVE-2026-54052 being exploited?

Not confirmed. CVE-2026-54052 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.39% probability of exploitation in the next 30 days.

How severe is CVE-2026-54052?

CVE-2026-54052 is rated Critical with a CVSS score of 9.9. 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-54052?

Yes. A fix has been recorded for CVE-2026-54052. The vendor advisory is the authority on the exact fixed version — apply it from there rather than from a summary.

What does CVE-2026-54052 affect?

CVE-2026-54052 affects n8n-MCP < 2.56.1 (HTTP mode, ENABLE_MULTI_TENANT=true), Self-hosted n8n instances using n8n-mcp multi-tenancy. Confirm the exact affected versions against the vendor advisory before deciding you are exposed.

What should I do about CVE-2026-54052?

Upgrade n8n-mcp to 2.56.1+ or disable HTTP multi-tenant mode until patched.

Exploitation status reflects CISA's KEV catalog as we last synced it. Check the catalog directly.

executive summary
technical analysis
affected
n8n-MCP < 2.56.1 (HTTP mode, ENABLE_MULTI_TENANT=true)Self-hosted n8n instances using n8n-mcp multi-tenancy
impact

Authenticated tenant can read workflow snapshots (node defs, credential refs, auth headers) and delete/destroy other tenants' backups.

action required

Immediate action required

affected versions
czlonkowski n8n-mcp
  • affected< 2.56.1

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.

how to fix
Remediation steps are tailored for users whose stack is affected. Add this technology to your stack to see the fix checklist.
references
get alerted

Track only the vulnerabilities that affect your infrastructure.

start for free