OAuth consent bypass via unbound refresh-token resource
Published Sep 8, 2026 · Updated Sep 9, 2026
Improper authorization in the n8n OAuth token endpoint before 2.37.7 and in 2.38.0 allows remote attackers to access unapproved workflows. Refresh-token records omit the consented resource, so rotation accepts any registered resource URL supplied by the client instead of enforcing the original grant. Exploitation requires a registered OAuth client, an authenticated user's approval for one protected workflow, and knowledge of another workflow that user can execute.
Summary
What happened
Improper authorization in the n8n OAuth token endpoint before 2.37.7 and in 2.38.0 allows remote attackers to access unapproved workflows. Refresh-token records omit the consented resource, so rotation accepts any registered resource URL supplied by the client instead of enforcing the original grant. Exploitation requires a registered OAuth client, an authenticated user's approval for one protected workflow, and knowledge of another workflow that user can execute.
The record
- CVE
- CVE-2026-86073
- Published
- Sep 8, 2026
- Updated
- Sep 9, 2026
- Vendor
- n8n
- Product
- n8n
- Classifications
- T1550.001
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Sep 8, 2026CVE publishedPublication date reported by the CVE source.
- Sep 9, 2026Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=< 2.37.7
- Affected versionversion=>= 2.38.0, < 2.38.1
What conditions does exploitation require?
What is affected?
Published CVSS scores
CVSS describes severity. EPSS estimates exploitation probability.
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Weakness, pattern, technique
Public exploit references
No public exploit references are available in this record.
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo