# CVE-2026-33720: n8n Has Authorization Bypass in OAuth Callback via N8N_SKIP_AUTH_ON_OAUTH_CALLBACK > Attackers can hijack OAuth tokens if a specific environment variable is enabled, allowing them to execute workflows as the victim. - **Severity:** Medium 6.3 (`CVSS:4.0/AV:N/AC:L/AT:P/PR:N/UI:N/VC:L/VI:L/VA:N/SC:L/SI:L/SA:N`) - **Exploited in the wild:** Not known - **Login needed:** Not needed - **Attackable:** Over the internet - **Victim action needed:** Not needed - **Fix available:** Yes - **Published:** 25 Mar 2026 - **Updated:** 25 Mar 2026 - **Also known as:** GHSA-vpgc-2f6g-7w7x ## What is CVE-2026-33720? CVE-2026-33720 is a medium-severity authentication bypass vulnerability in N8n N8n, published on 25 Mar 2026. An attacker can exploit it over the internet without logging in, with no action from the victim. ### Official description n8n is an open source workflow automation platform. Prior to version 2.8.0, 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 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 `N8N_SKIP_AUTH_ON_OAUTH_CALLBACK=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. Weakness: CWE-863 (Incorrect Authorization) ## Which versions are affected by CVE-2026-33720? 2 open source packages ship an affected version, including n8n. It affects 1 product. | Package | Ecosystem | Affected | Fixed in | | --- | --- | --- | --- | | `n8n` | npm | All versions | 2.8.0 | | `n8n` | npm | All versions | 2.8.0 | Products: N8n N8n. ## How do I fix CVE-2026-33720? Upgrade n8n to 2.8.0 or later. ## Is CVE-2026-33720 being exploited? There is no known exploitation of CVE-2026-33720 in the wild and no public exploit code. ## Other vulnerabilities in N8n N8n - [CVE-2025-68613](https://insights.sbomify.com/CVE-2025-68613/): n8n Improper Control of Dynamically-Managed Code Resources (critical 10.0, exploited in the wild) - [CVE-2026-21877](https://insights.sbomify.com/CVE-2026-21877/): n8n is vulnerable to Remote Code Execution via Arbitrary File Write (critical 10.0) - [CVE-2026-21858](https://insights.sbomify.com/CVE-2026-21858/): n8n Vulnerable to Unauthenticated File Access via Improper Webhook Request Handling (critical 10.0) - [CVE-2026-1470](https://insights.sbomify.com/CVE-2026-1470/): n8n Unsafe Workflow Expression Evaluation Allows Remote Code Execution (critical 9.9) - [CVE-2025-68668](https://insights.sbomify.com/CVE-2025-68668/): n8n Vulnerable to Arbitrary Command Execution in Pyodide based Python Code Node (critical 9.9) ## Fix prompt for AI coding agents ```text Check this codebase for CVE-2026-33720 and fix it if it is affected. What it is: CVE-2026-33720 is a medium-severity authentication bypass vulnerability in N8n N8n, published on 25 Mar 2026. An attacker can exploit it over the internet without logging in, with no action from the victim. Exploitation: There is no known exploitation of CVE-2026-33720 in the wild and no public exploit code. Affected packages and fixed versions: - n8n (npm): affected all versions; fixed in 2.8.0 - n8n (npm): affected all versions; fixed in 2.8.0 Task: 1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies. 2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it. 3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead. 4. Run the tests and summarise what changed and why. 5. If nothing in the project is affected, say so and change nothing. Reference: https://insights.sbomify.com/CVE-2026-33720/ (Markdown: https://insights.sbomify.com/CVE-2026-33720/index.md) ``` ## Sources - CVE record: https://www.cve.org/CVERecord?id=CVE-2026-33720 - NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-33720 - OSV: https://osv.dev/vulnerability/CVE-2026-33720 --- From sbomify Insights: https://insights.sbomify.com/CVE-2026-33720/ Summaries are generated and may contain mistakes; the official description above is the record.