CVE-2026-56350
highpriority · track · 31EPSS 0.004 · 32 %ileDEEUNLUSEPSS · scored 2026-10-27
n8n before 2.8.0 contains an authentication bypass vulnerability allowing authenticated SSO users to disable SSO enforcement through the API. Attackers can create local password credentials to authenticate directly, bypassing organizational SSO policies and identity-provider-enforced multi-factor authentication.
cvss
Technical severity, 0–10. One row per scoring source.
base score 0–10 · higher = more severe · hover a vector to decode⚠ sources disagree · low–high · 2.3–7.7
ssvc
A stakeholder decision — act, attend, or track — from exploitation and impact.
weaknesses
The CWE weakness classes this flaw belongs to.
affected products (5)
Products and version ranges known to be affected.
advisories (3)
Vendor and ecosystem advisories describing this.
- NCSC-2026-0248Kwetsbaarheden verholpen in n8n workflow automation platformNL2026-07-17csaf · ncsc_nlNL
n8n heeft meerdere kwetsbaarheden verholpen in het n8n workflow automation platform, specifiek in versies voor 2.10.1, 2.9.3, 1.123.22 en andere gerelateerde releases.
- WID-SEC-W-2026-0532n8n: Mehrere SchwachstellenDeutsch2026-02-25csaf · cert_bundDE
Ein Angreifer kann mehrere Schwachstellen in n8n ausnutzen, um beliebigen Programmcode auszuführen, um Sicherheitsvorkehrungen zu umgehen, um Daten zu manipulieren, um einen SQL-Injection Angriff durchzuführen, und um einen Cross-Site Scripting Angriff durchzuführen.
- GHSA-vjf3-2gpj-233vn8n has an SSO Enforcement Bypass in its Self-Service Settings API2026-02-26ghsa · osvUS
## 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.
also known as (3)
Other names and identifiers for this entity.
sources
Which sources assert this record, and when.
references (6)
External citations — patches, advisories, analysis.
- https://github.com/n8n-io/n8n/security/advisories/GHSA-vjf3-2gpj-233vcnnvd
- https://www.vulncheck.com/advisories/n8n-sso-enforcement-bypass-via-apicnnvd
- https://github.com/n8n-io/n8n/security/advisories/GHSA-vjf3-2gpj-233venisa_euvd
- https://www.vulncheck.com/advisories/n8n-sso-enforcement-bypass-via-apienisa_euvd
- https://github.com/n8n-io/n8n/security/advisories/GHSA-vjf3-2gpj-233vMitigationVendor Advisorynvd
- https://www.vulncheck.com/advisories/n8n-sso-enforcement-bypass-via-apiThird Party Advisorynvd
Attackers weaponise vulnerabilities like this against internet-exposed services. See what is exposed on your perimeter with a free passive scan.
Free scan