CVE-2026-65594: n8n Member-Level Users Can Execute Other Vulnerability
MODERATECVE-2026-65594 is a MODERATE member-level users can execute other vulnerability (CWE-863: Incorrect Authorization) affecting n8n libraries in the npm ecosystem. The issue involves member-level users can execute other users' mcp server trigger workflows via missing oauth authorization check. Remediation is available by upgrading affected packages to version 2.30.1, 2.29.8.
CVE-2026-65594 at a Glance
How to Fix CVE-2026-65594
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.
npm install n8n@2.30.1npm install n8n@2.29.8Run the following command in your project directory to verify that all resolved dependencies use the patched release:
npm ls n8nHow to Check if You Are Affected
To determine whether your Node.js application is affected by CVE-2026-65594, inspect your project dependencies using npm:
npm ls n8nAnalyze 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.30.1), 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-863: Incorrect Authorization, where the product performs an authorization check when an actor attempts to access a resource or perform an action, but it does not correctly perform the check. 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
CVE-2026-65594 Affected n8n Versions
2 component(s)References
Frequently Asked Questions
What is CVE-2026-65594?
Which n8n versions are affected?
What version fixes CVE-2026-65594?
Is n8n affected?
What CWE is associated with CVE-2026-65594?
How can I check npm dependencies for CVE-2026-65594?
Machine-readable OSV JSON
OSV v1.5 Schema
{
"schema_version" : "1.4.0",
"id" : "GHSA-q5xf-xhwf-cwqf",
"modified" : "2026-07-22T22:31:01Z",
"published" : "2026-07-22T22:31:01Z",
"aliases" : [ "CVE-2026-65594" ],
"summary" : "n8n: Member-Level Users Can Execute Other Users' MCP Server Trigger Workflows via Missing OAuth Authorization Check",
"details" : "## Impact\nThe OAuth 2.1 consent and token-issuance flow introduced in n8n 2.27.0 does not verify that the authenticated user has access to the workflow referenced as the OAuth resource. A member-level user can register an OAuth client, self-approve consent for another user's `n8n OAuth2`-protected MCP Server Trigger workflow, and obtain a valid token for it.\n\nThe workflow runs in the owner's project context with the owner's stored credentials. The attacker sets the tool inputs and reads the outputs, which may include data from the owner's connected integrations, breaking user and project isolation. The resulting executions appear under the owner's account and are not visible to the attacker.\n\nThis issue only affects instances running n8n 2.27.0 or later where at least one active workflow uses an MCP Server Trigger node configured with `n8n OAuth2` authentication.\n\n## Patches\nThe issue has been fixed in n8n versions 2.29.8 and 2.30.1. Users should upgrade to one of these versions or later to remediate the vulnerability.\n\n## Workarounds\nIf upgrading is not immediately possible, administrators should consider the following temporary mitigations:\n- Restrict n8n instance access to fully trusted users only.\n- Audit active workflows using the MCP Server Trigger with `n8n OAuth2` authentication and consider switching to a different authentication method or deactivating them until the patch is applied.\n\nThese workarounds do not fully remediate the risk and should only be used as short-term mitigation measures.",
"severity" : [ {
"type" : "CVSS_V4",
"score" : "CVSS:4.0/AV:N/AC:L/AT:P/PR:L/UI:N/VC:L/VI:L/VA:N/SC:H/SI:L/SA:N"
} ],
"affected" : [ {
"package" : {
"ecosystem" : "npm",
"name" : "n8n"
},
"ranges" : [ {
"type" : "ECOSYSTEM",
"events" : [ {
"introduced" : "2.30.0"
}, {
"fixed" : "2.30.1"
} ]
} ]
}, {
"package" : {
"ecosystem" : "npm",
"name" : "n8n"
},
"ranges" : [ {
"type" : "ECOSYSTEM",
"events" : [ {
"introduced" : "0"
}, {
"fixed" : "2.29.8"
} ]
} ]
} ],
"references" : [ {
"type" : "WEB",
"url" : "https://github.com/n8n-io/n8n/security/advisories/GHSA-q5xf-xhwf-cwqf"
}, {
"type" : "ADVISORY",
"url" : "https://nvd.nist.gov/vuln/detail/CVE-2026-65594"
}, {
"type" : "PACKAGE",
"url" : "https://github.com/n8n-io/n8n"
}, {
"type" : "WEB",
"url" : "https://github.com/n8n-io/n8n/releases/tag/n8n@2.29.8"
}, {
"type" : "WEB",
"url" : "https://github.com/n8n-io/n8n/releases/tag/n8n@2.30.1"
}, {
"type" : "WEB",
"url" : "https://www.vulncheck.com/advisories/n8n-before-missing-oauth-authorization-check"
} ],
"database_specific" : {
"cwe_ids" : [ "CWE-863" ],
"severity" : "MODERATE",
"github_reviewed" : true,
"github_reviewed_at" : "2026-07-22T22:31:01Z",
"nvd_published_at" : null
}
}