GHSA-5vfw-jc4p-fj39: Duplicate Advisory Member-Level Users Can Execute Other Vulnerability

MODERATE
CWE-863
Published
Advisory Summary

GHSA-5vfw-jc4p-fj39 is a MODERATE member-level users can execute other vulnerability (CWE-863: Incorrect Authorization) affecting Duplicate Advisory libraries in the npm ecosystem. The issue involves member-level users can execute other users' mcp server trigger workflows via missing oauth authorization check. Remediation is available in the latest vendor maintenance releases.

GHSA-5vfw-jc4p-fj39 at a Glance

CVE Identifier N/A
GHSA Identifier GHSA-5vfw-jc4p-fj39
Severity MODERATE
CVSS v3.1 Base Score N/A
CWE Classification CWE-863: Incorrect Authorization
Affected Product Duplicate Advisory
Package Ecosystem npm
Published Date
Last Updated

How to Fix GHSA-5vfw-jc4p-fj39

To remediate this vulnerability, upgrade all affected Duplicate Advisory 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: Latest secure release
npm install n8n@Latest secure release
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-5vfw-jc4p-fj39, inspect your project dependencies using npm:

npm ls n8n

Analyze the terminal output to locate any version of Duplicate Advisory in your dependency tree. If any resolved version matches the vulnerable ranges listed in the table below (for example, versions earlier than the patched release), 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-863: Incorrect Authorization, where the product performs an authorization check when an actor attempts to access a resource or perform an action, but it does not correctly perform the check. In Duplicate Advisory, 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

## Duplicate Advisory This advisory has been withdrawn because it is a duplicate of GHSA-q5xf-xhwf-cwqf. This link is maintained to preserve external references. ## Original Description n8n before 2.29.8 and 2.30.x before 2.30.1 (affected from 2.27.0, when the OAuth 2.1 consent and token-issuance flow was introduced) does not verify that the authenticated user has access to the workflow referenced as the OAuth resource. On instances with at least one active MCP Server Trigger workflow configured with n8n OAuth2 authentication, a member-level user can register an OAuth client, self-approve consent for another user's workflow, and obtain a valid token. The workflow then runs in the owner's project context with the owner's stored credentials, and the attacker can set tool inputs and read outputs (potentially including data from the owner's connected integrations), breaking user and project isolation.

GHSA-5vfw-jc4p-fj39 Affected Duplicate Advisory Versions

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

References

Frequently Asked Questions

What is GHSA-5vfw-jc4p-fj39?
GHSA-5vfw-jc4p-fj39 is a security vulnerability in Duplicate Advisory involving Member-Level Users Can Execute Other Users' MCP Server Trigger Workflows via Missing OAuth Authorization Check under CWE-863: Incorrect Authorization.
Which Duplicate Advisory versions are affected?
Affected versions include releases prior to current release patches across affected packages: n8n.
What version fixes GHSA-5vfw-jc4p-fj39?
Upgrading to current release patches (or the latest patched release for your respective branch) resolves the vulnerability.
Is n8n affected?
Yes, n8n is affected in releases prior to Latest secure release. Upgrade your dependency to Latest secure release or later.
What CWE is associated with GHSA-5vfw-jc4p-fj39?
GHSA-5vfw-jc4p-fj39 is classified under CWE-863: Incorrect Authorization (The product performs an authorization check when an actor attempts to access a resource or perform an action, but it does not correctly perform the check.).
How can I check npm dependencies for GHSA-5vfw-jc4p-fj39?
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
{
  "schema_version" : "1.4.0",
  "id" : "GHSA-5vfw-jc4p-fj39",
  "modified" : "2026-07-22T22:30:28Z",
  "published" : "2026-07-22T12:32:17Z",
  "withdrawn" : "2026-07-22T22:30:28Z",
  "aliases" : [ ],
  "summary" : "Duplicate Advisory: Member-Level Users Can Execute Other Users' MCP Server Trigger Workflows via Missing OAuth Authorization Check",
  "details" : "## Duplicate Advisory\n\nThis advisory has been withdrawn because it is a duplicate of GHSA-q5xf-xhwf-cwqf. This link is maintained to preserve external references.\n\n## Original Description\n\nn8n before 2.29.8 and 2.30.x before 2.30.1 (affected from 2.27.0, when the OAuth 2.1 consent and token-issuance flow was introduced) does not verify that the authenticated user has access to the workflow referenced as the OAuth resource. On instances with at least one active MCP Server Trigger workflow configured with n8n OAuth2 authentication, a member-level user can register an OAuth client, self-approve consent for another user's workflow, and obtain a valid token. The workflow then runs in the owner's project context with the owner's stored credentials, and the attacker can set tool inputs and read outputs (potentially including data from the owner's connected integrations), breaking user and project isolation.",
  "severity" : [ {
    "type" : "CVSS_V4",
    "score" : "CVSS:4.0/AV:N/AC:L/AT:P/PR:L/UI:N/VC:L/VI:L/VA:N/SC:H/SI:L/SA:N/E:X/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:X"
  } ],
  "affected" : [ {
    "package" : {
      "ecosystem" : "npm",
      "name" : "n8n"
    },
    "ranges" : [ {
      "type" : "ECOSYSTEM",
      "events" : [ {
        "introduced" : "0"
      } ]
    } ],
    "database_specific" : {
      "last_known_affected_version_range" : "< 2.29.8"
    }
  } ],
  "references" : [ {
    "type" : "WEB",
    "url" : "https://github.com/n8n-io/n8n/security/advisories/GHSA-q5xf-xhwf-cwqf"
  }, {
    "type" : "ADVISORY",
    "url" : "https://nvd.nist.gov/vuln/detail/CVE-2026-65594"
  }, {
    "type" : "WEB",
    "url" : "https://www.vulncheck.com/advisories/n8n-before-missing-oauth-authorization-check"
  } ],
  "database_specific" : {
    "cwe_ids" : [ "CWE-863" ],
    "severity" : "MODERATE",
    "github_reviewed" : true,
    "github_reviewed_at" : "2026-07-22T22:30:28Z",
    "nvd_published_at" : "2026-07-22T12:18:19Z"
  }
}