How severe is CVE-2026-59253?

No CVSS score has been assigned to CVE-2026-59253 yet. Review the advisory details and affected package list to assess your exposure.

Which packages are affected by CVE-2026-59253?

CVE-2026-59253 affects the following packages: n8n (npm). Ecosystems affected: npm.

How do I fix CVE-2026-59253?

Update n8n to 2.28.0 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2026-59253 is resolved across your whole dependency graph.

How do I detect CVE-2026-59253 in my npm dependencies?

Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for n8n, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.

How do I mitigate CVE-2026-59253 if there is no patch (or I can't update yet)?

If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.

Is CVE-2026-59253 actively exploited in the wild?

No public exploit code has been indexed for CVE-2026-59253 yet. This does not mean the vulnerability cannot be exploited — absence of public exploits does not imply safety. Apply the recommended fix and use O3 Security to monitor your exposure.

What is the EPSS score for CVE-2026-59253?

CVE-2026-59253 has an EPSS (Exploit Prediction Scoring System) score of 0.3%, placing it in the 19th percentile of all CVEs. EPSS is maintained by FIRST.org and estimates the probability that a vulnerability will be exploited in the wild within the next 30 days. This score indicates relatively lower exploitation probability, though the CVSS severity should still guide your patching priority.

What type of vulnerability is CVE-2026-59253?

CVE-2026-59253 is classified as CWE-639 (CWE-639). This weakness type describe the underlying flaw category, which helps determine the potential impact and the right class of mitigation.

When was CVE-2026-59253 published, and has it been updated?

CVE-2026-59253 was published on July 8, 2026 and was last updated on October 21, 2026. Advisory data evolves as severity scores, affected ranges, and exploit intelligence are revised — always check the latest version of the advisory before acting.

📦 npm

Not in CISA KEV

CVE-2026-59253 — n8n

CVE-2026-59253 is a CWE-639 vulnerability in n8n. A fix is available for n8n — see the affected versions and patch details below.

n8n - Improper Authorization in Workflow Assignment to Folders

Also known asGHSA-2xgm-wc4g-5jvg

Published

Jul 8, 2026

Updated

Oct 21, 2026

Affected

1 pkg

Patched

1 / 1

Exploits

None indexed

Exploitation data as of Oct 22, 2026 · OSV.dev, NVD, FIRST.org (EPSS)

Exploitation Status

No confirmed exploitation observed yet

CISA’s own triage has not observed active exploitation or public proof-of-concept code for this CVE as of its last assessment.

Exploitation and automatability from CISA’s SSVC triage for CVE-2026-59253.

EPSS Exploitation Probability

via FIRST.org ↗

0.3%probability of exploitation in next 30 days

Lower Risk0.00%

Lower risk than most CVEs19th percentile — riskier than 19% of all scored CVEsHighest risk

Probability of exploitation in the next 30 days, from FIRST.org EPSS.

Real-World Exposure

1 pkg affected

How broadly this vulnerability is actually deployed: weekly install volume shows current usage, and reverse-dependency count shows how many other packages break if it stays unpatched.

36other npm packages depend on this — each one inherits the vulnerability until it's patched upstream

n8nnpm

85Kdownloads / week

Description

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.

Affected Packages

1 total 1 fixed

Ecosystem	Package	Vulnerable range	Fix
📦npm	`n8n`	all versions	2.28.0`npm install n8n@2.28.0`

Affected Products

1 product · 1 configurations

Application

n8nn8n

< 2.28.0

range

Detection & mitigation playbook

Open-source dependency

Detect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for n8n, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update n8n to 2.28.0 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2026-59253 is resolved across your whole dependency graph.
Workarounds
If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.

Frequently Asked Questions

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

O3 Security · Impact-Aware SCA

Is CVE-2026-59253 in your dependencies?

Find it across npm, including transitive dependencies.

Scan my dependencies How O3 SCA works

CVE-2026-59253 — n8n

Exploitation Status

No confirmed exploitation observed yet

EPSS Exploitation Probability

Real-World Exposure

Description

Impact

Patches

Workarounds

Affected Packages

Affected Products

Detection & mitigation playbook

Detect

Fix

Workarounds

Frequently Asked Questions

Is CVE-2026-59253 in your dependencies?