NPM: n8n: Agent Workflow Tool Bypasses Sub-Workflow Caller Policy

NPM: n8n: Agent Workflow Tool Bypasses Sub-Workflow Caller Policy vulnerability discovered by ? in WordPress Npm n8n versions 2.37.7...

n8n: Agent Workflow Tool Bypasses Sub-Workflow Caller Policy

Impact A workflow's "This workflow can be called by" setting was enforced by the Execute Workflow node but was not consulted when the same workflow was attached to an Agent as a tool. A user who could build an Agent could therefore call a workflow that its owner had restricted, and read back what...

CVE-2026-86996

n8n (open-source workflow automation platform) is affected by a policy bypass in its Agent workflow tool . Prior to 2.37.7 and 2.38.2 , the "This workflow can be called by" setting was enforced by the Execute Workflow node but not when a workflow was attached to an Agent as a tool. The root cause...

CVE-2026-86996 n8n: Agent Workflow Tool Bypasses Sub-Workflow Caller Policy

n8n is an open source workflow automation platform. Prior to 2.37.7 and 2.38.2, the workflow setting named This workflow can be called by was enforced by the Execute Workflow node but not when a workflow was attached to an Agent as a tool. A user able to build an Agent could invoke a restricted...

CVE-2026-86996 n8n: Agent Workflow Tool Bypasses Sub-Workflow Caller Policy

n8n is an open source workflow automation platform. Prior to 2.37.7 and 2.38.2, the workflow setting named This workflow can be called by was enforced by the Execute Workflow node but not when a workflow was attached to an Agent as a tool. A user able to build an Agent could invoke a restricted...

CVE-2026-86996 n8n: Agent Workflow Tool Bypasses Sub-Workflow Caller Policy

n8n is an open source workflow automation platform. Prior to 2.37.7 and 2.38.2, the workflow setting named This workflow can be called by was enforced by the Execute Workflow node but not when a workflow was attached to an Agent as a tool. A user able to build an Agent could invoke a restricted...