n8n: Wrong OAuth Scope On Evaluations Test Run Creation Endpoint
n8n
- Severity
- High, CVSS 7.4
- CVSS vector
- CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:L/I:L/A:L
- Record
- GHSA-hv7x-3x78-gx53
- Affects
- n8n
- Known exploited
- Not listed in the CISA Known Exploited Vulnerabilities catalog
- Published
- Record first published by the source
- June 16, 2026
- Source last modified
- June 16, 2026
Description
Impact
The POST /workflows/{workflowId}/test-runs/new endpoint authorized access using workflow:read rather than workflow:execute. An authenticated user with read-only access to a workflow could trigger a real evaluation test run, causing the workflow to execute via the internal workflow runner. This could result in unintended outbound API calls, data mutations, or other side effects in downstream systems connected to the workflow.
This issue primarily affects instances where the Evaluations feature is in use and where users may have workflow:read access without workflow:execute access, such as deployments using RBAC project roles.
Patches
The issue has been fixed in n8n versions 1.123.55, 2.25.7, and 2.26.2. Users should upgrade to one of these versions or later to remediate the vulnerability.
Workarounds
If upgrading is not immediately possible, administrators should consider the following temporary mitigations:
- Restrict workflow access to fully trusted users only.
- Audit project role assignments and limit workflow:read access on sensitive workflows to users who should also be permitted to execute them.
These workarounds do not fully remediate the risk and should only be used as short-term mitigation measures.
Description quoted from the GitHub Advisory Database.
Who is affected
This flaw affects n8n, a tool for automating tasks by linking apps and online services into workflows. It mainly matters if your organization uses the Evaluations feature and some users can view a workflow but are not supposed to run it, for example when project roles give people different permissions. Such a signed-in user could start a real test run, which makes the workflow actually run. That could send unintended requests to other services, change data, or cause other side effects in systems the workflow connects to. This flaw is rated High.
What to do
- The person who installed or runs n8n for your organization should handle this. If an IT provider or vendor manages it for you, send them this advisory and ask when the update will be done.
- Update n8n to version
1.123.55,2.25.7or2.26.2, or any later version. - If you cannot update right away, restrict workflow access to fully trusted users only.
- Also audit project role assignments and limit
workflow:readaccess on sensitive workflows to users who should also be permitted to execute them. - These temporary steps do not fully remove the risk, so update as soon as you can.
Analysis written from the source record as of June 16, 2026 and reviewed before publishing.