CVE-2026-59253: n8n - Improper Authorization in Workflow Assignment to Folders
Impact An authenticated user with permission to create workflows in one project could bypass project/folder authorization boundaries during workflow creation. By supplying a crafted request payload, the user could associate a newly created workflow with a folder belonging to a different project they do not have access to.
The workflow itself remains in the attacker's project and is not visible to the target project's members. The target project's folder ownership is not changed, and no data from the target project is exposed. The impact is limited to a logical integrity violation of the target project's folder structure at the database level.
This issue affects instances with multi-project and folder support enabled.
Patches The issue has been fixed in n8n version 2.28.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 project membership and workflow creation permissions to fully trusted users only.
This workaround does not fully remediate the risk and should only be used as a short-term mitigation measure.
Other sources
n8n before 2.28.0 contains an improper authorization vulnerability allowing authenticated users to assign workflows to folders in other projects. Attackers can bypass project and folder authorization boundaries by supplying crafted request payloads during workflow creation, causing logical integrity violations in target project folder structures.
— 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.28.0 - Upgrade
Upgrade
n8nto a version that resolves this vulnerability.Fixed in 2.28.0 - Configuration
Restrict project membership and the ability to create workflows to fully trusted users only as a temporary mitigation for instances affected by improper authorization in workflow assignment to folders (multi-project and folder support enabled).
n8n project membership and workflow creation permissions = restricted to fully trusted users only
Event History
Frequently Asked Questions
What is the severity of CVE-2026-59253?
CVE-2026-59253 has a medium severity rating of 5.3 according to the CVSS score.
What type of vulnerability is described in CVE-2026-59253?
CVE-2026-59253 is an improper authorization vulnerability allowing users to assign workflows to unauthorized folders.
How can I fix CVE-2026-59253?
To fix CVE-2026-59253, update n8n to version 2.28.0 or later, where the vulnerability has been addressed.
Who is affected by CVE-2026-59253?
Authenticated users of n8n versions prior to 2.28.0 may be affected by CVE-2026-59253.
What are the potential consequences of exploiting CVE-2026-59253?
Exploiting CVE-2026-59253 could allow attackers to bypass project and folder authorization, impacting workflow integrity.