CVE-2026-59253: n8n Improper Authorization Allows Authenticated Users Vulnerability

MODERATE
Advisory Identifier: GHSA-2xgm-wc4g-5jvg
CWE-639
Published
Advisory Summary

CVE-2026-59253 is a MODERATE improper authorization allows authenticated users vulnerability (CWE-639: Authorization Bypass Through User-Controlled Key) affecting n8n libraries in the npm ecosystem. The issue involves improper authorization allows authenticated users to assign workflows to folders in other projects. Remediation is available by upgrading affected packages to version 2.28.0.

CVE-2026-59253 at a Glance

CVE Identifier CVE-2026-59253
GHSA Identifier GHSA-2xgm-wc4g-5jvg
Severity MODERATE
CVSS v3.1 Base Score N/A
CWE Classification CWE-639: Authorization Bypass Through User-Controlled Key
Affected Product n8n
Package Ecosystem npm
Published Date
Last Updated

How to Fix CVE-2026-59253

To remediate this vulnerability, upgrade all affected n8n dependencies to a patched release. Both direct and transitive dependencies should be checked, as frameworks or security libraries may pull in vulnerable versions transitively.

n8n fixed: 2.28.0
npm install n8n@2.28.0
Verify Direct and Transitive Dependencies

Run the following command in your project directory to verify that all resolved dependencies use the patched release:

npm ls n8n

How to Check if You Are Affected

To determine whether your Node.js application is affected by CVE-2026-59253, inspect your project dependencies using npm:

npm ls n8n

Analyze the terminal output to locate any version of n8n in your dependency tree. If any resolved version matches the vulnerable ranges listed in the table below (for example, versions earlier than 2.28.0), your application is affected.

Note: The npm ls n8n command inspects dependencies declared in your package.json and lockfile; it does not perform automated runtime dynamic scanning.

Technical Details

Vulnerability Mechanism & Technical Analysis

This vulnerability is classified under CWE-639: Authorization Bypass Through User-Controlled Key, where the system's authorization functionality does not prevent one user from gaining access to another user's data or record by modifying the key value identifying the data. In n8n, software state validation or input boundaries are circumvented during processing. Review the official source advisory statement below for specific affected components, classes, and reproduction details.

Source Advisory Statement

## 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.

CVE-2026-59253 Affected n8n Versions

1 component(s)
Fixed Versions:
2.28.0
Product / Package Ecosystem Affected Versions Fixed Version
n8n
npm
< 2.28.0
2.28.0

References

Frequently Asked Questions

What is CVE-2026-59253?
CVE-2026-59253 is a security vulnerability in n8n involving Improper Authorization Allows Authenticated Users to Assign Workflows to Folders in Other Projects under CWE-639: Authorization Bypass Through User-Controlled Key.
Which n8n versions are affected?
Affected versions include releases prior to 2.28.0 across affected packages: n8n.
What version fixes CVE-2026-59253?
Upgrading to 2.28.0 (or the latest patched release for your respective branch) resolves the vulnerability.
Is n8n affected?
Yes, n8n is affected in releases prior to 2.28.0. Upgrade your dependency to 2.28.0 or later.
What CWE is associated with CVE-2026-59253?
CVE-2026-59253 is classified under CWE-639: Authorization Bypass Through User-Controlled Key (The system's authorization functionality does not prevent one user from gaining access to another user's data or record by modifying the key value identifying the data.).
How can I check npm dependencies for CVE-2026-59253?
Run the dependency tree command: 'npm ls n8n'. This command lists direct and transitive dependencies in your build configuration so you can verify if a vulnerable version is resolved.
Machine-readable OSV JSON OSV v1.5 Schema
Normalized schema output
{
  "schema_version" : "1.4.0",
  "id" : "GHSA-2xgm-wc4g-5jvg",
  "modified" : "2026-07-22T22:24:43Z",
  "published" : "2026-07-22T22:24:43Z",
  "aliases" : [ "CVE-2026-59253" ],
  "summary" : "n8n: Improper Authorization Allows Authenticated Users to Assign Workflows to Folders in Other Projects",
  "details" : "## Impact\nAn 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.\n\nThe 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.\n\nThis issue affects instances with multi-project and folder support enabled.\n\n## Patches\nThe issue has been fixed in n8n version 2.28.0. Users should upgrade to this version or later to remediate the vulnerability.\n\n## Workarounds\nIf upgrading is not immediately possible, administrators should consider the following temporary mitigations:\n- Restrict project membership and workflow creation permissions to fully trusted users only.\n\nThis workaround does not fully remediate the risk and should only be used as a short-term mitigation measure.",
  "severity" : [ {
    "type" : "CVSS_V4",
    "score" : "CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:N/VI:L/VA:N/SC:N/SI:L/SA:N"
  } ],
  "affected" : [ {
    "package" : {
      "ecosystem" : "npm",
      "name" : "n8n"
    },
    "ranges" : [ {
      "type" : "ECOSYSTEM",
      "events" : [ {
        "introduced" : "0"
      }, {
        "fixed" : "2.28.0"
      } ]
    } ]
  } ],
  "references" : [ {
    "type" : "WEB",
    "url" : "https://github.com/n8n-io/n8n/security/advisories/GHSA-2xgm-wc4g-5jvg"
  }, {
    "type" : "ADVISORY",
    "url" : "https://nvd.nist.gov/vuln/detail/CVE-2026-59253"
  }, {
    "type" : "PACKAGE",
    "url" : "https://github.com/n8n-io/n8n"
  }, {
    "type" : "WEB",
    "url" : "https://github.com/n8n-io/n8n/releases/tag/n8n@2.28.0"
  }, {
    "type" : "WEB",
    "url" : "https://www.vulncheck.com/advisories/n8n-improper-authorization-in-workflow-assignment-to-folders"
  } ],
  "database_specific" : {
    "cwe_ids" : [ "CWE-639" ],
    "severity" : "MODERATE",
    "github_reviewed" : true,
    "github_reviewed_at" : "2026-07-22T22:24:43Z",
    "nvd_published_at" : null
  }
}