High (AgentArmorHQ estimate)Prompt injection

n8n: AI Agents Project Viewer Privilege Escalation via run_node_tool

Product
n8n
CVE
CVE-2026-65015
Affected
n8n (< 2.29.8) and n8n (>= 2.30.0, < 2.30.1)
Fixed in
2.29.8

Last verified against sources: October 26, 2026

Am I affected?

n8n: affected n8n (< 2.29.8) and n8n (>= 2.30.0, < 2.30.1). Fixed in 2.29.8.

  • Check your version: run npm ls n8n. Versions >= 2.30.0, < 2.30.1 of n8n are affected. [1]

What to do now

  1. Upgrade to the fixed version: run npm install n8n@2.30.1 (first patched version 2.30.1). [1]
  2. Upgrade to n8n 2.29.8 or 2.30.1 or later to remediate the vulnerability. [1]
  3. Disable the AI Agents module by removing agents from the N8N_ENABLED_MODULES environment variable. [1]
  4. 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. [1]
  5. Disable command-execution nodes (e.g. Execute Command, SSH) if they have been re-enabled, to limit the potential impact. [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.

Discuss this incident

What happened

  • 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. [1]
  • 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. [1]
  • Users of the AI Agents feature who share team projects with lower-privileged members are affected. [1]

Impact

  • 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. [1]
  • 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. [1]

What was done

  • The issue has been fixed in n8n versions 2.29.8 and 2.30.1. [1]
  • Users should upgrade to one of these versions or later to remediate the vulnerability. [1]

Sources

  1. GHSA-x5vx-c2c8-m3w9 — 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.

Brief
[CVE-2026-65015] n8n: AI Agents Project Viewer Privilege Escalation via run_node_tool
Product: n8n | Affected: n8n (< 2.29.8) and n8n (>= 2.30.0, < 2.30.1) | Fixed in: 2.29.8
Summary: 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.
Source & remediation on AgentArmorHQ: https://agentarmorhq.com/incidents/2026/07/cve-2026-65015-n8n
Was this page useful?

Corrections

Report an error or request a correction. We review requests within 5 business days and add a dated correction note.

10 to 2,000 characters. A link to a source helps. Stored as plain text.

Discussions for CVE-2026-65015

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.

Check before you install

Paste a package name or a GitHub link and get a clear answer in seconds: Block, Review or No known issues. No account needed.

Check a package

Questions? Contact us