Cross-project folder assignment via unchecked workflow payload
Published Jul 8, 2026 · Updated Jul 8, 2026
Improper authorization in n8n before 2.28.0 allows remote authenticated users to assign workflows to folders in other projects. During workflow creation, the server accepts a client-supplied folder identifier without enforcing that the folder belongs to the creator's project. Exploitation requires workflow-creation permission and multi-project folder support; it alters folder structure metadata without exposing target-project data.
Summary
What happened
Improper authorization in n8n before 2.28.0 allows remote authenticated users to assign workflows to folders in other projects. During workflow creation, the server accepts a client-supplied folder identifier without enforcing that the folder belongs to the creator's project. Exploitation requires workflow-creation permission and multi-project folder support; it alters folder structure metadata without exposing target-project data.
The record
- CVE
- CVE-2026-59253
- Published
- Jul 8, 2026
- Updated
- Jul 8, 2026
- Vendor
- n8n
- Product
- n8n
- Classifications
- CWE-639
- Attack vector
- network
- Privileges
- authenticated
Timeline
How it unfolded
- Jul 8, 2026CVE publishedPublication date reported by the CVE source.
- Jul 8, 2026Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=0 <2.28.0
What conditions does exploitation require?
What is affected?
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Weakness, pattern, technique
Public exploit references
No public exploit references are available in this record.
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo