Kurz gesagt
- CVE-2026-42226 ist eine Schwachstelle (HOCH (CVSS 7.5)) in n8n (n8n), n8n.
- Wahrscheinlichkeit einer Ausnutzung in den nächsten 30 Tagen (EPSS): 0.26%, höher als bei 17.7% aller Schwachstellen.
- Abhilfe: auf 2.17.5, 1.123.33 oder neuer aktualisieren.
| Package | Affected versions | Patched versions |
|---|
| n8n | ≥ 2.17.0, < 2.17.5< 1.123.33
| 2.17.51.123.33
|
| n8n npm | ≥ 2.17.0, < 2.17.5< 1.123.33
| 2.17.51.123.33
|
Description
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.
NVD description
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.
Running one of these products? Scan your site to see whether it exposes a vulnerable version.
Scan my site free