Understanding the n8n SSO Enforcement Bypass
A notable security flaw has been discovered in n8n, a popular workflow automation tool. This vulnerability, identified as an authentication bypass, allows certain users to sidestep crucial security measures. Specifically, an authenticated user who typically signs in using Single Sign-On (SSO) could exploit an API weakness to disable SSO enforcement for their own account. This means they could then create a local password, granting them direct access to n8n without needing to go through the organization’s SSO system. This bypass also circumvents any multi-factor authentication enforced by the identity provider, posing a significant risk to centralized identity management.
CVE Details
- Product: n8n
- Published Date: June 30, 2026
- Severity: Medium (CVSS v3.1 Score: 6.3)
- Status: Analyzed
Affected Products
The authentication bypass vulnerability impacts versions of n8n prior to 2.8.0. If your n8n instance is running an older version, it is susceptible to this issue.
Current Status
This vulnerability has been officially “Analyzed”, meaning its details, impact, and initial solutions have been investigated and documented by security researchers and the vendor.
Severity Level
The vulnerability carries a Medium severity rating with a CVSS v3.1 score of 6.3. While not critical, a medium severity indicates that the flaw could have a noticeable impact if exploited. In this case, it undermines the security benefits of SSO, potentially leading to unauthorized access and a loss of oversight over user authentication, which can be particularly problematic for organizations relying on strict identity management policies.
Possible Solutions
The most effective way to protect your n8n instance from this authentication bypass vulnerability is to upgrade to a patched version.
- Upgrade: Users are strongly advised to upgrade their n8n instance to version 2.8.0 or later. This version includes the necessary fixes to resolve the vulnerability.
If an immediate upgrade is not feasible, consider these temporary mitigation steps:
- Monitor Audit Logs: Regularly review audit logs for any unusual activity, especially for users attempting to create local credentials after authenticating via SSO.
- Restrict Access: Limit access to your n8n instance to only fully trusted users. This is a stop-gap measure and should not replace a timely upgrade.
References
https://github.com/n8n-io/n8n/security/advisories/GHSA-vjf3-2gpj-233v
https://www.vulncheck.com/advisories/n8n-sso-enforcement-bypass-via-api
