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.
CVE-2026-65594
This medium-severity CVE scores 5.1 under a secondary CVSS source (NVD's own analysis pending). EPSS exploit-prediction score not yet available (the EPSS model rescores nightly; freshly-published CVEs typically appear within 48 hours). GitHub Security Advisory data not yet ingested — confidence will rise once GHSA publishes (typical lag: hours to days for open-source ecosystem CVEs; never for infrastructure-only CVEs).
- Lower severity and no public exploit yet
No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.
- CVSS v3
- 5.1
- EG Score
- 5.1(low)
- EPSS
- —
- KEV
- Not listed
Published
July 22, 2026
Last Modified
July 22, 2026
Advisory Details (2)
Auto-updated Jul 22, 2026n8n before 2.30.1 Missing OAuth Authorization Check | Advisories | VulnCheck
https://www.vulncheck.com/advisories/n8n-before-missing-oauth-authorization-checkMember-Level Users Can Execute Other Users' MCP Server Trigger Workflows via Missing OAuth Authorization Check · Advisory · n8n-io/n8n · GitHub
https://github.com/n8n-io/n8n/security/advisories/GHSA-q5xf-xhwf-cwqfVendor Advisories for CVE-2026-65594(1)
These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.
Weakness Classification(1)
MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.
Data Freshness Timeline
(refreshed 4× in last 7d / 4× in last 30d)
Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. Most recent first.
- 2026-07-22 13:35 UTCEG score recompute
- 2026-07-22 13:35 UTCGHSA enrichment
- 2026-07-22 11:32 UTCEG score recompute
- 2026-07-22 11:32 UTCMITRE cvelistV5first tracked
Related CVEs(same CWE)
Same CWE
10 shownCWE-863
Frequently asked(4)
What is CVE-2026-65594?
When was CVE-2026-65594 disclosed?
What is the CVSS score of CVE-2026-65594?
How do I remediate CVE-2026-65594?
Dependency Blast Radius
Explore the affected products and dependency analysis for CVE-2026-65594
Is Your Infrastructure Affected by CVE-2026-65594?
EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.