All vulnerabilities

Servers and applications

CVE-2026-86073

Per-Resource OAuth Consent Bypass via Unbound Refresh Token Resource Substitution

Severity
Medium 5.9
Published
3 Sept 2026
Last changed
11 Sept 2026
Added to UpHeron
1 Nov 2026
Fixed in
2.37.7, 2.38.2
Exploit chance
0.4% in the next 30 daysHigher than 33% of CVEs. EPSS by FIRST, 19 Nov 2026
Weakness
Incorrect authorization (CWE-863)
Attack
Over the network · Only under certain conditions · No login needed · Needs someone to click or open something
Attacker can
Read data · Change some data · Slow it down
CVSS vector
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/E:X/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:X
Also known as
GHSA-cw9w-vv67-hf73
Sources
NVD, Project advisories (GitHub)

Description

The OAuth token endpoint bound an authorization code's first access token to the consented resource, but not its refresh token. Refreshing only checked that the requested resource was registered, not that it matched the original grant. An OAuth client approved for one workflow could refresh with a different workflow's URL and get a valid, unapproved token for it. The patch binds refresh tokens to the granted resource and rejects mismatches.

Exploitation requires the attacker to register an OAuth client, convince an authenticated user to approve that client for one known protected resource, and know the URL of a second protected resource that the consenting user is permitted to execute.

From n8n-io/n8n's security advisory.

Workarounds

If upgrading is not immediately possible, administrators should consider the following temporary mitigations:

  • Restrict n8n instance access to fully trusted users only.
  • Deactivate MCP Trigger, form, and webhook workflows that are protected by the n8n OAuth server if they are not required.
  • Audit connected OAuth clients and revoke any that are not recognized or no longer needed.
  • Require re-authorization for all existing OAuth clients after upgrading, as previously issued refresh tokens did not store the original resource binding.
Workarounds as given by n8n-io/n8n's security advisory.

Affected software

SoftwareAffected versions
n8nServers and applications · cpe:a:n8n:n8n
  • Every version before 2.37.7
  • Version 2.38.0
n8nServers and applications · github:n8n-io/n8n
  • Every version before 2.38.2
  • Every version before 2.37.7

About n8n

low-code automation tool

From Wikidata, CC0 1.0.
Weekly downloads (npm)
103,525npm, 15 Nov 2026
Docker Hub pulls
286,090,810Docker Hub, 15 Nov 2026
GitHub stars
210,541GitHub, 15 Nov 2026
Forks
61,525GitHub, 15 Nov 2026
Latest release
[email protected]GitHub, 15 Nov 2026
Released
13 Nov 2026GitHub
Written in
TypeScript, Node.jsWikidata
First released
2019Wikidata
First published on GitHub
22 Jun 2019GitHub

References

  • NVD https://nvd.nist.gov/vuln/detail/CVE-2026-86073
  • CVE.org https://www.cve.org/CVERecord?id=CVE-2026-86073
  • GitHub Advisory Database https://github.com/advisories/GHSA-cw9w-vv67-hf73
  • github.com https://github.com/n8n-io/n8n/security/advisories/GHSA-cw9w-vv67-hf73