Auth bypass in N8n
CVE-2026-65594
n8n before 2.29.8 and 2.30.x before 2.30.1 (affected from 2.27.0, when the OAuth 2.1 consent and token-issuance flow was introduced) does not verify that the authenticated user has access to the workflow referenced as the OAuth resource. On instances with at least one active MCP Server Trigger workflow configured with n8n OAuth2 authentication, a member-level user can register an OAuth client, self-approve consent for another user's workflow, and obtain a valid token. The workflow then runs in the owner's project context with the owner's stored credentials, and the attacker can set tool inputs and read outputs (potentially including data from the owner's connected integrations), breaking user and project isolation.
Vulnerability class: Broken Access Control
Published · last modified .
CVSS v3 metric
CVSS v3 base score 6.5 (Medium). Vector: CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N.
EPSS exploit prediction
EPSS 0.004, 38.8th percentile (scored ); unchanged over 30 days. About EPSS.
Affected products
- N8n — versions 2.30.0
- N8n-Io N8n — versions 0, 2.30.1, 2.29.8
Weakness classification (CWE)
References
- GitHub Security Advisory (GHSA-q5xf-xhwf-cwqf) (vendor-advisory, Mitigation, Vendor Advisory)
- VulnCheck Advisory: n8n before 2.30.1 Missing OAuth Authorization Check (Third Party Advisory, third-party-advisory)