CVE-2026-42226: n8n's Credential Authorization Bypass in dynamic-node-parameters Allows Foreign API Key Replay
n8n's dynamic-node-parameters endpoints did not check that the caller may use the credential ID in the request. A user with access to a shared workflow could name someone else's credential and a destination URL they control, and n8n would send that credential's API key to their server. Fixed per the package data in n8n 1.123.33 and 2.17.5.
Published Apr 29, 2026 · Updated May 8, 2026 · Analysis Oct 28, 2026
What an attacker can do
The dynamic-node-parameters endpoints load options for node fields. They accepted a credential ID in the request body without an authorization check (CWE-862). The backend decrypted that credential and used it in a helper execution path where the caller also controls the destination URL.
The attacker is an authenticated user who has access to a shared workflow. They send another user's credential ID and a URL pointing at infrastructure they run. n8n authenticates to that URL with the foreign credential, and the attacker reads the key from the incoming request. The result is a reusable API key for whatever service the credential belongs to.
The advisory says the problem is not limited to one node type: any node that resolves credentials dynamically through these endpoints may be affected. Credential IDs are the part the attacker must obtain; a shared workflow can reveal the credentials it references.
Who is affected
The npm package n8n below 1.123.33, and 2.17.x below 2.17.5, according to the package data. The advisory text says the fix is in 2.18.0, so a 2.18.x release is also fine. Instances with shared workflows and several users carry the risk.
npm ls n8nFor Docker, check the image tag.
n8n
- Ecosystem
- npm
- Affected
- >= 2.17.0, < 2.17.5
- Fixed in
- 2.17.5
- Check
npm ls n8n
n8n
- Ecosystem
- npm
- Affected
- < 1.123.33
- Fixed in
- 1.123.33
- Check
npm ls n8n
How to fix it
Upgrade to n8n 1.123.33 or 2.17.5, or to 2.18.0 or later. The advisory's text names 2.18.0; the package data lists 1.123.33 and 2.17.5 for the older lines. Pick the newest in your line.
Temporary mitigations from the advisory (not a full fix): restrict n8n access to fully trusted users, and avoid sharing workflows with users who should not have access to the credentials those workflows reference. Rotate credentials that may have been exposed.
How to tell if you were hit
Review the n8n server access logs for requests to the dynamic-node-parameters endpoints that carry a credential ID the calling user does not own, or a custom destination URL. Check outbound connections from the n8n host to unfamiliar domains. For services whose keys were stored in n8n, look at provider logs for use of those keys from unexpected addresses.
Original advisory
From the GitHub Advisory Database (CC BY 4.0).
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.
Credited to ESPanda666.
Questions
- What does the attacker gain?
A reusable API key. n8n sends the foreign credential to a URL the attacker controls.
- Is it limited to certain nodes?
No. The advisory says any node that resolves credentials dynamically through these endpoints may be affected.
- Which version fixes CVE-2026-42226?
The advisory text says 2.18.0. The package data lists 1.123.33 and 2.17.5 for older lines.
References
How this page is made: the data panel comes from the GitHub Advisory Database, CISA’s KEV catalog, the NVD and FIRST EPSS, and updates twice a day. The analysis is written by an AI model from the sources listed above and checked by automated rules before it is published. Check versions against the vendor's advisory before you act. Methodology
More n8n vulnerabilities
All n8n entriesCVE-2026-86073
n8n: Per-Resource OAuth Consent Bypass via Unbound Refresh Token Resource Substitution
medium5.9Sep 10, 2026CVE-2026-86074
n8n: Instance AI Credential Setup Accepts Unvalidated Probe URL from Fetched Content
medium5.9Sep 10, 2026CVE-2026-86075
n8n: Unauthenticated Persistent Storage Exhaustion via OAuth Dynamic Client Registration Endpoint
high8.7Sep 10, 2026CVE-2026-86076
n8n: Expression Sandbox Escape via Class-Field Sanitizer Rebinding Can Lead to Code Execution
high8.7Sep 10, 2026CVE-2026-86077
n8n: Anonymous Approval-Gate Bypass via Reused resumeToken over the Chat WebSocket
medium6.3Sep 10, 2026CVE-2026-86078
n8n: Prototype Pollution via Workflow Structure Summary Can Lead to Denial of Service
medium6.0Sep 10, 2026
