要点
- CVE-2026-86996 は n8n (n8n), n8n に影響する深刻度「中」 (CVSS 5.4) の脆弱性です。
- 今後30日間に悪用される確率（EPSS）：0.29%（全脆弱性の 22.1% より高い）。
- 対処：2.38.2, 2.37.7 以降に更新してください。
| パッケージ | 影響を受けるバージョン | 修正済みバージョン |
|---|
| n8n | ≥ 2.38.0, < 2.38.2< 2.37.7
| 2.38.22.37.7
|
| n8n npm | ≥ 2.38.0, < 2.38.2< 2.37.7
| 2.38.22.37.7
|
概要
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.
NVD の説明
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 workflow and read its returned data. The affected path is packages/cli/src/modules/agents/tools/workflow-tool-factory.ts, where executeWorkflow omitted SubworkflowPolicyChecker.checkForProject. This issue is fixed in versions 2.37.7 and 2.38.2.
これらの製品をお使いですか？サイトをスキャンして、脆弱なバージョンが公開されていないか確認しましょう。
無料でサイトをスキャン