n8n: Credential Authorization Bypass in dynamic-node-parameters Allows Foreign API Key Replay
No exploitation in the wild has been reported. EPSS puts the chance of exploitation in the next 30 days at 0%. Fixed in n8n 1.123.33 and n8n 2.17.5.
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.
Affected
Vendors, products and packages with version ranges
| Vendor | Product | Versions | Fixed |
|---|---|---|---|
| n8n | n8n | <1.123.33, >=2.17.0 <2.17.5 | 1.123.33, 2.17.5 |
| n8n-io | <1.123.33, >=2.17.0 <2.17.5 |
Timeline
Every event on this vulnerability
Related
Other vulnerabilities in n8n, strongest first
Embed
A live severity badge for an advisory, README or ticket