n8n: Wrong OAuth Scope on Evaluation Test Runs Endpoints
- Product
- n8n
- Affected
- npm/n8n < 1.123.55; npm/n8n >= 2.0.0-rc.0, < 2.25.7; npm/n8n >= 2.26.0, < 2.26.2
- Fixed in
- 1.123.55
Last verified against sources: October 26, 2026
Am I affected?
n8n: affected npm/n8n < 1.123.55; npm/n8n >= 2.0.0-rc.0, < 2.25.7; npm/n8n >= 2.26.0, < 2.26.2. Fixed in 1.123.55.
- Check your version: run
npm ls n8n. Versions < 1.123.55 of n8n are affected. [1]
What to do now
- Upgrade to the fixed version: run
npm install n8n@1.123.55(first patched version 1.123.55). [1] - Upgrade to one of these versions or later to remediate the vulnerability. [1]
- Restrict project membership to fully trusted users only. [1]
- Avoid granting viewer access to projects containing sensitive workflows. [1]
General practice, not from the source: if the affected software could read tokens or credentials, rotate them after upgrading; pin versions and review changes before updating tools your agents run.
What happened
- Three mutating endpoints in the evaluation test runs controller authorized state-changing actions using
workflow:readinstead of the action-appropriateworkflow:executescope. [1] - This issue only affects instances with Advanced Permissions (Enterprise/Cloud) where projects and viewer roles are in use. [1]
Impact
- An authenticated user with
project:viewerrole on a project could start new evaluation test runs, cancel in-flight runs, and delete run records for workflows they only had read access to. [1]
What was done
Sources
- GHSA-664h-gpgq-h6xx — GitHub Advisory Database
Every statement above was checked against these sources before publishing. Spotted an error? Tell us and we will correct it with a dated note.
Share advisory brief with your team
Copy a plain-text summary for Slack, GitHub issues, or team security channels.
n8n: Wrong OAuth Scope on Evaluation Test Runs Endpoints
Product: n8n | Affected: npm/n8n < 1.123.55; npm/n8n >= 2.0.0-rc.0, < 2.25.7; npm/n8n >= 2.26.0, < 2.26.2 | Fixed in: 1.123.55
Summary: Three mutating endpoints in the evaluation test runs controller authorized state-changing actions using `workflow:read` instead of the action-appropriate `workflow:execute` scope.
Source & remediation on AgentArmorHQ: https://agentarmorhq.com/incidents/2026/06/ghsa-664h-gpgq-h6xx-n8nCorrections
Report an error or request a correction. We review requests within 5 business days and add a dated correction note.
Discussions for n8n
Ask questions or share configuration tips. Governed by our Community Rules & Terms.
No posts match this filter yet.
Be the first to ask a question or share a working tip.