Overview
A critical security vulnerability, identified as CVE-2026-54307, has been discovered in n8n, a widely used open-source platform that simplifies and automates various workflows. This flaw, dubbed ‘Cross-User Credential Access,’ presents a significant risk where sensitive user credentials could be exposed to unauthorized individuals. In essence, a malicious or compromised user with editor privileges on a shared workflow could exploit certain public API endpoints to gain access to credentials they do not legitimately own. This means that private login information, connection keys, and other secrets intended for specific users could be viewed or used by others on the same n8n instance. The core of the problem lies in insufficient credential ownership checks, which were only partially enforced across the platform. If your organization relies on n8n for automating tasks and utilizes its workflow sharing features, particularly when member-level users are granted editor access to shared workflows, your system could be at risk. Understanding and addressing this vulnerability swiftly is crucial to maintaining the security and integrity of your automated processes and sensitive data.
CVE Details
- Product: n8n workflow automation platform
- CVE ID: CVE-2026-54307
- Published Date: June 23, 2026
- Last Modified: June 26, 2026
- Severity: Critical (CVSS Score 9.6)
- Status: Analyzed
Affected Products
This vulnerability impacts versions of n8n prior to the following:
- 1.123.55
- 2.25.7
- 2.26.2
Current Status
The vulnerability has been thoroughly analyzed, and its details are now public. Patches have been released to address the flaw.
Severity Level
This vulnerability has been assigned a ‘Critical’ severity rating with a CVSS (Common Vulnerability Scoring System) score of 9.6 out of 10. A critical rating signifies the highest level of risk, indicating that exploiting this flaw can lead to severe consequences, often without requiring complex attack techniques or significant user interaction. For n8n users, this translates to a high potential for a complete loss of confidentiality regarding sensitive data, as attackers could exfiltrate stored credentials. While the immediate impact on integrity and availability of the n8n system itself might appear lower, the ability to steal credentials for integrated services could lead to widespread compromise across various connected platforms. This could result in unauthorized data access, manipulation, or even service disruption in those linked systems. Therefore, the immediate and far-reaching implications of credential theft make this a top-priority security concern for all n8n administrators and users.
Possible Solutions
The most effective way to protect your n8n instance is to upgrade to a patched version immediately. The following versions include the fix:
- n8n 1.123.55 or later
- n8n 2.25.7 or later
- n8n 2.26.2 or later
If an immediate upgrade is not feasible, consider these temporary mitigation steps:
- Restrict Workflow Sharing: Only share workflows with users who are fully trusted and require editor access.
- Audit Shared Workflows: Regularly review shared workflows for any unexpected credential references or recent unauthorized modifications.
These workarounds help reduce risk but do not fully resolve the underlying issue. Prioritize upgrading to a secure version as soon as possible.
References
https://github.com/n8n-io/n8n/security/advisories/GHSA-pmqw-72cg-wx85
