PT-2026-63352 · N8N Io · N8N

CVE-2026-65594 · Published 2026-07-22 · Updated 2026-07-22

NVD

CVSS v4.0

5.1

Medium

Base vector

AV:N/AC:L/AT:P/PR:L/UI:N/VC:L/VI:L/VA:N/SC:H/SI:L/SA:N/E:X/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:X

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.

Fix

Incorrect Authorization

Weakness Enumeration

CWE-863

Related Identifiers

CVE-2026-65594

Affected Products

N8N

References · 3

• https://github.com/n8n-io/n8n/security/advisories/GHSA-q5xf-xhwf-cwqf · Vendor Advisory
• https://nvd.nist.gov/vuln/detail/CVE-2026-65594 · Security Note
• https://vulncheck.com/advisories/n8n-before-missing-oauth-authorization-check · Note