Skip to main content

N8n CVE-2026-33722

| EUVDEUVD-2026-15953 HIGH
Incorrect Authorization (CWE-863)
2026-03-25 GitHub_M GHSA-fxcw-h3qj-8m8p
7.3
CVSS 4.0 · GitHub Advisory
View

Attack ChainAIDerived

Hypothetical attack flow derived from CVE metadata – not a confirmed exploit chain

  1. Access
    Authenticate as unprivileged user
  2. Exploit
    Reference external secret by name in credential
  3. Execution
    Bypass externalSecret:list permission check
  4. Impact
    Retrieve plaintext secret value from vault

Vulnerability Assessment

Weakness
CWE
OWASP Top 10:2025
A01:2025 - Broken Access Control
ASVS 5.0
V8 - Authorization Authorization logic validation
MITRE ATT&CK

1 technique across 1 tactic: Privilege Escalation

The technique list with ATT&CK links and the kill-chain view is part of the Basic plan and up.

Exploitation Conditions

Requires n8n versions prior to 2.6.4 or 1.123.23 with external secrets vault configured. Attacker needs valid n8n user credentials (any authenticated user), knowledge or ability to guess target secret name, and ability to save/edit credentials. No victim interaction needed.

Impact

The CVSS v4.0 score of 7.3 reflects high confidentiality impact with network attack vector, low complexity, and low privileges required, though attack requires present conditions (AT:P) indicating the need for external vault configuration and knowledge of secret names. The vulnerability enables privilege escalation from authenticated users to accessing admin-level secrets, presenting genuine risk in multi-tenant or role-separated environments. The CVSS vector shows high subsequent system confidentiality, integrity, and availability impacts (SC:H/SI:H/SA:H), indicating potential for broader compromise beyond the vulnerable component itself. Real-world risk is moderate to high for organizations using n8n with external vault integration, as authenticated insider threats or compromised low-privilege accounts could harvest sensitive credentials. The requirement for vault configuration and secret name knowledge reduces attack surface compared to unauthenticated or zero-knowledge exploits, but the low attack complexity (AC:L) means exploitation is straightforward once prerequisites are met.

Exploit ScenarioDerived

An authenticated user with limited privileges in an n8n instance with Hashicorp Vault integration creates or modifies a workflow credential configuration, intentionally referencing external secret names obtained through social engineering or systematic enumeration of common naming patterns like 'database_password' or 'api_key_prod'. When saving the credential, the system bypasses the externalSecret:list permission check and retrieves the plaintext secret value from the vault, allowing the low-privilege user to exfiltrate sensitive credentials normally restricted to administrators or owners for use in unauthorized activities or lateral movement.

This Week Schedule remediation this week. Why: HIGH severity (CVSS 7.0-8.9).
Patch available 0.0% exploitation probability (EPSS)

Get an e-mail when this CVE is exploited, patched or re-scored. Free account.

Alert me

AnalysisAIv1 – Mar 25, 2026

Authenticated users in n8n versions prior to 1.123.23 and 2.6.4 can bypass external secrets permission checks to retrieve plaintext secret values from configured vaults by referencing secrets by name in credentials, even without list permissions. This allows unauthorized access to sensitive vault-stored credentials without requiring admin or owner privileges, provided the attacker knows or can guess the target secret name. Public exploit code exists for this vulnerability.

Earlier versions of this analysis (1)
v1 Mar 25, 2026 - 18:32 CVSS 7.3

An improper authorization vulnerability in n8n workflow automation platform allows authenticated users without proper permissions to retrieve plaintext secrets from external vaults by referencing secret names in credential configurations. This bypasses the externalSecret:list permission check, enabling unauthorized access to sensitive vault secrets without requiring admin or owner privileges. The vulnerability affects n8n versions prior to 1.123.23 and 2.6.4, requires an external secrets vault to be configured, and the attacker must know or guess the target secret name.

RemediationAI

Upgrade n8n to version 1.123.23 or later for the legacy branch, or version 2.6.4 or later for the current branch to fully remediate the vulnerability. Patches are available through the official GitHub repository and detailed in the security advisory at https://github.com/n8n-io/n8n/security/advisories/GHSA-fxcw-h3qj-8m8p. If immediate patching is not feasible, administrators should implement temporary mitigations including restricting n8n instance access to fully trusted users only through authentication controls or network segmentation, and disabling external secrets vault integration until the patch can be applied. Note that these workarounds provide only partial risk reduction and should be considered short-term measures only, as they do not address the underlying authorization flaw.

Affected VersionsENISA

n8n 2.0.0-rc.0, < 2.6.4
n8n < 1.123.23

Affected Packages

npm n8n fix: 1.123.23, 2.6.4
euvd n8n_2_0_0_rc_0 fix: 2.6.4

Source: OSV (Open Source Vulnerabilities)

Affects your stack

Affects 2 packages in npm, euvd

Checking this CVE against your own stacks and servers is part of the Basic plan and up.

Technical ContextAI · show details

n8n is an open-source workflow automation platform identified by CPE cpe:2.3:a:n8n-io:n8n. The vulnerability is classified as CWE-863 (Incorrect Authorization), meaning the application fails to properly enforce authorization checks when users attempt to access external secrets. The issue stems from inadequate permission validation in the credential saving workflow, where the system checks for externalSecret:list permission but allows authenticated users to bypass this control by directly referencing external secret names during credential creation or modification. The Hashicorp tag suggests integration with Hashicorp Vault or similar external secrets management systems, where the application retrieves secrets but fails to validate whether the requesting user has appropriate access rights before returning plaintext values.

Know when N8n gets its next vulnerability

  • Watch products and get an email when something new is published
  • Check this CVE against your own stack and servers
  • Exploit and PoC references, threat intelligence from 22 sources

No credit card · 7-day full trial

Severity by source

GitHub Advisory PRIMARY 7.3 HIGH
CVSS:4.0/AV:N/AC:L/AT:P/PR:L/UI:N/VC:H/VI:N/VA:N/SC:H/SI:H/SA:H

Primary rating from GitHub Advisory · only source for this CVE.

CVSS VectorGitHub Advisory

Attack Vector
Network
Attack Complexity
Low
Attack Requirements
Present
Privileges Required
Low
User Interaction
None
Vulnerable system: Confidentiality
High
Vulnerable system: Integrity
None
Vulnerable system: Availability
None
Subsequent system: Confidentiality
High
Subsequent system: Integrity
High
Subsequent system: Availability
High

Lifecycle Timeline

3
Patch released
Mar 31, 2026 - 21:13 nvd
Patch available
PoC Detected
Mar 27, 2026 - 19:34 vuln.today
Public exploit code
CVE Published
Mar 25, 2026 - 18:09 nvd
HIGH 7.3

DescriptionGitHub Advisory

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.

Executive ViewAI

Why It Matters

A HIGH severity vulnerability in n8n workflow automation allows authenticated employees to illegally access sensitive secrets stored in external vaults, potentially exposing API keys, database credentials, and other critical authentication materials. Organizations using n8n with external vault integrations face immediate risk of credential theft and downstream system compromise if attackers gain user access.

Business Impact: High
Compensating Controls

Disable external secrets vault integration temporarily if operationally feasible; implement network-level restrictions limiting n8n's access to vault systems; enforce IP whitelisting between n8n and vault; monitor and log all vault access attempts for anomaly detection; restrict n8n user account permissions to minimum required roles; consider WAF rules blocking requests to vault endpoints from unexpected sources; rotate all secrets currently referenced in n8n configurations.

Threat Intelligence Overview

EPSS Score
0.0%
Top 98% exploitable
Exploit
POC
Public exploit code exists
Data Quality
6 sources
Confidence: High
EUVD NVD CVE.org EPSS Vulnrichment GitHub VulDB

How this decision was reached

The engine reads each signal below and applies a fixed list of rules from top to bottom. The first rule that matches sets the recommended action – like a statement, every line is shown.

SignalValue
Severity HIGH
CISA KEV No
Public POC Yes
EPSS 0.0%
Patch available Yes
Active threat No
Deciding rule
HIGH severity (CVSS 7.0-8.9)
What every action level means
Emergency Immediate action required. Criteria: CRITICAL + in CISA KEV (actively exploited) without patch, OR CRITICAL + EPSS > 30% without patch, OR CRITICAL + active threat signals without patch.
Act Now Prioritize within 24-48h. Criteria: in KEV with patch available, OR CRITICAL + public POC, OR HIGH + EPSS > 10%, OR CRITICAL + active threat, OR any CRITICAL severity.
This Week Schedule remediation this week. Criteria: HIGH severity (CVSS 7.0-8.9). Patch within normal change window.
This Month Plan within 30 days. Criteria: MEDIUM severity (CVSS 4.0-6.9), lower exploitation probability. Include in regular patch cycle.
Monitor Track and reassess. Criteria: LOW severity (CVSS 0.1-3.9), minimal exploitation risk. No immediate action needed.

SSVC AssessmentENISA

SSVC Decision
Scheduled
Exploitation
None
System Exposure· derived
Open
Automatable
No
Human Impact
High
Technical Impact
Partial

Priority Score

56
Low Medium High Critical
KEV: 0
EPSS: 0
CVSS: +36
PoC: +20
Weaponized: 0
Threat intel: 0
Gov advisory: 0

Attack Technique

Authentication bypass attacks exploit flaws in the verification mechanisms that control access to systems and applications.

Related Vulnerabilities in n8n Workflow Automation Multiple Vulnerabilities

View all 2

More in N8n

View all
CVE-2025-68613 HIGH POC
8.8 Dec 19

Remote code execution in n8n's workflow expression evaluation system allows an authenticated user with workflow creation

CVE-2026-21877 CRITICAL POC
9.9 Jan 08

n8n workflow automation (through 1.121.2) allows authenticated users to execute arbitrary code via the n8n service, with

CVE-2026-21858 CRITICAL POC
10.0 Jan 08

n8n workflow automation (1.65.0 to 1.121.0) allows unauthenticated file access through form-based workflows. A critical

CVE-2026-1470 CRITICAL POC
9.9 Jan 27

n8n has a fifth critical RCE vulnerability (CVSS 9.9) in the Expression evaluator, enabling code execution through craft

CVE-2025-65964 CRITICAL POC
9.4 Dec 09

Authenticated users who can create or modify an n8n workflow can achieve remote code execution on the n8n host by abusin

CVE-2026-33696 CRITICAL POC
9.4 Mar 25

A prototype pollution vulnerability in the XML and GSuiteAdmin nodes of n8n workflow automation platform allows authenti

CVE-2026-33660 CRITICAL POC
9.4 Mar 25

An authenticated user with workflow creation or modification privileges in n8n workflow automation platform can exploit

CVE-2025-55526 CRITICAL POC
9.1 Aug 26

n8n-workflows Main Commit ee25413 allows attackers to execute a directory traversal via the download_workflow function w

CVE-2026-33665 HIGH POC
8.8 Mar 25

Authenticated n8n users can hijack administrator accounts when LDAP authentication is enabled by manipulating their LDAP

CVE-2023-27563 HIGH POC
8.8 May 10

The n8n package 0.218.0 for Node.js allows Escalation of Privileges. Rated high severity (CVSS 8.8), this vulnerability

CVE-2026-33713 HIGH POC
8.7 Mar 25

SQL injection in n8n's Data Table Get node allows authenticated users with workflow modification permissions to execute

CVE-2026-0863 HIGH POC
8.5 Jan 18

Authenticated users can exploit string formatting and exception handling in n8n's Python task executor to escape sandbox

This site uses cookies essential for authentication and security. No tracking or analytics cookies are used. Privacy Policy