CVE-2026-54305

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.

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.

CVE-2026-54305 has a CVSS score of 9.9 (High). The vector is network-reachable, low privileges required, and no user interaction. A CVSS score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether this affects your application depends on whether the vulnerable code is present and reachable in your environment. A fixed version is available (1.123.55, 2.26.2, 2.25.7); upgrading removes the vulnerable code path.

Kodem intelligence

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.

1. What is CVE-2026-54305? CVE-2026-54305 is a high-severity security vulnerability in n8n (npm), affecting versions < 1.123.55. It is fixed in 1.123.55, 2.26.2, 2.25.7.
2. How severe is CVE-2026-54305? CVE-2026-54305 has a CVSS score of 9.9 (High). This score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether it represents real risk in your environment depends on whether the vulnerable code is present and reachable.
3. Which versions of n8n are affected by CVE-2026-54305? n8n (npm) versions < 1.123.55 is affected.
4. Is there a fix for CVE-2026-54305? Yes. CVE-2026-54305 is fixed in 1.123.55, 2.26.2, 2.25.7. Upgrade to this version or later.
5. Is CVE-2026-54305 exploitable, and should I be worried? Whether CVE-2026-54305 is exploitable in your environment depends on whether the vulnerable code is present and reachable. A CVSS score is a worst-case rating; it does not account for your specific deployment, configuration, or usage patterns. Kodem, an Intelligent Application Security platform, uses runtime intelligence to show which vulnerabilities actually execute in production, so you can focus on the ones that represent real risk. Get a demo
6. What actually determines whether CVE-2026-54305 is exploitable, and how bad it is? Exploitability and impact are not fixed properties of a CVE. They depend on runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A high CVSS score on a dependency that never runs is not the same as real risk. Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter.
7. How do I fix CVE-2026-54305?
   • Upgrade n8n to 1.123.55 or later
   • Upgrade n8n to 2.26.2 or later
   • Upgrade n8n to 2.25.7 or later