CVE-2026-42226: n8n: Credential Authorization Bypass in dynamic-node-parameters Allows Foreign API Key Replay
Impact 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.
The issue is not limited to any single node type; any node that resolves credentials dynamically through these endpoints may be affected.
Patches The issue has been fixed in n8n version 2.18.0. Users should upgrade to this version or later to remediate the vulnerability.
Workarounds 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.
Other sources
n8n is an open source workflow automation platform. Prior to versions 1.123.33 and 2.17.5, 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. The issue is not limited to any single node type; any node that resolves credentials dynamically through these endpoints may be affected. This issue has been patched in versions 1.123.33, 2.17.5, and 2.18.0.
— MITRE
Affected Software
Event History
Frequently Asked Questions
What is the severity of CVE-2026-42226?
CVE-2026-42226 has been classified with a critical severity due to unauthorized access risks.
How do I fix CVE-2026-42226?
To fix CVE-2026-42226, update n8n to version 1.123.33 or 2.17.5.
What environments are affected by CVE-2026-42226?
CVE-2026-42226 affects n8n versions below 1.123.33 and versions between 2.17.0 and 2.17.5.
What kind of attack can CVE-2026-42226 enable?
CVE-2026-42226 can enable unauthorized users to access sensitive data using foreign credential IDs.
Is there any workaround for CVE-2026-42226?
Currently, there are no known workarounds for CVE-2026-42226; upgrading is the only solution.