Analysis and contextual insights are available on OpenCVE Cloud.
No vendor fix or workaround currently provided.
Additional remediation guidance may be available on OpenCVE Cloud.
Tracking
Sign in to view the affected projects.
| Source | ID | Title |
|---|---|---|
Github GHSA |
GHSA-cw9w-vv67-hf73 | n8n: Per-Resource OAuth Consent Bypass via Unbound Refresh Token Resource Substitution |
Fri, 11 Sep 2026 23:45:00 +0000
| Type | Values Removed | Values Added |
|---|---|---|
| First Time appeared |
N8n
N8n n8n |
|
| CPEs | cpe:2.3:a:n8n:n8n:*:*:*:*:*:node.js:*:* cpe:2.3:a:n8n:n8n:2.38.0:*:*:*:*:node.js:*:* |
|
| Vendors & Products |
N8n
N8n n8n |
|
| Metrics |
cvssV3_1
|
Wed, 09 Sep 2026 17:30:00 +0000
| Type | Values Removed | Values Added |
|---|---|---|
| Metrics |
ssvc
|
Tue, 08 Sep 2026 17:15:00 +0000
| Type | Values Removed | Values Added |
|---|---|---|
| Description | 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. | |
| Title | n8n: Per-Resource OAuth Consent Bypass via Unbound Refresh Token Resource Substitution | |
| Weaknesses | CWE-863 | |
| References |
|
|
| Metrics |
cvssV4_0
|
Status: PUBLISHED
Assigner: GitHub_M
Published:
Updated: 2026-09-09T15:58:40.814Z
Reserved: 2026-09-04T19:34:03.100Z
Link: CVE-2026-86073
Updated: 2026-09-09T15:58:37.999Z
Status : Analyzed
Published: 2026-09-08T17:18:39.167
Modified: 2026-09-11T18:07:39.963
Link: CVE-2026-86073
No data.
OpenCVE Enrichment
Updated: 2026-09-10T03:45:06Z
Github GHSA