CVE-2026-65594: n8n incorrect authorization in OAuth 2.1 flow for MCP Server Triggers

CVE-2026-65594 · Severity: medium · CVSS 4 · Published 2026-07-22

n8n is a workflow automation platform used to connect different business applications. A security flaw allows users with low-level access to bypass authorization checks and execute automated tasks belonging to other users, including administrators. This could allow an attacker to access sensitive data from connected integrations or perform actions using another user's high-level credentials without their knowledge.

Technologies: N8n, n8n (npm). Vendors: N8n, npm.

Quick answers

Is CVE-2026-65594 exploited in the wild?
No. Junglewise Threat Intelligence has no report of CVE-2026-65594 being exploited in the wild.
How severe is CVE-2026-65594?
Medium severity, with a CVSS score of 4, published 22 July 2026.
Which products and versions are affected?
N8n >= 2.27.0, < 2.29.8; >= 2.30.0, < 2.30.1, >= 2.27.0, < 2.29.8; 2.30.x < 2.30.1; n8n (npm) SEMVER:introduced=2.30.0,fixed=2.30.1.
Is there a fix for CVE-2026-65594?
Yes. n8n (npm): upgrade to 2.30.1 or later. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
How is CVE-2026-65594 attacked?
It is attacked over the network, in a network appliance.
Am I affected by CVE-2026-65594?
Check whether you run N8n or n8n (npm) at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.

How to fix

  • n8n (npm): upgrade to 2.30.1 or later
    npm install n8n@2.30.1

Technical details

An incorrect authorization vulnerability (CWE-863) exists in n8n's OAuth 2.1 consent and token-issuance flow. The system fails to verify if an authenticated user has permission to access the specific workflow requested as an OAuth resource. A member-level attacker can register an OAuth client and self-approve consent for another user's 'n8n OAuth2'-protected MCP Server Trigger workflow. This allows the attacker to obtain a valid token and execute the workflow within the victim's project context, utilizing the victim's stored credentials and accessing their connected integration data. The issue is fixed in versions 2.29.8 and 2.30.1.

Affected products

  • n8n-io n8n >= 2.27.0, < 2.29.8; >= 2.30.0, < 2.30.1

Identifiers

  • CVE-2026-65594
  • GHSA-q5xf-xhwf-cwqf

Timeline

  • 2026-07-08: disclosed: Initial disclosure by n8n-io
  • 2026-07-22: advisory: GitHub Advisory published and CVE assigned

References

This page as Markdown. Free to reuse under CC BY 4.0 with a link back.