Incorrect Authorization Affecting n8n package, versions <2.29.8-r0


Severity

Recommended
0.0
medium
0
10

Snyk's Security Team recommends NVD's CVSS assessment. Learn more

Threat Intelligence

EPSS
0.27% (19th percentile)

Do your applications use this vulnerable package?

In a few clicks we can analyze your entire application and see what components are vulnerable in your application, and suggest you quick fixes.

Test your applications
  • Snyk IDSNYK-MINIMOSLATEST-N8N-18280610
  • published24 Jul 2026
  • disclosed22 Jul 2026

Introduced: 22 Jul 2026

NewCVE-2026-65594  (opens in a new tab)
CWE-863  (opens in a new tab)

How to fix?

Upgrade Minimos:latest n8n to version 2.29.8-r0 or higher.

NVD Description

Note: Versions mentioned in the description apply only to the upstream n8n package and not the n8n package as distributed by Minimos. See How to fix? for Minimos:latest relevant fixed versions and status.

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 Base Scores

version 3.1