| Package | Affected versions | Patched versions |
|---|---|---|
| n8n-mcp | < 2.56.1 | 2.56.1 |
| n8n-mcp | < 2.56.1 | 2.56.1 |
In multi-tenant HTTP deployments — where a single n8n-mcp server serves several tenants — the locally stored workflow version history (the automatic backups taken before workflow updates) was not isolated per tenant. An authenticated tenant could read workflow version snapshots belonging to other tenants, and could delete or destroy other tenants' stored backups.
A stored snapshot includes full node definitions, so the exposed data can contain credential references and authorization headers configured on nodes. This is therefore a confidentiality issue in addition to an integrity/availability one.
ENABLE_MULTI_TENANT=true), where multiple tenants are served by a single shared instance and database.Not affected:
<= 2.56.0
2.56.1. The stored version history is now isolated per instance, so a tenant can only access its own backups. Upgrading runs a one-time migration that isolates existing history and clears previously stored, un-scoped backups (these are auto-created, short-retention backups).
If users cannot upgrade immediately:
DISABLED_TOOLS=n8n_workflow_versions in the server environment (for example, in your Docker .env). This removes the affected tool from the deployment for all tenants; automatic backups are unaffected, but the cross-tenant access path is closed.stdio and single-tenant HTTP deployments are not affected.
Reported by Francisco Rosales (@0xmagic0) and coordinated by Ax Sharma (@axsharma) of Manifold Security.
Running one of these products? Scan your site to see whether it exposes a vulnerable version.
Scan my site free