CVE-2026-86073: CWE-863: Incorrect Authorization in n8n-io n8n
An incorrect authorization vulnerability exists in n8n versions prior to 2.37.7 and 2.38.1. The OAuth token endpoint failed to properly bind refresh tokens to the originally consented resource, allowing an OAuth client authorized for one workflow to obtain valid tokens for other unapproved workflows by substituting the resource parameter. This issue is fixed in versions 2.37.7 and 2.38.1.
AI Analysis
Technical Summary
The n8n workflow automation platform had an authorization flaw in its OAuth token endpoint before versions 2.37.7 and 2.38.1. While the first access token was correctly bound to the consented resource, the refresh token was not. When refreshing tokens, the system only verified that the requested resource was registered, not that it matched the original authorization grant. This allowed an OAuth client approved for one workflow to substitute a different workflow URL in the resource parameter and obtain a valid token for an unapproved workflow accessible to the consenting user. The vulnerability is identified as CWE-863 (Incorrect Authorization) and has a CVSS 4.0 base score of 5.9 (medium severity).
Potential Impact
An attacker with an OAuth client authorized for one workflow could use this flaw to obtain valid tokens for other workflows that were not originally approved by the user. This could lead to unauthorized access to workflows and potentially sensitive data or actions within those workflows. However, exploitation requires user interaction (UI:A) and the attacker has no privileges initially (PR:N).
Mitigation Recommendations
This vulnerability is fixed in n8n versions 2.37.7 and 2.38.1. Users should upgrade to one of these versions or later to remediate the issue. No other mitigation guidance is provided or required.
CVE-2026-86073: CWE-863: Incorrect Authorization in n8n-io n8n
Description
An incorrect authorization vulnerability exists in n8n versions prior to 2.37.7 and 2.38.1. The OAuth token endpoint failed to properly bind refresh tokens to the originally consented resource, allowing an OAuth client authorized for one workflow to obtain valid tokens for other unapproved workflows by substituting the resource parameter. This issue is fixed in versions 2.37.7 and 2.38.1.
CVSS v4.0
Score 5.9medium
Affected software
Run on your own infrastructure? Check whether these packages are installed with threat-finder — our free open-source scanner.
Weaknesses
AI-Powered Analysis
Machine-generated threat intelligence
Technical Analysis
The n8n workflow automation platform had an authorization flaw in its OAuth token endpoint before versions 2.37.7 and 2.38.1. While the first access token was correctly bound to the consented resource, the refresh token was not. When refreshing tokens, the system only verified that the requested resource was registered, not that it matched the original authorization grant. This allowed an OAuth client approved for one workflow to substitute a different workflow URL in the resource parameter and obtain a valid token for an unapproved workflow accessible to the consenting user. The vulnerability is identified as CWE-863 (Incorrect Authorization) and has a CVSS 4.0 base score of 5.9 (medium severity).
Potential Impact
An attacker with an OAuth client authorized for one workflow could use this flaw to obtain valid tokens for other workflows that were not originally approved by the user. This could lead to unauthorized access to workflows and potentially sensitive data or actions within those workflows. However, exploitation requires user interaction (UI:A) and the attacker has no privileges initially (PR:N).
Mitigation Recommendations
This vulnerability is fixed in n8n versions 2.37.7 and 2.38.1. Users should upgrade to one of these versions or later to remediate the issue. No other mitigation guidance is provided or required.
Technical Details
- Data Version
- 5.2
- Assigner Short Name
- GitHub_M
- Date Reserved
- 2026-09-04T19:34:03.100Z
- Cvss Version
- 4.0
- State
- PUBLISHED
- Remediation Level
- null
Threat ID: 6aa040f6acd9273b49f5b519
Added to database: 09/08/2026, 17:08:06 UTC
Last enriched: 09/08/2026, 17:22:46 UTC
Last updated: 09/08/2026, 17:22:46 UTC
Views: 4
Community Reviews
0 reviewsCrowdsource mitigation strategies, share intel context, and vote on the most helpful responses. Sign in to add your voice and help keep defenders ahead.
Want to contribute mitigation steps or threat intel context? Sign in or create an account to join the community discussion.
Actions
Updates to AI analysis require Pro Console access. Upgrade inside Console → Billing.
Need more coverage?
Upgrade to Pro Console for AI refresh and higher limits.
For incident response and remediation, OffSeq services can help resolve threats faster.
Latest Threats
Check if your credentials are on the dark web
Instant breach scanning across billions of leaked records. Free tier available.