CVE-2026-33720

Workarounds

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

• Avoid enabling N8N_SKIP_AUTH_ON_OAUTH_CALLBACK=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.

When the N8N_SKIP_AUTH_ON_OAUTH_CALLBACK 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 N8N_SKIP_AUTH_ON_OAUTH_CALLBACK=true is explicitly configured (non-default).

The application does not correctly enforce access controls, allowing a principal to access resources or operations beyond their granted permissions. Typical impact: unauthorized data access or execution of privileged operations.

CVE-2026-33720 has a CVSS score of 4.7 (Medium). The vector is network-reachable, no privileges required, and user interaction required. A CVSS score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether this affects your application depends on whether the vulnerable code is present and reachable in your environment. A fixed version is available (2.8.0); upgrading removes the vulnerable code path.

Kodem intelligence

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

1. What is CVE-2026-33720? CVE-2026-33720 is a medium-severity incorrect authorization vulnerability in n8n (npm), affecting versions < 2.8.0. It is fixed in 2.8.0. The application does not correctly enforce access controls, allowing a principal to access resources or operations beyond their granted permissions.
2. How severe is CVE-2026-33720? CVE-2026-33720 has a CVSS score of 4.7 (Medium). This score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether it represents real risk in your environment depends on whether the vulnerable code is present and reachable.
3. Which versions of n8n are affected by CVE-2026-33720? n8n (npm) versions < 2.8.0 is affected.
4. Is there a fix for CVE-2026-33720? Yes. CVE-2026-33720 is fixed in 2.8.0. Upgrade to this version or later.
5. Is CVE-2026-33720 exploitable, and should I be worried? Whether CVE-2026-33720 is exploitable in your environment depends on whether the vulnerable code is present and reachable. A CVSS score is a worst-case rating; it does not account for your specific deployment, configuration, or usage patterns. Kodem, an Intelligent Application Security platform, uses runtime intelligence to show which vulnerabilities actually execute in production, so you can focus on the ones that represent real risk. Get a demo
6. What actually determines whether CVE-2026-33720 is exploitable, and how bad it is? Exploitability and impact are not fixed properties of a CVE. They depend on runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A high CVSS score on a dependency that never runs is not the same as real risk. Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter.
7. How do I fix CVE-2026-33720? Upgrade n8n to 2.8.0 or later.