Shared-Workflow Credential Check Misses Nested and Tool Inline Sub-Workflows
GHSA-r6g9-5cpp-ppwr · published 2026-09-30
- Severity
- High
- CVSS score
- 7.2
- Chance of exploitation (EPSS)
- No CVE
- Fixed in
- 1.123.83
On the version 1.x, the save-time check that stops a shared-workflow editor introducing credentials they are not allowed to use inspected only one node type, one level deep. Two other nodes also accept an inline workflow in their parameters, and inline workflows can nest. An editor can therefore save a workflow whose embedded nodes reference credentials they have no access to; at execution those nodes run with the owner's credential values.
Upgrade n8n to 1.123.83 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.83. 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 for Workflow Tool or Workflow Retriever nodes that use an inline workflow definition and verify that any referenced credentials are accessible to all users with edit access to that workflow. Restrict workflow sharing to the minimum set of users required until the instance is patched. 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.83 | 1.123.83 |
- 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.