Skip to main content
VulnerabilityPublished

CVE-2026-33720: n8n · Incorrect Authorization

Affects n8nSource CVE Database V5

0
Compare

Not known to be exploited · CVSS 6.3 Medium : upgrade to 2.8.0 when convenient.

Data as of 29 Oct 2026, 19:04 UTC

CVSS 4.0 base score
6.3Medium
How severe the flaw is on the 0–10 CVSS scale.
EPSS
0.1% chance of exploitation in 30 days – higher than 7% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
Patch
Available – fixed in 2.8.0
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

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 25 Mar 2026

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponized: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq Mirage: no evidence on record.

    No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 29 Oct 2026.

What to do

Upgrade n8n and n8n-io/n8n to 2.8.0.

Affected software

ProductAffectedFixed in
n8n-ion8nAffected
  • <2.8.0
Fixed in
  • 2.8.0
GitHubn8n-io/n8npkg:github/n8n-io/n8nOther threatsAffected
  • <2.8.0
Fixed in
  • 2.8.0

Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.

AI-suggested

  1. Upgrade all n8n instances to version 2.8.0 or later immediately to ensure the OAuth callback handler performs proper ownership verification.
  2. Audit current n8n deployments to identify if the environment variable N8N_SKIP_AUTH_ON_OAUTH_CALLBACK is set to true and disable it unless absolutely necessary.
  3. If disabling the environment variable is not feasible immediately, restrict access to the n8n instance by implementing strict network segmentation, IP whitelisting, and strong authentication controls to limit usage to fully trusted users only.
  4. Monitor OAuth flows and logs for unusual activity indicative of token misuse or unauthorized workflow executions.
  5. Educate users about phishing and social engineering risks that could lead to being tricked into completing malicious OAuth flows.
  6. Implement additional OAuth state parameter validation mechanisms if possible to detect anomalies.
  7. Regularly review and update workflow permissions and OAuth credential scopes to minimize potential damage from compromised tokens.

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.

References

Community reviews

Loading reviews…