CVE-2026-103252: n8n: authz bypass in credential test leaks variables
HIGHn8n's credential test endpoint resolves project-scoped variables for any project ID the caller supplies, without checking that the caller has access to that project. An authenticated low-privilege user can therefore point a credential test at a host they control and receive other projects' sensitive variables, such as API keys and secrets that AI agent workflows often hold. The CVSS is 7.7 with a changed scope, meaning confidentiality impact extends beyond the attacker's own project. Exploitation likelihood is currently low to moderate: EPSS is 0.27% (top 82% percentile), the CVE is not in CISA KEV, no public exploit or Nuclei template exists, and CISA SSVC says TRACK. Upgrade to n8n 1.123.80, 2.39.6 or 2.40.1 or later. Until you can, restrict who can create or test credentials, and review project variables for secrets that need rotation.
What is the risk?
Medium-high. The attack is network-reachable, low complexity, needs no user interaction and needs only a low-privilege authenticated account. The scope change and high confidentiality impact (C:H) make multi-tenant and multi-project n8n instances the most exposed. Exploitation likelihood is low for now (no public PoC, not in KEV, EPSS 0.27%), but the technique is simple once the advisory details are known. Integrity and availability are not affected.
How does the attack unfold?
What systems are affected?
| Package | Ecosystem | Vulnerable Range | Patched |
|---|---|---|---|
| n8n | npm | — | No patch |
Do you use n8n? You're affected.
How severe is it?
What is the attack surface?
What should I do?
1 step1) Upgrade to n8n 1.123.80, 2.39.6 or 2.40.1 or later. 2) Until patched, limit credential creation and testing to trusted users, and restrict access to the credential test endpoint where possible. 3) Block unneeded egress from the n8n host to unapproved destinations with an allowlist. 4) Rotate any secrets stored in project variables if untrusted users had access. 5) Review reverse proxy and application logs for credential test requests with unexpected project IDs or unusual external hosts. 6) Keep secrets in a dedicated secret manager instead of plain project variables where possible.
What does CISA's SSVC say?
Source: CISA Vulnrichment (SSVC v2.0). Decision based on the CISA Coordinator decision tree.
How is it classified?
Which compliance frameworks are affected?
This CVE is relevant to:
Frequently Asked Questions
What is CVE-2026-103252?
n8n's credential test endpoint resolves project-scoped variables for any project ID the caller supplies, without checking that the caller has access to that project. An authenticated low-privilege user can therefore point a credential test at a host they control and receive other projects' sensitive variables, such as API keys and secrets that AI agent workflows often hold. The CVSS is 7.7 with a changed scope, meaning confidentiality impact extends beyond the attacker's own project. Exploitation likelihood is currently low to moderate: EPSS is 0.27% (top 82% percentile), the CVE is not in CISA KEV, no public exploit or Nuclei template exists, and CISA SSVC says TRACK. Upgrade to n8n 1.123.80, 2.39.6 or 2.40.1 or later. Until you can, restrict who can create or test credentials, and review project variables for secrets that need rotation.
Is CVE-2026-103252 actively exploited?
No confirmed active exploitation of CVE-2026-103252 has been reported, but organizations should still patch proactively.
How to fix CVE-2026-103252?
1) Upgrade to n8n 1.123.80, 2.39.6 or 2.40.1 or later. 2) Until patched, limit credential creation and testing to trusted users, and restrict access to the credential test endpoint where possible. 3) Block unneeded egress from the n8n host to unapproved destinations with an allowlist. 4) Rotate any secrets stored in project variables if untrusted users had access. 5) Review reverse proxy and application logs for credential test requests with unexpected project IDs or unusual external hosts. 6) Keep secrets in a dedicated secret manager instead of plain project variables where possible.
What systems are affected by CVE-2026-103252?
This vulnerability affects the following AI/ML architecture patterns: agent frameworks, workflow automation, LLM orchestration pipelines, multi-tenant AI platforms.
What is the CVSS score for CVE-2026-103252?
CVE-2026-103252 has a CVSS v3.1 base score of 7.7 (HIGH). The EPSS exploitation probability is 0.27%.
What is the AI security impact?
Affected AI Architectures
MITRE ATLAS Techniques
AML.T0012Valid AccountsAML.T0025Exfiltration via Cyber MeansAML.T0083Credentials from AI Agent ConfigurationAML.T0098AI Agent Tool Credential HarvestingCompliance Controls Affected
What are the technical details?
Original Advisory
n8n versions before 1.123.80, from 2.0.0 before 2.39.6, and from 2.40.0 before 2.40.1 contain an authorization bypass vulnerability in the credential test endpoint that resolves project-scoped variables without validating caller access. Attackers can specify an arbitrary project ID in the request body to interpolate sensitive variables into credential test requests sent to attacker-controlled hosts for exfiltration.
Exploitation Scenario
An attacker with a low-privilege account on a shared n8n instance, such as a contractor or a compromised user, finds or guesses the project ID of a team that runs AI agent workflows. They send a credential test request that sets that project ID in the body and sets the target host to a server they control. n8n interpolates the victim project's variables, such as an OpenAI API key or a vector database token, into the outgoing test request. The attacker's server receives the secrets and uses them to access the LLM provider account or the connected data stores.
Weaknesses (CWE)
CWE-639Authorization Bypass Through User-Controlled KeyPrimaryCWE-639Authorization Bypass Through User-Controlled KeyCWE-639 — Authorization Bypass Through User-Controlled Key: The system's authorization functionality does not prevent one user from gaining access to another user's data or record by modifying the key value identifying the data.
- [Architecture and Design] For each and every data access, ensure that the user has sufficient privilege to access the record that is being requested.
- [Architecture and Design, Implementation] Make sure that the key that is used in the lookup of a specific user's record is not controllable externally by the user or that any tampering can be detected.
Source: MITRE CWE corpus.
CVSS Vector
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:H/I:N/A:NReferences
Timeline
Related Vulnerabilities
CVE-2026-3366310.0n8n: member role steals plaintext HTTP credentials
Same package: n8nCVE-2026-3366010.0TensorFlow: type confusion NPD in tensor conversion
Same package: n8nCVE-2026-2185810.0n8n: Input Validation flaw enables exploitation
Same package: n8nCVE-2026-275779.9n8n: Code Injection enables RCE
Same package: n8nCVE-2026-274949.9n8n: security flaw enables exploitation
Same package: n8n