N8N · GHSA-h59h-rf6m-7jp5 · AI agents & MCP
FIX → 3.2.2 · 2.48.3 · 1.123.96 +1
When a workflow is activated, n8n registers its trigger nodes using the credentials set on them without checking the publisher may use those credentials. A member who knows another user's credential ID can activate a workflow that uses it, so n8n creates or deletes webhooks on the connected service with that credential's privileges and receives events from resources the member chooses.
first public Nov 13, 2026 · 1 source
Check it with your coding agent
It reads this page and tells you if your code or app is affected.
Self-hosted or cloud n8n instances where more than one user can create or activate workflows and where trigger nodes use credentials owned by other users. A member with access to the instance can exploit it by knowing another user's credential ID. Single-user instances, or instances where only fully trusted users can access n8n, face much lower risk.
Not affected if single-user, trusted-users-only
Who cares github, gitlab, n8n, self-hosted, webhooks
When a workflow was activated, n8n registered its trigger nodes with the connected services using the credentials set on those nodes. Activation did not check that the user publishing the workflow had access to those credentials. A member who knew the ID of another user's credential could activate a workflow whose trigger used it. n8n then created or deleted webhooks on the connected service with that credential's privileges, and delivered events from resources the member chose to the member's workflow.
The issue has been fixed in n8n versions 1.123.96, 2.47.6, 2.48.3 and 3.2.2. 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:
These workarounds do not fully remediate the risk and should only be used as short-term mitigation measures.
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.
InfraStack checks it against your stack and answers on your report, with the evidence and the fix.
Upgrade to 3.2.2 · 2.48.3 · 1.123.96 +1
n8n 1.123.96n8n 2.47.6n8n 2.48.3n8n 3.2.2