GHSA-vjf3-2gpj-233v: N8n Remote Code Execution Vulnerability

MODERATE
Share
CVSS 6.3
CWE-284 CWE-287 CWE-269
Published
Advisory Summary

GHSA-vjf3-2gpj-233v is a MODERATE (CVSS 6.3) remote code execution vulnerability (CWE-284: Improper Access Control) affecting N8n libraries in the npm ecosystem. The issue involves n8n has an sso enforcement bypass in its self-service settings api. Remediation is available by upgrading affected packages to version 2.8.0.

GHSA-vjf3-2gpj-233v at a Glance

CVE Identifier N/A
GHSA Identifier GHSA-vjf3-2gpj-233v
Severity MODERATE
CVSS v3.1 Base Score 6.3
CWE Classification CWE-284: Improper Access Control
Affected Product N8n
Package Ecosystem npm
Published Date
Last Updated

Security Impact

CVSS: 6.3

The security impact metrics below are parsed directly from the CVSS v3.1 vector string (CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:C/C:N/I:H/A:N).

Attack Vector Network (AV:N)
Attack Complexity High (AC:H)
Privileges Required Low (PR:L)
User Interaction None (UI:N)
Scope Changed (S:C)
Confidentiality None (C:N)
Integrity High (I:H)
Availability None (A:N)

How to Fix GHSA-vjf3-2gpj-233v

To remediate this vulnerability, upgrade all affected N8n dependencies to a patched release. Both direct and transitive dependencies should be checked, as frameworks or security libraries may pull in vulnerable versions transitively.

n8n fixed: 2.8.0 
npm install n8n@2.8.0
Verify Direct and Transitive Dependencies

Run the following command in your project directory to verify that all resolved dependencies use the patched release: 

npm ls n8n

How to Check if You Are Affected

To determine whether your Node.js application is affected by GHSA-vjf3-2gpj-233v, inspect your project dependencies using npm:

npm ls n8n

Analyze the terminal output to locate any version of N8n in your dependency tree. If any resolved version matches the vulnerable ranges listed in the table below (for example, versions earlier than 2.8.0), your application is affected.

Note: The npm ls n8n command inspects dependencies declared in your package.json and lockfile; it does not perform automated runtime dynamic scanning.

Technical Details

Vulnerability Mechanism & Technical Analysis

This vulnerability is classified under CWE-284: Improper Access Control, where the product does not restrict or incorrectly restricts access to a resource from an unauthorized actor. In N8n, software state validation or input boundaries are circumvented during processing. Review the official source advisory statement below for specific affected components, classes, and reproduction details.

Source Advisory Statement

## 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.

GHSA-vjf3-2gpj-233v Affected N8n Versions

1 component(s)
Fixed Versions:
2.8.0
Product / Package Ecosystem Affected Versions Fixed Version
n8n
npm/n8n
npm
< 2.8.0
2.8.0

References

GitHub Advisory / Wiki ADVISORY
https://github.com/n8n-io/n8n/security/advisories/GHSA-vjf3-2gpj-233v
Security Fix Commit FIX COMMIT
https://github.com/n8n-io/n8n/commit/a70b2ea379086da3de103bb84811e88cadf29976
N8n Source Repository REPOSITORY
https://github.com/n8n-io/n8n
N8n Release RELEASE
https://github.com/n8n-io/n8n/releases/tag/n8n@2.8.0

Frequently Asked Questions

What is GHSA-vjf3-2gpj-233v?
GHSA-vjf3-2gpj-233v is a security vulnerability in N8n involving n8n has an SSO Enforcement Bypass in its Self-Service Settings API under CWE-284: Improper Access Control.
Which N8n versions are affected?
Affected versions include releases prior to 2.8.0 across affected packages: n8n.
What version fixes GHSA-vjf3-2gpj-233v?
Upgrading to 2.8.0 (or the latest patched release for your respective branch) resolves the vulnerability.
Is n8n affected?
Yes, n8n is affected in releases prior to 2.8.0. Upgrade your dependency to 2.8.0 or later.
What is the CVSS score of GHSA-vjf3-2gpj-233v?
GHSA-vjf3-2gpj-233v has a CVSS v3.1 base score of 6.3 (MODERATE) with vector string CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:C/C:N/I:H/A:N.
What CWE is associated with GHSA-vjf3-2gpj-233v?
GHSA-vjf3-2gpj-233v is classified under CWE-284: Improper Access Control (The product does not restrict or incorrectly restricts access to a resource from an unauthorized actor.).
How can I check npm dependencies for GHSA-vjf3-2gpj-233v?
Run the dependency tree command: 'npm ls n8n'. This command lists direct and transitive dependencies in your build configuration so you can verify if a vulnerable version is resolved.
Machine-readable OSV JSON OSV v1.5 Schema
Normalized schema output
View Raw JSON 
{
  "schema_version" : "1.4.0",
  "id" : "GHSA-vjf3-2gpj-233v",
  "modified" : "2026-02-26T22:45:14Z",
  "published" : "2026-02-26T22:45:13Z",
  "aliases" : [ ],
  "summary" : "n8n has an SSO Enforcement Bypass in its Self-Service Settings API",
  "details" : "## Impact\nAn 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.\n\n## Patches\nThe issue has been fixed in n8n version 2.8.0. Users should upgrade to this version or later to remediate the vulnerability.\n\n## Workarounds\nIf upgrading is not immediately possible, administrators should consider the following temporary mitigations:\n- Monitor audit logs for users who create local credentials after authenticating via SSO.\n- Restrict the n8n instance to fully trusted users only.\n\nThese workarounds do not fully remediate the risk and should only be used as short-term mitigation measures.",
  "severity" : [ {
    "type" : "CVSS_V3",
    "score" : "CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:C/C:N/I:H/A:N"
  }, {
    "type" : "CVSS_V4",
    "score" : "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"
  } ],
  "affected" : [ {
    "package" : {
      "ecosystem" : "npm",
      "name" : "n8n"
    },
    "ranges" : [ {
      "type" : "ECOSYSTEM",
      "events" : [ {
        "introduced" : "0"
      }, {
        "fixed" : "2.8.0"
      } ]
    } ]
  } ],
  "references" : [ {
    "type" : "WEB",
    "url" : "https://github.com/n8n-io/n8n/security/advisories/GHSA-vjf3-2gpj-233v"
  }, {
    "type" : "WEB",
    "url" : "https://github.com/n8n-io/n8n/commit/a70b2ea379086da3de103bb84811e88cadf29976"
  }, {
    "type" : "PACKAGE",
    "url" : "https://github.com/n8n-io/n8n"
  }, {
    "type" : "WEB",
    "url" : "https://github.com/n8n-io/n8n/releases/tag/n8n@2.8.0"
  } ],
  "database_specific" : {
    "cwe_ids" : [ "CWE-269", "CWE-284", "CWE-287" ],
    "severity" : "MODERATE",
    "github_reviewed" : true,
    "github_reviewed_at" : "2026-02-26T22:45:13Z",
    "nvd_published_at" : null
  }
}