GHSA-vjf3-2gpj-233v
Suggest an improvement- Source
- https://github.com/advisories/GHSA-vjf3-2gpj-233v
- Import Source
- https://github.com/github/advisory-database/blob/main/advisories/github-reviewed/2026/02/GHSA-vjf3-2gpj-233v/GHSA-vjf3-2gpj-233v.json
- JSON Data
- https://api.osv.dev/v1/vulns/GHSA-vjf3-2gpj-233v
- Published
- 2026-02-26T22:45:13Z
- Modified
- 2026-02-26T23:20:15.146544Z
- Severity
-
- 6.3 (Medium) CVSS_V3 - CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:C/C:N/I:H/A:N CVSS Calculator
- 6.0 (Medium) CVSS_V4 - CVSS:4.0/AV:N/AC:L/AT:P/PR:L/UI:N/VC:N/VI:H/VA:N/SC:N/SI:N/SA:N CVSS Calculator
- Summary
- n8n has an SSO Enforcement Bypass in its Self-Service Settings API
- Details
-
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.
- Database specific
{ "github_reviewed": true, "github_reviewed_at": "2026-02-26T22:45:13Z", "severity": "MODERATE", "nvd_published_at": null, "cwe_ids": [ "CWE-269", "CWE-284", "CWE-287" ] }- References
Affected packages
npm / n8n
Package
- Name
- n8n
- View open source insights on deps.dev
- Purl
- pkg:npm/n8n