Duplicate Node IDs Bypass Workflow Credential Tamper Guard, Exposing Credentials to a Shared Workflow Editor
GHSA-7gjv-rcf8-x5qc · published 2026-09-16
- Severity
- High
- CVSS score
- 7.1
- Chance of exploitation (EPSS)
- No CVE
- Fixed in
- 1.123.80
Workflows shared with an editor keep credential-bearing nodes read-only, reverting on save any node that references a credential the editor cannot access. The revert matched nodes by id while the runtime matches them by name, so of two nodes sharing an id only one was reverted — the other kept the editor's parameters and the victim's credential reference, letting them send the secret to a host they control.
Upgrade n8n to 1.123.80 or later. If you start it from an MCP config with npx or uvx, pin that version so an old cached copy is not used.
The issue has been fixed in n8n version 1.123.80. Users should upgrade to this version or later to remediate the vulnerability.
If upgrading is not immediately possible, administrators should consider the following temporary mitigations: Restrict n8n instance access to fully trusted users only. Audit shared workflows and remove the Editor role from any users who do not require it. Review workflow nodes for unexpected credential references or external URLs and rotate any credentials that may have been exposed. These workarounds do not fully remediate the risk and should only be used as short-term mitigation measures.
| Package | Registry | Affected | Fixed in |
|---|---|---|---|
| n8n | npm | < 1.123.80 | 1.123.80 |
- CriticalLiteLLM has SQL Injection in Proxy API key verificationlitellmExploited
- HighLiteLLM has a sandbox escape in custom-code guardraillitellmExploited
- HighLangflow affected by Remote Code Execution via validate_code() exec()langflowExploited
- CriticalJupyter MCP Server: Browser DNS rebinding can hijack the Jupyter backend through management routesjupyter-mcp-server
- Criticalmem0ai Databricks vector store vulnerable to SQL injectionmem0ai
- CriticalFlowise NodeVM sandbox escape via puppeteer allowlist - authenticated RCE and arbitrary file read via Chromiumflowise, flowise-components
- Criticaln8n Vulnerable to Remote Code Execution via Expression Injectionn8n, n8nExploited
- Criticaln8n Has an Arbitrary File Read via Git Noden8n, n8n, n8n
- Criticaln8n: HTTP Request Node Pagination Prototype Pollution to RCEn8n, n8n, n8n
- Criticaln8n Has an XML Node Prototype Pollution Patch Bypassn8n, n8n, n8n
- Criticaln8n has XML Node Prototype Pollution that to RCEn8n, n8n, n8n
- Criticaln8n has Prototype Pollution in XML Webhook Body Parser that Leads to RCEn8n, n8n, n8n
The impact, patch and workaround text comes from the advisory, shortened (published by n8n). Proof-of-concept and reproduction sections and code are left out; the original advisory has them.