Which versions of n8n are affected by EUVD-2026-38476?

n8n Enterprise deployments with Dynamic Credentials enabled are vulnerable to credential hijacking across tenant accounts, allowing authenticated users to steal OAuth tokens and compromise integrated…. A patch is available.

How to fix or mitigate EUVD-2026-38476?

Within 24 hours: Disable Dynamic Credentials if non-essential and audit access logs for suspicious activity. Within 7 days: Upgrade n8n Enterprise to the patched version per vendor advisory and rotate all stored OAuth credentials. Within 30 days: Perform comprehensive access review of credential modifications and implement enhanced logging for multi-tenant isolation.

n8n EUVD-2026-38476

Q: What is the CVSS score of EUVD-2026-38476?

EUVD-2026-38476 has a CVSS 4.0 base score of 8.9 (High). CVSS vector: CVSS:4.0/AV:N/AC:L/AT:P/PR:L/UI:N/VC:H/VI:H/VA:L/SC:H/SI:H/SA:L/E:X/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:X. EPSS exploitation probability: 0.3%.

| CVE-2026-54305 HIGH

Information Exposure (CWE-200)

2026-06-16 https://github.com/n8n-io/n8n

GHSA-2j5h-858j-5mpf

Information Disclosure

8.9

CVSS 4.0 · Vendor: https://github.com/n8n-io/n8n

Severity by source

Vendor (https://github.com/n8n-io/n8n) PRIMARY

8.9 HIGH

CVSS:4.0/AV:N/AC:L/AT:P/PR:L/UI:N/VC:H/VI:H/VA:L/SC:H/SI:H/SA:L/E:X/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:X

vuln.today AI

9.9 CRITICAL

Network-reachable EE endpoints exploitable by any authenticated user (PR:L), no UI; scope changes as victim's OAuth integrations on other systems are impacted; token revocation gives partial availability impact.

3.1 AV:N/AC:L/PR:L/UI:N/S:C/C:H/I:H/A:L

4.0 AV:N/AC:L/AT:P/PR:L/UI:N/VC:H/VI:H/VA:L/SC:H/SI:H/SA:L

Primary rating from Vendor (https://github.com/n8n-io/n8n).

CVSS VectorVendor: https://github.com/n8n-io/n8n

Attack Vector

Network

Attack Complexity

Low

Privileges Required

Low

User Interaction

None

Scope

Lifecycle Timeline

Analysis Updated

Jun 23, 2026 - 18:39 vuln.today

v3 (cvss_changed)

Analysis Updated

Jun 23, 2026 - 18:38 vuln.today

v2 (cvss_changed)

Re-analysis Queued

Jun 23, 2026 - 18:22 vuln.today

cvss_changed

CVSS changed

Jun 23, 2026 - 18:22 NVD

9.9 (HIGH) 8.9 (HIGH)

Source Code Evidence Fetched

Jun 17, 2026 - 00:13 vuln.today

Analysis Generated

Jun 17, 2026 - 00:13 vuln.today

DescriptionCVE.org

Impact

Three EE endpoints used by the Dynamic Credentials feature accepted any authenticated n8n session without performing per-resource ownership or scope checks on the target workflow or credential. An authenticated user with no project membership or credential sharing relationship could enumerate credential identifiers, names, and types referenced by any private workflow in the instance, initiate an OAuth authorization flow against another user's credential to overwrite its stored tokens with tokens bound to an account they control, or revoke another user's stored credential tokens entirely.

Workflows relying on a hijacked credential would subsequently execute under the attacker's OAuth identity, enabling data exfiltration to attacker-controlled external services and persistent takeover of integrations. Token revocation would break affected workflows.

This issue only affects Enterprise instances where the Dynamic Credentials feature is enabled.

Patches

The issue has been fixed in n8n versions 1.123.55, 2.25.7, and 2.26.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.
If the Dynamic Credentials feature is not actively required, disable it by unsetting N8N_ENV_FEAT_DYNAMIC_CREDENTIALS.

These workarounds do not fully remediate the risk and should only be used as short-term mitigation measures.

AnalysisAI

Cross-tenant credential takeover in n8n Enterprise allows any authenticated user to hijack OAuth credentials belonging to other tenants when the Dynamic Credentials feature is enabled. Three EE endpoints failed to enforce per-resource ownership checks, letting attackers enumerate credentials across private workflows, overwrite stored OAuth tokens with attacker-controlled tokens, or revoke victim tokens entirely. No public exploit identified at time of analysis, but the issue has a high CVSS 4.0 score of 8.9 and a vendor advisory confirms the flaw.

Technical ContextAI

n8n is a popular open-source workflow automation platform written in TypeScript/Node.js (distributed as the npm package n8n). The Dynamic Credentials feature in n8n Enterprise edition lets workflows resolve OAuth credentials at runtime through dedicated EE endpoints. Per the GHSA-2j5h-858j-5mpf advisory, three of these endpoints validated only that the requester held a valid n8n session, but skipped per-resource authorization checks against the target workflow or credential. This is a classic CWE-200 (Exposure of Sensitive Information to an Unauthorized Actor) combined with broken object-level authorization (BOLA-style) flaw: trusting the session as a proxy for resource ownership.

RemediationAI

Vendor-released patch: upgrade to n8n 1.123.55, 2.25.7, or 2.26.2 (or later) depending on the release line in use, as documented in GHSA-2j5h-858j-5mpf (https://github.com/n8n-io/n8n/security/advisories/GHSA-2j5h-858j-5mpf). If immediate upgrade is not feasible, disable the Dynamic Credentials feature by unsetting the N8N_ENV_FEAT_DYNAMIC_CREDENTIALS environment variable - this fully removes the vulnerable endpoints from the attack surface but breaks any workflow that depends on dynamic credential resolution at runtime. As a second-line mitigation, restrict instance access to fully trusted users only (e.g., via VPN, SSO with strict provisioning, or IP allowlisting) since any authenticated session is sufficient for exploitation; this reduces but does not eliminate insider risk. After patching, administrators should also rotate any OAuth credentials that may have been overwritten and audit recent workflow execution logs for unexpected integration calls.