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.

What this means for your business

It affects N8n. It matters if your company, or a supplier that handles your data, runs it.
An attacker can use it remotely, over a network, without a login, but only after tricking someone into an action such as opening a file or a link.
FIRST's prediction model gives it a 0.2% chance of attack attempts being seen in the next 30 days, ranking above 12% of all known flaws.

What to do

1Check whether your company or your suppliers run N8n, and which version. The affected versions are listed further down this page.
2If you do, apply the vendor's fix. A patch or vendor advisory has been published.

Not sure if your company is exposed?

Fastnexa’s certified penetration testers can check whether attackers could use this flaw, or others like it, against your websites, apps and network. The full test is free for our first 10 founding clients until 31 December 2026.

Check if you’re exposed Book a call

Scoring

CVSS: 7.6 (v3.1)
Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:L/A:L
CVSS v4: 5.9
Weakness: CWE-863
Assigned by: security-advisories@github.com

Dates

Published: 2026-09-08
Last modified: 2026-09-11
Sources: NVD

Affected products

N8n N8n- 2.37.7, 2.38.0

As listed in the NVD configuration data. Not a statement about your estate.