n8n's Credential Authorization Bypass in dynamic-node-parameters Allows Foreign API Key Replay
CVE-2026-42226 · GHSA-r4v6-9fqc-w5jr · published 2026-04-29 · updated 2026-05-08
- Severity
- High
- CVSS score
- 8.5
- Chance of exploitation (EPSS)
- 0.26%
- Fixed in
- 2.17.5
- Exploitation No known exploitation
- Automatable No
- Technical impact Partial
- CISA SSVC
The dynamic-node-parameters endpoints did not verify whether the authenticated caller was authorized to use a supplied credential reference. An authenticated user with access to a shared workflow could supply a foreign credential ID in the request body, causing the backend to decrypt and use that credential in a helper execution path where the caller also controls the destination URL. This allowed the caller to force the backend to authenticate against attacker-controlled infrastructure using a credential belonging to another user, effectively exfiltrating a reusable API key.
Upgrade n8n to 2.17.5 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 2.18.0. 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 access to fully trusted users only. Avoid sharing workflows with users who should not have access to the credentials those workflows reference. These workarounds do not fully remediate the risk and should only be used as short-term mitigation measures.
- CriticalMarimo: Pre-Auth Remote Code Execution via Terminal WebSocket Authentication BypassmarimoExploited
- CriticalLangflow CORS misconfiguration enables Account Takeover and RCElangflowExploited
- HighLiteLLM: MCP Authentication Bypass via OAuth2 Passthrough FallbacklitellmExploited
- HighLangflow: IDOR Vulnerability in `/api/v1/responses` Endpoint Allows Authenticated Attackers to Access Another User's FlowlangflowExploited
- CriticalTodoist MCP Server: Browser DNS rebinding lets websites write and delete Todoist data through local MCP server@doist/todoist-mcp
- CriticalLangflow: Unauthenticated Flow Execution via Webhook Authentication Bypasslangflow
- 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 (GitHub Advisory Database, CC BY 4.0). Proof-of-concept and reproduction sections and code are left out; the original advisory has them.