Описание
n8n: External Secrets Accessible via Workflow Expressions Outside Credentials
Impact
External secrets were incorrectly resolved in workflow node expressions, where they are not intended to be available. An authenticated user with project editor access could read the plaintext value of external secrets by referencing them in a node expression, without needing explicit secrets access permissions.
This issue only affects instances with the external secrets feature configured.
Patches
The issue has been fixed in n8n versions 2.27.4 and 2.28.1. 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 project membership to fully trusted users only.
- Avoid granting editor access to projects on instances where external secrets are configured.
These workarounds do not fully remediate the risk and should only be used as short-term mitigation measures.
Ссылки
- https://github.com/n8n-io/n8n/security/advisories/GHSA-2434-3x6q-8r99
- https://nvd.nist.gov/vuln/detail/CVE-2026-59254
- https://github.com/n8n-io/n8n/releases/tag/n8n%402.27.4
- https://github.com/n8n-io/n8n/releases/tag/n8n%402.28.1
- https://www.vulncheck.com/advisories/n8n-external-secrets-disclosure-via-workflow-node-expressions
Пакеты
n8n
>= 2.28.0, < 2.28.1
2.28.1
n8n
< 2.27.4
2.27.4
Связанные уязвимости
n8n before 2.28.1 contains an information disclosure vulnerability where external secrets are incorrectly resolved in workflow node expressions outside credentials scope. Authenticated project editors can read plaintext external secret values by referencing them in node expressions without requiring explicit secrets access permissions.