CVE-2026-54307
Awaiting Analysis Awaiting Analysis - Queue
Unauthorized Credential Access in n8n Workflow Automation

Publication date: 2026-06-23

Last updated on: 2026-06-23

Assigner: GitHub, Inc.

Description
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.
CVSS Scores
EPSS Scores
Probability:
Percentile:
Meta Information
Published
2026-06-23
Last Modified
2026-06-23
Generated
2026-06-23
AI Q&A
2026-06-23
EPSS Evaluated
N/A
NVD
EUVD
Affected Vendors & Products
Showing 3 associated CPEs
Vendor Product Version / Range
n8n-io n8n to 1.123.55 (exc)
n8n-io n8n to 2.25.7 (exc)
n8n-io n8n to 2.26.2 (exc)
Helpful Resources
Exploitability
CWE
CWE Icon
KEV
KEV Icon
CWE ID Description
CWE-863 The product performs an authorization check when an actor attempts to access a resource or perform an action, but it does not correctly perform the check.
Attack-Flow Graph
AI Quick Actions
Instant insights powered by AI
Executive Summary

CVE-2026-54307 is a high-severity vulnerability in n8n, an open-source workflow automation platform. It occurs in versions prior to 1.123.55, 2.25.7, and 2.26.2. The issue allows a member-level user with editor access to a shared workflow to access credentials they do not own by exploiting specific public API endpoints. This happens because credential ownership checks were only partially enforced, leading to cross-user credential access. The vulnerability affects instances where workflow sharing is enabled and at least one workflow has been shared with an editor-level user.

Impact Analysis

This vulnerability can lead to unauthorized access and exfiltration of sensitive credentials by users who should not have access to them. Since a member-level user with editor rights can bypass ownership checks, they can potentially access confidential information stored in credentials, which can compromise the security of the affected system and any connected systems that rely on those credentials.

Detection Guidance

This vulnerability can be detected by auditing shared workflows for unexpected credential references, especially in instances where workflow sharing is enabled and at least one workflow has been shared with a member-level user as an Editor.

Since the issue involves exploitation of specific public API endpoints to access credentials, monitoring API access logs for unusual or unauthorized credential access attempts by member-level users with editor access can help detect exploitation.

No specific commands are provided in the available resources to detect this vulnerability.

Mitigation Strategies

The primary immediate step to mitigate this vulnerability is to upgrade n8n to one of the fixed versions: 1.123.55, 2.25.7, or 2.26.2.

As a temporary mitigation, restrict workflow sharing to trusted users only and audit shared workflows for any unexpected credential references.

Note that temporary mitigations do not fully resolve the risk, so upgrading to a patched version is strongly recommended.

Compliance Impact

This vulnerability allows a member-level user with editor access to a shared workflow to access credentials they do not own due to incomplete ownership checks in the n8n platform. Such unauthorized access to sensitive credentials can lead to data breaches or unauthorized data exposure.

Because credentials often contain sensitive personal or protected information, this vulnerability could impact compliance with data protection regulations such as GDPR and HIPAA by potentially exposing confidential data to unauthorized users.

Organizations using affected versions of n8n should upgrade to patched versions immediately to mitigate this risk and maintain compliance with these standards.

Chat Assistant
Ask questions about this CVE
Hi! I’m here to help you understand CVE-2026-54307. Ask me anything about the vulnerability, its impact, or mitigation strategies.
0/70
EPSS Chart