NPM · JULY 2026 · EARLY WARNING

n8n npm Package Vulnerability: Improper Authorization Reported

EARLY WARNING · UNCONFIRMED. This page describes a developing threat that 0Day surfaced from early signals and has not yet independently confirmed. Details may change. Always verify against the primary sources before acting.

GHSA-2XGM-WC4G-5JVGSeverity: HIGH

An improper authorization vulnerability has been reportedly discovered in the n8n npm package, affecting versions prior to 2.28.0. This vulnerability allows authenticated users to assign workflows to folders in other projects, leading to a logical integrity violation at the database level.

What happened

The n8n npm package is under investigation for an improper authorization vulnerability tracked as GHSA-2XGM-WC4G-5JVG. This vulnerability appears to allow authenticated users to assign workflows to folders in projects other than their own. This results in a logical integrity violation of the target project's folder structure at the database level.

To assess your exposure, check if your project is using n8n version <2.28.0. If so, it is recommended to upgrade to version 2.28.0 or later to remediate the vulnerability. Consult the primary sources for more detailed information and guidance on upgrading.

How 0Day mitigates this

MATCHED TO YOUR ACTUAL DEPENDENCY GRAPH0Day matches every incoming threat signal against your GitHub organization’s full dependency graph, including transitive dependencies. If n8n is anywhere in your dependency tree, the engineers who own the affected repositories get a push alert the moment it is flagged — no manual audit to remember to run.

Read how this differs from waiting on a scanner to catch a known advisory, or see the exact, read-only access 0Day needs to do this for an organization.

Join the 0Day waitlist →

← Back to all threats