Answer in brief
CVE-2026-65594 records a Medium severity (CVSS 5.1) vulnerability in n8n before 2.30.1 Missing OAuth Authorization Check. The current sources do not mark it as known exploited. The current feed maps n8n-io/n8n (generic), n8n-io/n8n (generic). Check affected ranges and fixed versions before updating.
Analysis pending evidence review
HOL Guard separates source facts from reviewed analysis. See the methodology.
CVSS is 5.1. The current sources do not mark it as known exploited. Treat this as a source-backed prioritization signal, not a statement about your environment.
Analysis status
Analysis pending evidence review
Factual feed record only; HOL analysis is not approved for indexing. Read the methodology.
The current feed maps n8n-io/n8n (generic), n8n-io/n8n (generic). Check affected ranges and fixed versions before updating.
| Product | Affected versions | Fixed versions |
|---|---|---|
| cpe:2.3:a:n8n:n8n:2.30.0:*:*:*:community:node.js:*:* | Not reported | Not reported |
| cpe:2.3:a:n8n:n8n:2.30.0:*:*:*:enterprise:node.js:*:* | Not reported | Not reported |
| cpe:2.3:a:n8n:n8n:*:*:*:*:community:node.js:*:* | Not reported | Not reported |
| cpe:2.3:a:n8n:n8n:*:*:*:*:enterprise:node.js:*:* | Not reported | Not reported |
| Package | Affected range | Fixed version |
|---|---|---|
| n8n-io/n8ngeneric | >=2.30.0 <2.30.1 | 2.30.1 |
| n8n-io/n8ngeneric | >=0 <2.29.8 | 2.29.8 |
Published upstream
Jul 22, 2026
Evidence: source:cvelist:source_dates:source-dates:recordSource modified
Oct 29, 2026
Evidence: source:cvelist:source_dates:source-dates:recordFirst seen by HOL
Oct 28, 2026
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.
Quoted source text, attributed separately from HOL analysis.