CVE-2026-86073
Medium
Elevated severity or exploit probability.
CVSS base
7.6
HIGH
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:L/A:L
EPSS — probability of exploitation (30 days)
0.2%
12.5th percentile
CISA KEV
Not listed
Weakness / dates
CWE-863
Published 2026-09-08 · modified 2026-09-11
CVSS breakdown
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:L/A:L
| Attack Vector | N | Network |
| Attack Complexity | L | Low |
| Privileges Required | N | None |
| User Interaction | R | Required |
| Scope | U | Unchanged |
| Confidentiality | H | High |
| Integrity | L | Low |
| Availability | L | Low |
Timeline
- 2026-09-08 — Published (NVD)
- 2026-09-11 — Last modified (NVD)
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.
Affected
References
- https://github.com/n8n-io/n8n/commit/18458482861097a26f874f30ad7e8136e268475c
- https://github.com/n8n-io/n8n/commit/380788fd9a3264c83161e868026a98731d274d88
- https://github.com/n8n-io/n8n/pull/37122
- https://github.com/n8n-io/n8n/pull/37588
- https://github.com/n8n-io/n8n/releases/tag/n8n@2.37.7
- https://github.com/n8n-io/n8n/releases/tag/n8n@2.38.1
- https://github.com/n8n-io/n8n/security/advisories/GHSA-cw9w-vv67-hf73