CVE-2026-54307: n8n: Credential Exfiltration via Permission Bypass

Published Jun 16, 2026
·
Updated

Impact A member-level user with editor access to a shared workflow could reference credentials they do not own via specific public API endpoints. Credential ownership checks were only enforced partially leading to cross-user credential access.

This issue affects instances where workflow sharing is enabled and at least one workflow has been shared with a member-level user as an Editor.

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 workflow sharing to fully trusted users only. - Audit shared workflows for unexpected credential references or recent modifications.

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

Credits: Momen Elkhouli

Other sources

n8n is an open source workflow automation platform. Prior to 1.123.55, 2.25.7, and 2.26.2, a member-level user with editor access to a shared workflow could reference credentials they do not own via specific public API endpoints. Credential ownership checks were only enforced partially leading to cross-user credential access. This issue affects instances where workflow sharing is enabled and at least one workflow has been shared with a member-level user as an Editor. 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

    Restrict workflow sharing so it is limited to fully trusted users only.

    n8n workflow sharing shared workflow access level = fully trusted users only
  8. Compensating control

    Audit shared workflows for unexpected credential references or recent modifications.

Event History

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

Frequently Asked Questions

1

What is the severity of CVE-2026-54307?

The severity of CVE-2026-54307 is critical with a CVSS score of 9.6.

2

How do I fix CVE-2026-54307?

To fix CVE-2026-54307, ensure that credential ownership checks are fully enforced in your workflow configuration.

3

What impact does CVE-2026-54307 have on user data?

CVE-2026-54307 allows a member-level user with editor access to reference credentials they do not own, leading to potential unauthorized access to sensitive information.

4

What software is affected by CVE-2026-54307?

CVE-2026-54307 affects the npm/n8n workflow automation software.

5

When was CVE-2026-54307 published?

CVE-2026-54307 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