CVE-2026-86073: n8n Remote Code Execution Vulnerability
MODERATECVE-2026-86073 is a MODERATE remote code execution vulnerability (CWE-863: Incorrect Authorization) affecting n8n libraries in the npm ecosystem. The issue involves per-resource oauth consent bypass via unbound refresh token resource substitution. Remediation is available by upgrading affected packages to version 2.38.1, 2.37.7.
CVE-2026-86073 at a Glance
How to Fix CVE-2026-86073
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.
npm install n8n@2.38.1
npm install n8n@2.37.7
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 CVE-2026-86073, 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.38.1), 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 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
CVE-2026-86073 Affected n8n Versions
2 component(s)References
Frequently Asked Questions
What is CVE-2026-86073?
Which n8n versions are affected?
What version fixes CVE-2026-86073?
Is n8n affected?
What CWE is associated with CVE-2026-86073?
How can I check npm dependencies for CVE-2026-86073?
Machine-readable OSV JSON
OSV v1.5 Schema
{
"schema_version" : "1.4.0",
"id" : "GHSA-cw9w-vv67-hf73",
"modified" : "2026-09-10T21:21:49Z",
"published" : "2026-09-10T21:21:49Z",
"aliases" : [ "CVE-2026-86073" ],
"summary" : "n8n: Per-Resource OAuth Consent Bypass via Unbound Refresh Token Resource Substitution",
"details" : "## Impact\n\nThe OAuth token endpoint bound an authorization code's first access token to the consented resource, but not its refresh token. Refreshing only checked that the requested resource was registered, not that it matched the original grant. An OAuth client approved for one workflow could refresh with a different workflow's URL and get a valid, unapproved token for it. The patch binds refresh tokens to the granted resource and rejects mismatches.\n\nExploitation requires the attacker to register an OAuth client, convince an authenticated user to approve that client for one known protected resource, and know the URL of a second protected resource that the consenting user is permitted to execute.\n\n## Patches\n\nThe issue has been fixed in n8n versions 2.38.1 and 2.37.7. Users should upgrade to this version or later to remediate the vulnerability.\n\n## Workarounds\n\nIf upgrading is not immediately possible, administrators should consider the following temporary mitigations:\n- Restrict n8n instance access to fully trusted users only.\n- Deactivate MCP Trigger, form, and webhook workflows that are protected by the n8n OAuth server if they are not required.\n- Audit connected OAuth clients and revoke any that are not recognized or no longer needed.\n- Require re-authorization for all existing OAuth clients after upgrading, as previously issued refresh tokens did not store the original resource binding.\n\nThese workarounds do not fully remediate the risk and should only be used as short-term mitigation measures.",
"severity" : [ {
"type" : "CVSS_V4",
"score" : "CVSS:4.0/AV:N/AC:L/AT:P/PR:N/UI:A/VC:H/VI:L/VA:L/SC:N/SI:N/SA:N"
} ],
"affected" : [ {
"package" : {
"ecosystem" : "npm",
"name" : "n8n"
},
"ranges" : [ {
"type" : "ECOSYSTEM",
"events" : [ {
"introduced" : "2.38.0"
}, {
"fixed" : "2.38.1"
} ]
} ]
}, {
"package" : {
"ecosystem" : "npm",
"name" : "n8n"
},
"ranges" : [ {
"type" : "ECOSYSTEM",
"events" : [ {
"introduced" : "0"
}, {
"fixed" : "2.37.7"
} ]
} ]
} ],
"references" : [ {
"type" : "WEB",
"url" : "https://github.com/n8n-io/n8n/security/advisories/GHSA-cw9w-vv67-hf73"
}, {
"type" : "ADVISORY",
"url" : "https://nvd.nist.gov/vuln/detail/CVE-2026-86073"
}, {
"type" : "WEB",
"url" : "https://github.com/n8n-io/n8n/pull/37122"
}, {
"type" : "WEB",
"url" : "https://github.com/n8n-io/n8n/pull/37588"
}, {
"type" : "WEB",
"url" : "https://github.com/n8n-io/n8n/commit/18458482861097a26f874f30ad7e8136e268475c"
}, {
"type" : "WEB",
"url" : "https://github.com/n8n-io/n8n/commit/380788fd9a3264c83161e868026a98731d274d88"
}, {
"type" : "PACKAGE",
"url" : "https://github.com/n8n-io/n8n"
}, {
"type" : "WEB",
"url" : "https://github.com/n8n-io/n8n/releases/tag/n8n@2.37.7"
}, {
"type" : "WEB",
"url" : "https://github.com/n8n-io/n8n/releases/tag/n8n@2.38.1"
} ],
"database_specific" : {
"cwe_ids" : [ "CWE-863" ],
"severity" : "MODERATE",
"github_reviewed" : true,
"github_reviewed_at" : "2026-09-10T21:21:49Z",
"nvd_published_at" : "2026-09-08T17:18:39Z"
}
}