N8N · GHSA-8crx-5h96-q72q · AI agents & MCP
FIX → >= 1.123.85 +2
n8n's save-time check on shared workflows does not inspect sub-workflows that the Execute Sub-workflow node loads from a URL or local file at run time. An editor of a shared workflow can therefore get credentials from the owning project resolved and receive their decrypted values.
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 or cloud n8n instances that share workflows with editors who are not fully trusted, and where a shared workflow contains an Execute Sub-workflow node that loads its sub-workflow from a URL or local file. Instances where every editor is fully trusted, or that do not share workflows, are less exposed.
Not affected if fully-trusted-editors, no-shared-workflows, single-owner-instance
Who cares credentials, n8n, self-hosted
n8n --version or the image tag; affected versions are below 1.123.85 on the 1.x line, below 2.43.5 on the 2.43 line, and below 2.44.1 on the 2.44 line.When a workflow is shared for editing, n8n checks on save that the editor does not add credentials they may not use. The Execute Sub-workflow node can load its sub-workflow from a URL or a local file at run time, and the check never saw that content. An editor of a shared workflow can therefore have credentials of the workflow's project resolved by a sub-workflow they serve, and receive the decrypted values.
The issue has been fixed in n8n versions 1.123.85, 2.44.1, and 2.43.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:
source: url or source: localFile parameters and remove or restrict them.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.
source: urlsource: localFileUpgrade to >= 1.123.85 +2
1.123.852.43.52.44.1