n8n Has External Secrets Authorization Bypass in Credential Saving

中 5.3CVE-2026-33722 · GHSA-fxcw-h3qj-8m8p · 25/03/2026 公開 · 17/06/2026 更新

要点

CVE-2026-33722 は n8n (n8n), n8n に影響する深刻度「中」 (CVSS 5.3) の脆弱性です。
今後30日間に悪用される確率（EPSS）：0.27%（全脆弱性の 18.4% より高い）。
対処：2.6.4, 1.123.23 以降に更新してください。

パッケージ	影響を受けるバージョン	修正済みバージョン
n8n n8n	`≥ 2.0.0, < 2.6.4< 1.123.23`	`2.6.41.123.23`
n8n npm	`≥ 2.0.0-rc.0, < 2.6.4< 1.123.23`	`2.6.41.123.23`

概要

Impact

An authenticated user without permission to list external secrets could reference a secret by the external name in a credential and retrieve its plaintext value when saving the credential. This bypassed the externalSecret:list permission check and allowed access to secrets stored in connected vaults without admin or owner privileges.

This issue requires the instance to have an external secrets vault configured.
The attacker must know or be able to guess the name of a target secret.

Patches

The issue has been fixed in n8n versions 1.123.23 and 2.6.4. 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 access to fully trusted users only.
Disable external secrets integration until the patch can be applied.

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 versions 2.6.4 and 1.123.23, an authenticated user without permission to list external secrets could reference a secret by the external name in a credential and retrieve its plaintext value when saving the credential. This bypassed the `externalSecret:list` permission check and allowed access to secrets stored in connected vaults without admin or owner privileges. This issue requires the instance to have an external secrets vault configured. The attacker must know or be able to guess the name of a target secret. The issue has been fixed in n8n versions 1.123.23 and 2.6.4. Users should upgrade to one of these versions or later to remediate the vulnerability. If upgrading is not immediately possible, administrators should consider the following temporary mitigations: Restrict n8n access to fully trusted users only, and/or disable external secrets integration until the patch can be applied. These workarounds do not fully remediate the risk and should only be used as short-term mitigation measures.