Advisory

GHSA-q5xf-xhwf-cwqf

Also known as: CVE-2026-65594

Summary

n8n: Member-Level Users Can Execute Other Users' MCP Server Trigger Workflows via Missing OAuth Authorization Check

Details

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.

Severity

Medium Basis: The source's own band: MODERATE

Dates

Published
2026-07-22 22:31 UTC
Modified
2026-07-22 22:56 UTC

Affected packages and fixes

n8n

npm · All systems

Affected

  • introduced 2.30.0, fixed 2.30.1 (semver)

Fixed versions

2.30.1

Fix

n8n

npm · All systems

Affected

  • introduced 0, fixed 2.29.8 (semver)

Fixed versions

2.29.8

Fix

Fix commands are the export's own generic commands. Ojuju never runs them. Check them against your setup first.

Check your own computer: guard packages check

View this record on OSV.dev

Source

Source: GitHub Advisory Database (reviewed advisories) · CC BY 4.0

Sources & licences