Skip to content
n8nGHSA-7hgx-277f-7vmg

n8n: Agent Workflow Tool Bypasses Sub-Workflow Caller Policy

MediumCVE-2026-86996 · Published Sep 8, 2026

## 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 it returned. The patch applies the sub-workflow caller policy on the Agent tool path. ## Patches The issue has been fixed in n8n versions 2.37.7 and 2.38.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 n8n instance access to fully trusted users only. - Audit workflows attached as Agent tools and review their caller policy settings. - Remove sensitive workflows from Agent tool configurations until the instance is patched. These workarounds do not fully remediate the risk and should only be used as short-term mitigation measures.

GitHub advisory

Affected versions

PackageAffectedFixed in
n8n
npm
>= 2.38.0, < 2.38.22.38.2
< 2.37.72.37.7
Details and references
CVSS 4.0
CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:L/VI:L/VA:N/SC:L/SI:L/SA:N
Severity from
GitHub (reviewed advisory)
Weakness
CWE-862
Also known as
CVE-2026-86996

More n8n advisories

All n8n

Critical advisories by email

Wednesdays: the week’s critical and high advisories in the AI and data stack, with the fixed versions. Only in weeks that have some.

Double opt-in. Unsubscribe any time.