CyberRota Analysis
AI-GeneratedThe vulnerability affects n8n versions prior to 2.30.1, allowing authenticated users to exploit OAuth 2.1 flows by registering an OAuth client and self-approving consent for workflows belonging to other users. This can lead to unauthorized access to sensitive data and execution of actions within the owner's project context, compromising user and project isolation. Organizations using n8n with active MCP Server Trigger workflows should prioritize patching to mitigate potential data breaches and unauthorized actions.
Public Exploit Signal
A public exploit, PoC, GitHub repository or Metasploit reference was detected for this CVE.
Note: these links are listed for security research and verification purposes only.
Original NVD Description
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.
Related CVEs
Other vulnerabilities affecting the same vendor(s)