CVE-2026-85166
largeIncorrect Authorization in n8n Enables Credential Exfiltration via Inline Sub-Workflows
n8n before 2.35.4 and 2.36.x before 2.36.2 fails to validate credential references in the inline workflow JSON of nodes that execute an inline sub-workflow, such as the Workflow Tool node (CWE-863, incorrect authorization). A user with workflow-editing rights — a shared-workflow editor, or anyone creating or updating a workflow via the REST API, Public API, or MCP — can persist a node that references a credential they do not own. When that workflow is later executed under an identity that holds the referenced credential, the inline sub-workflow resolves the secret and can send it to an attacker-controlled endpoint, exfiltrating credentials with high confidentiality impact. Any n8n deployment on affected versions where multiple users, shared workflows, or API/MCP-driven workflow creation is in use is affected; single-user instances face limited risk. Exploitation is not currently observed: there is no public PoC, CISA KEV listing is absent, and EPSS puts 30-day exploitation probability at about 0.2%.
What to do: Upgrade n8n to 2.35.4 or 2.36.2 (or later). Until patched, review existing workflows — especially Workflow Tool and other inline sub-workflow nodes — for credential references owned by other users or higher-privileged identities, and restrict workflow creation/updates via the REST API, Public API, and MCP to trusted users. After upgrading, audit recent workflow executions and outbound endpoints for signs that secrets were sent to unexpected destinations.
| n8n | before 2.35.4 and 2.36.x before 2.36.2 (fixed in 2.35.4 and 2.36.2) |
Order-of-magnitude estimate by the model from install counts, market share and public scan data it knows; verify before quoting.
n8n before 2.35.4 and 2.36.x before 2.36.2 does not validate credential references in the inline workflow JSON of nodes that execute an inline sub-workflow (e.g., the Workflow Tool node). A shared-workflow editor, or any user creating/updating a workflow via the REST API, Public API, or MCP, can persist a node referencing a credential they do not own. When the workflow is later executed under an identity that holds the credential, the inline sub-workflow resolves the secret and can send it to an attacker-controlled endpoint, resulting in credential exfiltration.
- Vendors
- n8n
- Products
- n8n
- Weakness
- CWE-863
- Vector
- CVSS:4.0/AV:N/AC:L/AT:P/PR:L/UI:N/VC:H/VI:N/VA:N/SC:H/SI:H/SA:L/E:X/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:X
In the news0 stories
No ingested article mentions this CVE yet.