CVE-2026-59254: n8n - External Secrets Disclosure via Workflow Node Expressions
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.
Other sources
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.
— NVD
Affected Software
Remediation
Recommended actions to resolve this vulnerability, in priority order.
- Upgrade
Upgrade
npm/n8nto a version that resolves this vulnerability.Fixed in 2.27.4 - Upgrade
Upgrade
npm/n8nto a version that resolves this vulnerability.Fixed in 2.28.1 - Upgrade
Upgrade
n8nto a version that resolves this vulnerability.Fixed in 2.27.4 - Upgrade
Upgrade
n8nto a version that resolves this vulnerability.Fixed in 2.28.1 - Compensating control
Temporary mitigation: Avoid granting editor access to projects on instances where external secrets are configured.
- Compensating control
Temporary mitigation: Restrict project membership to fully trusted users only.
Event History
Frequently Asked Questions
What is the severity of CVE-2026-59254?
CVE-2026-59254 has a medium severity rating of 6.3 based on the CVSS score.
How do I fix CVE-2026-59254?
To fix CVE-2026-59254, upgrade to n8n version 2.28.1 or later where the vulnerability is resolved.
Who is affected by CVE-2026-59254?
Authenticated project editors using n8n before version 2.28.1 are affected by CVE-2026-59254.
What is the nature of CVE-2026-59254?
CVE-2026-59254 involves information disclosure where external secrets can be accessed improperly through workflow node expressions.
Can CVE-2026-59254 be exploited remotely?
CVE-2026-59254 requires authenticated access, meaning it can be exploited by users with editor permissions.