Auth bypass in N8n
CVE-2026-86073
n8n is an open source workflow automation platform. Prior to 2.37.7 and 2.38.1, the OAuth token endpoint bound an authorization code's first access token to the consented resource but did not bind its refresh token. Refreshing checked only that the requested resource was registered, not that it matched the original grant. An OAuth client approved for one workflow could substitute a different workflow URL in the resource parameter and obtain a valid token for an unapproved workflow accessible to the consenting user. This issue is fixed in versions 2.37.7 and 2.38.1.
Vulnerability class: Broken Access Control
Published · last modified .
CVSS v3 metric
CVSS v3 base score 7.6 (High). Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:L/A:L.
EPSS exploit prediction
EPSS: 0.004 (31.9th percentile), scored .
Very low probability of exploitation in the next 30 days; routine patching cadence is appropriate. 32nd percentile — 31.9% of CVEs in the catalogue have a lower EPSS than this one. How to read EPSS.
EPSS over last 30 days · oldest: 0.004 · newest: 0.004 · change: 0.000
Affected products
- N8n — versions 2.38.0
- N8n-Io N8n — versions < 2.37.7, >= 2.38.0, < 2.38.1
Weakness classification (CWE)
References
- github.com/n8n-io/n8n/commit/18458482861097a26f874f30ad7e8136e268475c (Patch)
- github.com/n8n-io/n8n/commit/380788fd9a3264c83161e868026a98731d274d88 (Patch)
- github.com/n8n-io/n8n/pull/37122 (Issue Tracking)
- github.com/n8n-io/n8n/pull/37588 (Issue Tracking)
- github.com/n8n-io/n8n/releases/tag/n8n@2.37.7 (Release Notes)
- github.com/n8n-io/n8n/releases/tag/n8n@2.38.1 (Release Notes)
- github.com/n8n-io/n8n/security/advisories/GHSA-cw9w-vv67-hf73 (Mitigation, Vendor Advisory)
Frequently asked questions
- What is CVE-2026-86073?
- CVE-2026-86073 is a high-severity vulnerability in N8n, classified under Incorrect Authorization. CVSS score: 7.6/10. Published 2026-09-08.
- How severe is CVE-2026-86073?
- High severity. CVSS v3 base score is 7.6 out of 10.