Advisoriesby Ibisn8n: improper authorization
Impact
The 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.
The 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.
This 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.
Patches
The 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.
Workarounds
If upgrading is not immediately possible, administrators should consider the following temporary mitigations:
- Restrict n8n instance access to fully trusted users only.
- Audit active workflows using the MCP Server Trigger with
n8n OAuth2authentication and consider switching to a different authentication method or deactivating them until the...
Affected versions
| Package | Affected | Fixed in |
|---|---|---|
| n8n npm | >= 2.30.0, < 2.30.1 | 2.30.1 |
| < 2.29.8 | 2.29.8 |
Details and references
## Impact The 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. The 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. This 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. ## Patches The 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. ## Workarounds If upgrading is not immediately possible, administrators should consider the following temporary mitigations: - Restrict n8n instance access to fully trusted users only. - 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. These workarounds do not fully remediate the risk and should only be used as short-term mitigation measures.
- CVSS 4.0
- 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
- Severity from
- GitHub (reviewed advisory)
- Weakness
- CWE-863
- Also known as
- CVE-2026-65594
More n8n advisories
All n8n
n8n: Snowflake Node executeQuery Operation Allows SQL Injection via Unparameterized Expression InterpolationCVE-2026-72750fixed in 1.123.67 +2n8n: SQL injectionCVE-2026-72775fixed in 1.123.67 +2n8n: Cross-Tenant Module-Cache Poisoning in the JS Task RunnerCVE-2026-72764fixed in 1.123.67 +2n8n: Custom Header Credential Values Leaked in Plaintext into LLM Node Execution DataCVE-2026-65589fixed in 1.123.64 +2n8n: Unauthenticated Endpoint Allows Cancellation of Any User's Active Test WebhookCVE-2026-65014fixed in 2.27.4n8n: GraphQL Node Bypasses "Allowed HTTP Request Domains" RestrictionCVE-2026-65596fixed in 1.123.64 +2