N8N · GHSA-8vrr-mgc5-jg55 · AI agents & MCP
FIX → >= 1.123.85 +2
n8n checks credential access before a workflow runs, but a node inside an inline sub-workflow with a non-boolean disabled value can be skipped by that check while still executing. A member who knows the id of a credential they cannot access can run such a node and send the decrypted credential to a server they control.
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.
Self-hosted n8n instances with multiple users who have member access, where workflows use inline sub-workflows (Execute Workflow nodes in inline JSON mode) and credentials are stored. Instances used only by fully trusted users have a lower practical risk, though the advisory still recommends upgrading.
Not affected if managed-hosting-patched, single-user-instance
Who cares n8n, self-hosted, workflow-automation
n8n --version or the n8n entry in package.json; versions below 1.123.85, 2.43.5 or 2.44.1 on their respective lines are affected.Before a workflow runs, n8n checks that the user may use each credential its nodes reference. The check and the execution engine decided in different ways whether a node is disabled, so a node inside an inline sub-workflow could be skipped by the check and still run. A member who knows the id of a credential they have no access to can run such a node and send the decrypted credential to a server they control.
The issue has been fixed in n8n versions 1.123.85, 2.43.5, and 2.44.1. 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.
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 >= 1.123.85 +2
1.123.852.43.52.44.1