Vulnerability · Published Jul 22, 2026 · Assigned by VulnCheck

CVE-2026-65594n8n before 2.30.1 Missing OAuth Authorization Check

Medium 5.1

In plain English

A medium-severity incorrect authorization in n8n from n8n-io. There are no confirmed reports of exploitation so far. The chance it is exploited in the next 30 days is estimated at 0.4% (higher than 38% of all known vulnerabilities). Fixed versions are available - upgrade the affected package.

Severity (CVSS 4.0)5.1Medium
Exploit odds (30 days)0.4%top 61.5% of all CVEs
Exploited in the wildNo reportsCISA SSVC: none
Attack toolingNoneno public tooling known

Official 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.

Affected packages & fixed versions

EcosystemPackageFixed inAdvisory
npmn8n2.30.1GHSA-q5xf-xhwf-cwqf
npmn8n2.29.8GHSA-q5xf-xhwf-cwqf

Affected products (as reported)

VendorProductVersions
n8n-io n8n 2.30.0 – before 2.30.1
n8n-io n8n 0 – before 2.29.8

Weakness: CWE-863 · Vector: 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

References