n8n has an SSO Enforcement Bypass in its Self-Service Settings API
Medium6.3CVE-2026-56350 · Published Feb 26, 2026 · updated Jul 8, 2026
## Impact An authenticated user signed in through Single Sign-On (SSO) could disable SSO enforcement for their own account through the n8n API. This allowed the user to create a local password and authenticate directly with email and password, completely bypassing the organization's SSO policy, centralized identity management, and any identity-provider-enforced multi-factor authentication. ## Patches The issue has been fixed in n8n version 2.8.0. Users should upgrade to this version or later to remediate the vulnerability. ## Workarounds If upgrading is not immediately possible, administrators should consider the following temporary mitigations: - Monitor audit logs for users who create local credentials after authenticating via SSO. - Restrict the n8n instance to fully trusted users only. These workarounds do not fully remediate the risk and should only be used as short-term mitigation measures.
Affected versions
| Package | Affected | Fixed in |
|---|---|---|
| n8n npm | < 2.8.0 | 2.8.0 |
Details and references
More n8n advisories
All n8n| Date | Advisory | Severity | Fixed in |
|---|---|---|---|
| Feb 26 | n8n has Webhook Forgery on Zendesk Trigger Node | Medium4.0 | 1.123.18+1 more |
| Feb 26 | n8n has a Guardrail Node Bypass | Medium3.7 | 2.10.0 |
| Feb 26 | n8n has an Authentication Bypass in its Chat Trigger Node | Medium4.8 | 1.123.22+2 more |
| Feb 26 | n8n: Webhook Forgery on Github Webhook Trigger | Medium4.0 | 1.123.15+1 more |
| Feb 26 | n8n: SQL Injection in MySQL, PostgreSQL, and Microsoft SQL nodes | Medium8.2 | 2.4.0 |
| Feb 25 | n8n Vulnerable to Stored XSS via Various Nodes | High5.4 | 1.123.22+2 more |