N8N · GHSA-pcr3-v5vr-qppf · AI agents & MCP
FIX → >= 2.42.2 +1
n8n runs the error workflow named in a failed workflow's settings and passes it the failed run's execution context, including the identity of the user who started it. A project editor can point a colleague's workflow at an error workflow they own and read that user's per-user credential secrets.
first public Oct 14, 2026 · 1 source
Could this affect your app?
Free first check from your website. Connect your repo for the full answer.
Only self-hosted or managed n8n instances that use team projects with editor roles and per-user credentials, including the dynamic credentials feature, are exposed. An attacker needs an editor account in a project, and the workflow setting settings.errorWorkflow must be used to chain runs. Instances with only fully trusted users, or without team projects and per-user credentials, carry much less risk.
Not affected if dynamic-credentials-disabled, no-team-projects, single-user-instance
Who cares n8n, per-user-credentials, self-hosted, team-projects, workflow-automation
n8n --version or the npm package version in your install.settings.errorWorkflow field and look for unexpected values.When a workflow fails, n8n runs the workflow named in its error-workflow setting and hands it the failed run's execution context, including the carrier that binds the run to the user who started it. A project editor could point a colleague's workflow at an error workflow they own, inherit the colleague's identity in their own execution, and resolve that user's per-user credential secrets. The error workflow now receives only non-identity fields.
The issue has been fixed in n8n versions 2.42.2 and 2.41.5. Users should upgrade to one of these versions or later to remediate the vulnerability.
If upgrading is not immediately possible, administrators should consider the following temporary mitigations:
settings.errorWorkflow field for unexpected values.These workarounds do not fully remediate the risk and should only be used as short-term mitigation measures.
Check it with your coding agent
It reads this page and tells you if your code is affected.
Are you affected?
Ask from here. InfraStack checks the affected versions against your stack and answers in your inbox.
InfraStack checks the affected versions against your stack and answers in Slack, with the evidence and the fix.
Upgrade to >= 2.42.2 +1
2.42.2 (fixed line 2.42.x)2.41.5 (fixed line 2.41.x)