CVE-2026-42227: n8n: Public API Variables IDOR Allows Cross-Project Secret Disclosure
Impact An authenticated user with a valid API key scoped to variable:list could read variables from projects they are not a member of by supplying an arbitrary projectId query parameter to the public API variables endpoint. The handler queried the variables repository directly without enforcing project membership checks, bypassing the authorization-aware service layer used by the internal enterprise controller.
If variables were misused to store sensitive information such as credentials or tokens, they should be rotated immediately.
This issue only affects licensed enterprise or team deployments with multiple projects and the variables feature enabled.
Patches The issue has been fixed in n8n versions 1.123.32, 2.17.4, and 2.18.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 n8n access and API key issuance to fully trusted users only. - Audit existing project variables for sensitive values and rotate any secrets that may have been exposed.
These workarounds do not fully remediate the risk and should only be used as short-term mitigation measures.
Other sources
n8n is an open source workflow automation platform. Prior to versions 1.123.32, 2.17.4, and 2.18.1, an authenticated user with a valid API key scoped to variable:list could read variables from projects they are not a member of by supplying an arbitrary projectId query parameter to the public API variables endpoint. The handler queried the variables repository directly without enforcing project membership checks, bypassing the authorization-aware service layer used by the internal enterprise controller. If variables were misused to store sensitive information such as credentials or tokens, they should be rotated immediately. This issue only affects licensed enterprise or team deployments with multiple projects and the variables feature enabled. This issue has been patched in versions 1.123.32, 2.17.4, and 2.18.1.
— MITRE
Affected Software
Event History
Frequently Asked Questions
What is the severity of CVE-2026-42227?
CVE-2026-42227 has a medium severity rating, indicating that it poses a risk of unauthorized access to sensitive information.
How do I fix CVE-2026-42227?
To mitigate CVE-2026-42227, update to n8n versions 2.17.4, 2.18.1, or 1.123.32, which contain patches for the vulnerability.
Who is affected by CVE-2026-42227?
Users of n8n versions between 2.0.0 to 2.17.4 and those below version 2.18.0 are affected by CVE-2026-42227.
What flaw does CVE-2026-42227 exploit?
CVE-2026-42227 allows an authenticated user with a valid API key to read project variables they do not belong to by manipulating the projectId parameter.
Is there a workaround for CVE-2026-42227 until I can upgrade?
A temporary workaround for CVE-2026-42227 is to restrict access to the API endpoint and carefully control API key permissions.