Signal is active with 2 mentions in latest observed window
Recommended action window: Monitor and triage in normal cycle
NVD description
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.
Priority
LOW
Exploitation
NONE
PoC
NONE
Patch
AVAILABLE
Momentum
NONE
If you run products in this scope, you should treat this CVE as relevant to your environment.
CVE-2026-33722 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 refe… https://www.cve.org/CVERecord?id=CVE-2026-33722
Post summary
The post announces CVE-2026-33722, describing an authenticated privilege escalation issue in n8n and noting that patch versions exist, but it lacks PoC, exploit code, or evidence of active misuse.
CVE-2026-33722 highlights a permissions issue in older n8n versions. I've seen similar scenarios where unauthorized personnel access sensitive data due to inadequate permission settings. Did you know that n8n's workflow automation capabilities can be leveraged to automatically revoke or update user permissions upon login? This would prevent unauthorized access and reduce the risk of security breaches. I've built a custom n8n workflow that does just this, if you're interested in taking a look.
Post summary
The post highlights a permissions issue tied to CVE‑2026‑33722 in older n8n versions and offers a general workflow suggestion to mitigate unauthorized access, but provides no concrete technical evidence or exploitation details.
1 of 1 entries
| Part | Vendor | Product | Version | Target SW | Target HW |
|---|---|---|---|---|---|
| App | n8n | n8n | - | node.js | - |