CVE-2026-54305: n8n: Cross-Tenant Credential Takeover via Dynamic Credentials EE Endpoints

Published Jun 16, 2026
·
Updated

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 N8NENVFEATDYNAMICCREDENTIALS.

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

Other sources

n8n is an open source workflow automation platform. Prior to 1.123.55, 2.25.7, and 2.26.2, 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 vulnerability is fixed in 1.123.55, 2.25.7, and 2.26.2.

MITRE

Affected Software

6 affected componentsFixes available
npm/n8n>=2.0.0-rc.0<2.25.7
2.25.7
npm/n8n>=2.26.0<2.26.2
2.26.2
npm/n8n<1.123.55
1.123.55
n8n N8n Node.js<1.123.55
n8n N8n Node.js>=2.0.0<2.25.7
n8n N8n Node.js>=2.26.0<2.26.2

Remediation

Recommended actions to resolve this vulnerability, in priority order.

  1. Upgrade

    Upgrade npm/n8n to a version that resolves this vulnerability.

    Fixed in 2.25.7
  2. Upgrade

    Upgrade npm/n8n to a version that resolves this vulnerability.

    Fixed in 2.26.2
  3. Upgrade

    Upgrade npm/n8n to a version that resolves this vulnerability.

    Fixed in 1.123.55
  4. Upgrade

    Upgrade n8n to a version that resolves this vulnerability.

    Fixed in 1.123.55
  5. Upgrade

    Upgrade n8n to a version that resolves this vulnerability.

    Fixed in 2.25.7
  6. Upgrade

    Upgrade n8n to a version that resolves this vulnerability.

    Fixed in 2.26.2
  7. Configuration

    If the Dynamic Credentials feature is not actively required, disable it by unsetting N8N_ENV_FEAT_DYNAMIC_CREDENTIALS.

    n8n N8N_ENV_FEAT_DYNAMIC_CREDENTIALS = unset
  8. Compensating control

    Restrict n8n instance access to fully trusted users only.

Event History

Jun 16, 2026
Advisory Published
via GitHub·11:32 PM
Data Sourced
via GitHub·11:32 PM
DescriptionSeverityWeaknessAffected Software
Jun 23, 2026
CVE Published
via MITRE·03:45 PM
Data Sourced
via MITRE·03:45 PM
DescriptionWeakness
Data Sourced
via NVD·05:17 PM
DescriptionSeverityWeaknessAffected Software

Frequently Asked Questions

1

What is the severity of CVE-2026-54305?

The severity of CVE-2026-54305 is rated as critical with a score of 9.9.

2

How do I fix CVE-2026-54305?

To address CVE-2026-54305, ensure that proper per-resource ownership and scope checks are implemented for all Dynamic Credentials feature endpoints.

3

What software is affected by CVE-2026-54305?

CVE-2026-54305 affects the n8n software package version available on npm.

4

What kind of risks does CVE-2026-54305 introduce?

CVE-2026-54305 poses risks of information leakage, allowing unauthorized users to access sensitive workflows and credentials.

5

When was CVE-2026-54305 published?

CVE-2026-54305 was published on June 16, 2026.

Contact

SecAlerts Pty Ltd.
132 Wickham Terrace
Fortitude Valley,
QLD 4006, Australia
info@secalerts.co
By using SecAlerts services, you agree to our services end-user license agreement. This website is safeguarded by reCAPTCHA and governed by the Google Privacy Policy and Terms of Service. All names, logos, and brands of products are owned by their respective owners, and any usage of these names, logos, and brands for identification purposes only does not imply endorsement. If you possess any content that requires removal, please get in touch with us.
© 2026 SecAlerts Pty Ltd.
ABN: 70 645 966 203, ACN: 645 966 203