n8n-io · n8n · published 2026-09-08
CVE-2026-86073n8n: Per-Resource OAuth Consent Bypass via Unbound Refresh Token Resource Substitution
Routine No exploitation evidence; EPSS 0.4%.
CVE-2026-86073 is not known to be exploited in the wild. EPSS estimates a 0.4% chance of exploitation in the next 30 days, higher than 33% of all CVEs. This n8n vulnerability: CVSS 5.9 (v4.0). Fixed upstream in n8n 2.38.2, 2.37.7. Routine: patch when convenient.
Jump to: Remediation Exploit intelAffected versionsDescription
Remediation#
Fixed upstream in n8n 2.38.2, 2.37.7.
Patch events
AI toolingn8n
n8n security releases: 2.38.2, 2.37.7
Upgrade to
2.38.22.37.7Why: Vendor security release for server software (most severe: CVE-2026-86073).
Exploit intelligence#
| Signal | Value | Source |
|---|---|---|
| Known exploited | No | CISA KEV |
| Ransomware use | — | CISA KEV |
| EPSS (30-day exploitation probability) | 0.4% (34th pct) | FIRST EPSS v2026.06.15 |
| CVSS base score | 5.9 (v4.0)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 | CNA / CISA ADP |
| SSVC exploitation | none | CISA Vulnrichment |
| SSVC automatable | No | CISA Vulnrichment |
| SSVC technical impact | partial | CISA Vulnrichment |
Affected versions (from the CVE record)#
- n8n-io n8n
< 2.37.7(affected)>= 2.38.0, < 2.38.1(affected)
Description (from the CVE record)#
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.
Quoted from the CVE Program record.