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.

Share this

Remediation#

Fixed upstream in n8n 2.38.2, 2.37.7.

Patch events

  1. This monthSecurity release

    AI toolingn8n

    n8n security releases: 2.38.2, 2.37.7

    Upgrade to 2.38.22.37.7

    Why: Vendor security release for server software (most severe: CVE-2026-86073).

Exploit intelligence#

SignalValueSource
Known exploitedNoCISA KEV
Ransomware use—CISA KEV
EPSS (30-day exploitation probability)0.4% (34th pct)FIRST EPSS v2026.06.15
CVSS base score5.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 exploitationnoneCISA Vulnrichment
SSVC automatableNoCISA Vulnrichment
SSVC technical impactpartialCISA Vulnrichment

Affected versions (from the CVE record)#

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.

Elsewhere#

Distro status: Debian · Ubuntu · Red Hat · Alpine

Something wrong on this page?
Anonymous. Reports are checked against the primary source.

Also on today's list

See today's list → · Coming up →