Kurz gesagt
- CVE-2026-33722 ist eine Schwachstelle (MITTEL (CVSS 5.3)) in n8n (n8n), n8n.
- Wahrscheinlichkeit einer Ausnutzung in den nächsten 30 Tagen (EPSS): 0.27%, höher als bei 18.4% aller Schwachstellen.
- Abhilfe: auf 2.6.4, 1.123.23 oder neuer aktualisieren.
| Package | Affected versions | Patched versions |
|---|
| n8n | ≥ 2.0.0, < 2.6.4< 1.123.23
| 2.6.41.123.23
|
| n8n npm | ≥ 2.0.0-rc.0, < 2.6.4< 1.123.23
| 2.6.41.123.23
|
Description
Impact
An authenticated user without permission to list external secrets could reference a secret by the external name in a credential and retrieve its plaintext value when saving the credential. This bypassed the externalSecret:list permission check and allowed access to secrets stored in connected vaults without admin or owner privileges.
- This issue requires the instance to have an external secrets vault configured.
- The attacker must know or be able to guess the name of a target secret.
Patches
The issue has been fixed in n8n versions 1.123.23 and 2.6.4. Users should upgrade to one of these versions 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.
- Disable external secrets integration until the patch can be applied.
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 2.6.4 and 1.123.23, an authenticated user without permission to list external secrets could reference a secret by the external name in a credential and retrieve its plaintext value when saving the credential. This bypassed the `externalSecret:list` permission check and allowed access to secrets stored in connected vaults without admin or owner privileges. This issue requires the instance to have an external secrets vault configured. The attacker must know or be able to guess the name of a target secret. The issue has been fixed in n8n versions 1.123.23 and 2.6.4. Users should upgrade to one of these versions 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, and/or disable external secrets integration until the patch can be applied. These workarounds do not fully remediate the risk and should only be used as short-term mitigation measures.
Running one of these products? Scan your site to see whether it exposes a vulnerable version.
Scan my site free