MISFIRE

Browse / MCP and Tool Server Flaws / CVE-2026-65015

n8n: AI Agents Project Viewer Privilege Escalation via run_node_tool

CVE-2026-65015 ยท 2026-07-22 high

Class
MCP and Tool Server Flaws (filed by a model that read the source)
Technique
Authentication and access control
Also involves
Tool and Agent Misuse, Sensitive Data Disclosure
Affected
n8n (npm)
Gets past
Authorisation check
CVSS
CVSS:4.0/AV:N/AC:L/AT:P/PR:L/UI:N/VC:H/VI:L/VA:N/SC:H/SI:L/SA:L
EPSS
0.6% chance of exploitation in 30 days

How it works, in short

A read-only project user could chat with an agent whose node tool ran with project credentials, skipping execution and credential permission checks. (Our summary, written by a model. The source text is below.)

Details

Impact

In n8n's AI Agents feature, a user with the read-only Project Viewer role could escalate their privileges by chatting with an agent that has node tools enabled. The agent's node-execution tool was authorized only by the agent:execute scope and ran nodes using the project's credentials, without verifying that the requesting user was permitted to execute nodes or to access those credentials.

As a result, a Project Viewer could execute arbitrary tool nodes on the server and use credential secrets they were not authorized to read, gaining execution capabilities their role is intended to deny. On instances where a command- or file-capable tool node (such as Execute Command or SSH) is enabled, this could be extended to arbitrary command execution on the n8n host.

Users of the AI Agents feature who share team projects with lower-privileged members are affected.

Patches

The issue has been fixed in n8n versions 2.29.8 and 2.30.1. 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: - Disable the AI Agents module by removing agents from the N8N_ENABLED_MODULES environment variable. - Restrict project membership to fully trusted users only, and avoid granting Project Viewer access to untrusted users on projects containing agents with node tools enabled. - Disable command-execution nodes (e.g. Execute Command, SSH) if they have been re-enabled, to limit the potential impact.

These workarounds do not fully remediate the risk and should only be used as short-term mitigation measures.

References

Source: GitHub Advisory Database, used under CC BY 4.0.