CVE-2026-65594

MEDIUMPre-NVD 5.15.1
EchelonGraph scoreMEDIUM confidence

This medium-severity CVE scores 5.1 under a secondary CVSS source (NVD's own analysis pending). EPSS exploit probability: 0.3%, top 80% of all CVEs by exploit prediction. 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).

Triggered by: NVD CVSS baseline
Sources: epss, secondary
Trending — 4 sources updated this week
5.1EG
EchelonGraph verdictMonitorLow exploitation likelihood right now — keep watching.
  • Lower severity and no public exploit yet
CISA-KEV: Not listedEPSS PROB: 0%CVSS: 5.1Exploit: None knownExposed: 0

No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.

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.

CVSS v3
5.1
EG Score
5.1(medium)
EG Risk
23(Track)
EG Risk 23/100SSVC: Track

EG Risk is EchelonGraph's 0–100 priority score: it fuses intrinsic severity with real-world exploitation and automatability so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner. Distinct from the 0–10 EG Score (severity).

How it’s computed
Severity51% × 45%
Exploitation0% × 40%
Automatability0% × 15%
Action: Routine — remediate on your standard cadence.
EPSS PROB
0%
EPSS %ILE
20%
KEV
Not listed

Published

July 22, 2026

Last Modified

July 23, 2026

Advisory Details (2)

Auto-updated Jul 22, 2026
Patch available. Sources: github.
generic

n8n before 2.30.1 Missing OAuth Authorization Check | Advisories | VulnCheck

https://www.vulncheck.com/advisories/n8n-before-missing-oauth-authorization-check
github Patch Available

Member-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-cwqf

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

Affected Packages

(1 across 1 ecosystem)
npm(1)
PackageVulnerable rangeFixed inDependents
n8n2.29.8

Weakness Classification(1)

MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.

Data Freshness Timeline

(refreshed 27× in last 7d / 27× 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.

  1. 2026-07-27 14:14 UTCEPSS rescore
  2. 2026-07-27 01:09 UTCEG score recompute
  3. 2026-07-26 14:54 UTCEPSS rescore
  4. 2026-07-26 14:54 UTCEPSS rescore
  5. 2026-07-26 03:30 UTCEG score recompute
  6. 2026-07-25 14:18 UTCEPSS rescore
  7. 2026-07-25 14:18 UTCEPSS rescore
  8. 2026-07-24 14:18 UTCEPSS rescore
  9. 2026-07-24 14:18 UTCEPSS rescore
  10. 2026-07-23 14:18 UTCEPSS rescore
  11. 2026-07-23 14:18 UTCEPSS rescore
  12. 2026-07-23 03:22 UTCEG score recompute
  13. 2026-07-22 22:07 UTCEG score recompute
  14. 2026-07-22 22:07 UTCGHSA enrichment
  15. 2026-07-22 19:59 UTCGHSA enrichment
  16. 2026-07-22 19:52 UTCGHSA enrichment
  17. 2026-07-22 19:42 UTCGHSA enrichment
  18. 2026-07-22 19:40 UTCGHSA enrichment
  19. 2026-07-22 19:39 UTCGHSA enrichment
  20. 2026-07-22 19:32 UTCGHSA enrichment
  21. 2026-07-22 19:29 UTCGHSA enrichment
  22. 2026-07-22 19:26 UTCGHSA enrichment
  23. 2026-07-22 19:20 UTCGHSA enrichment
  24. 2026-07-22 13:35 UTCEG score recompute
  25. 2026-07-22 13:35 UTCGHSA enrichment
Show 2 more
  1. 2026-07-22 11:32 UTCEG score recompute
  2. 2026-07-22 11:32 UTCMITRE cvelistV5first tracked

Frequently asked(5)

What is CVE-2026-65594?
CVE-2026-65594 is a medium vulnerability published on July 22, 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…
When was CVE-2026-65594 disclosed?
CVE-2026-65594 was first published in the National Vulnerability Database on July 22, 2026, with the most recent update on July 23, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-65594 actively exploited?
CVE-2026-65594 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0% probability of exploitation in the next 30 days, which ranks it in the top 79.9% of all scored CVEs.
What is the CVSS score of CVE-2026-65594?
CVE-2026-65594 has a CVSS v3 base score of 5.1 (NVD).
How do I remediate CVE-2026-65594?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-65594, EchelonGraph cross-links them in the Vendor Advisories panel below — those typically contain the canonical remediation steps, fixed version numbers, and any vendor-specific mitigations.

Dependency Blast Radius

See which npm, PyPI, Go, and Maven packages are affected by CVE-2026-65594

Explore →

Is Your Infrastructure Affected by CVE-2026-65594?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.