CVE-2026-33720: n8n Has Authorization Bypass in OAuth Callback via N8N_SKIP_AUTH_ON_OAUTH_CALLBACK

Published Mar 25, 2026
·
Updated

Impact When the N8NSKIPAUTHONOAUTHCALLBACK environment variable is set to true, the OAuth callback handler skips ownership verification of the OAuth state parameter. This allows an attacker to trick a victim into completing an OAuth flow against a credential object the attacker controls, causing the victim's OAuth tokens to be stored in the attacker's credential. The attacker can then use those tokens to execute workflows in their name.

- This issue only affects instances where N8NSKIPAUTHONOAUTHCALLBACK=true is explicitly configured (non-default).

Patches The issue has been fixed in n8n version 2.8.0. Users should upgrade to this version or later to remediate the vulnerability.

Workarounds If upgrading is not immediately possible, administrators should consider the following temporary mitigations: - Avoid enabling N8NSKIPAUTHONOAUTHCALLBACK=true unless strictly required. - Restrict access to the n8n instance to fully trusted users only.

These workarounds do not fully remediate the risk and should only be used as short-term mitigation measures.

Other sources

n8n is an open source workflow automation platform. Prior to version 2.8.0, when the N8NSKIPAUTHONOAUTHCALLBACK environment variable is set to true, the OAuth callback handler skips ownership verification of the OAuth state parameter. This allows an attacker to trick a victim into completing an OAuth flow against a credential object the attacker controls, causing the victim's OAuth tokens to be stored in the attacker's credential. The attacker can then use those tokens to execute workflows in their name. This issue only affects instances where N8NSKIPAUTHONOAUTHCALLBACK=true is explicitly configured (non-default). The issue has been fixed in n8n version 2.8.0. Users should upgrade to this version or later to remediate the vulnerability. If upgrading is not immediately possible, administrators should consider the following temporary mitigations: Avoid enabling N8NSKIPAUTHONOAUTHCALLBACK=true unless strictly required, and/ or restrict access to the n8n instance to fully trusted users only. These workarounds do not fully remediate the risk and should only be used as short-term mitigation measures.

MITRE

Affected Software

3 affected componentsFixes available
npm/n8n<2.8.0
npm/n8n<2.8.0
2.8.0
n8n N8n Node.js<2.8.0

Event History

Mar 25, 2026
CVE Published
via MITRE·06:06 PM
Data Sourced
via MITRE·06:06 PM
DescriptionWeakness
Data Sourced
via NVD·07:16 PM
DescriptionSeverityWeaknessAffected Software
Advisory Published
via GitHub·09:57 PM
Data Sourced
via GitHub·09:57 PM
DescriptionSeverityWeaknessAffected Software
Free Weekly Intel

Don't miss critical vulnerabilities

Join thousands of security professionals who receive our weekly digest of trending CVEs, zero-days, and exploited vulnerabilities.

No spam. Unsubscribe anytime.

Frequently Asked Questions

1

What is the severity of CVE-2026-33720?

CVE-2026-33720 has been classified as a high severity vulnerability due to the potential for unauthorized access.

2

How do I fix CVE-2026-33720?

To fix CVE-2026-33720, upgrade n8n to version 2.8.0 or later to ensure proper authorization checks are in place.

3

What does CVE-2026-33720 affect?

CVE-2026-33720 affects versions of n8n prior to 2.8.0 when the N8N_SKIP_AUTH_ON_OAUTH_CALLBACK variable is set to true.

4

How does CVE-2026-33720 impact n8n users?

CVE-2026-33720 allows attackers to bypass authorization during OAuth callbacks, potentially compromising user data.

5

What is the N8N_SKIP_AUTH_ON_OAUTH_CALLBACK environment variable?

The N8N_SKIP_AUTH_ON_OAUTH_CALLBACK environment variable, when set to true, disables ownership verification for OAuth callbacks, leading to possible unauthorized access.

Contact

SecAlerts Pty Ltd.
132 Wickham Terrace
Fortitude Valley,
QLD 4006, Australia
info@secalerts.co
By using SecAlerts services, you agree to our services end-user license agreement. This website is safeguarded by reCAPTCHA and governed by the Google Privacy Policy and Terms of Service. All names, logos, and brands of products are owned by their respective owners, and any usage of these names, logos, and brands for identification purposes only does not imply endorsement. If you possess any content that requires removal, please get in touch with us.
© 2026 SecAlerts Pty Ltd.
ABN: 70 645 966 203, ACN: 645 966 203