OAuth token theft via skipped state ownership check
Published Mar 25, 2026 · Updated Mar 25, 2026
Incorrect authorization in n8n before 2.8.0 allows remote attackers to capture victims' OAuth tokens through a crafted OAuth flow. With N8N_SKIP_AUTH_ON_OAUTH_CALLBACK=true, the callback handler omits ownership verification of OAuth state and saves the victim's tokens to an attacker-controlled credential. The non-default setting and victim completion of the OAuth flow are required; stolen tokens let the attacker execute workflows as the victim.
Summary
What happened
Incorrect authorization in n8n before 2.8.0 allows remote attackers to capture victims' OAuth tokens through a crafted OAuth flow. With N8N_SKIP_AUTH_ON_OAUTH_CALLBACK=true, the callback handler omits ownership verification of OAuth state and saves the victim's tokens to an attacker-controlled credential. The non-default setting and victim completion of the OAuth flow are required; stolen tokens let the attacker execute workflows as the victim.
The record
- CVE
- CVE-2026-33720
- Published
- Mar 25, 2026
- Updated
- Mar 25, 2026
- Vendor
- n8n
- Product
- n8n
- Classifications
- CWE-863, T1550.001, T1528
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Mar 25, 2026CVE publishedPublication date reported by the CVE source.
- Mar 25, 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.8.0
What conditions does exploitation require?
What is affected?
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