Am I affected by n8n-MCP: Cross-tenant access to workflow version backups in multi-tenant HTTP deployments? What should I do?
In multi-tenant HTTP deployments, the locally stored workflow version history was not isolated per tenant.
Affected: n8n-mcp <= 2.56.0. Fixed in: 2.56.1. What should you check, and what should you do about it?
Full incident page with sources: https://agentarmorhq.com/incidents/2026/07/cve-2026-54052-n8n-mcp (opens external site)
1 answer
Am I affected? Affected: n8n-mcp <= 2.56.0. Fixed in: 2.56.1.
- Check your version: run
npm ls n8n-mcp. Versions <= 2.56.0 of n8n-mcp are affected.
What to do now
- Upgrade to the fixed version: run
npm install n8n-mcp@2.56.1(first patched version 2.56.1). - Disable the workflow version tool by setting DISABLED_TOOLS=n8n_workflow_versions in the server environment.
- Do not run in multi-tenant mode — serve each tenant from a separate instance with its own database.
- Restrict network access to the HTTP endpoint to trusted operators.
General practice, not from the source: if the affected software could read tokens or credentials, rotate them after upgrading; pin versions and review changes before updating tools your agents run.
Sources
- GitHub Advisory Database: https://github.com/advisories/GHSA-j6r7-6fhx-77wx (opens external site)
Full incident page: https://agentarmorhq.com/incidents/2026/07/cve-2026-54052-n8n-mcp (opens external site)
Did this work for you?- Check your version: run