Skip to main content
VulnerabilityPublished

CVE-2026-103252: n8n · Insecure Direct Object Reference

Affects n8nSource CVE Database V5

0
Compare

Not known to be exploited · CVSS 7.1 High · fixed in 2.40.1 : patch n8n soon.

Data as of 15 Nov 2026, 20:25 UTC

CVSS 4.0 base score
7.1High
How severe the flaw is on the 0–10 CVSS scale.
EPSS
0.2% chance of exploitation in 30 days – higher than 19% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
Patch
Available – fixed in 2.40.1, 2.39.6, 1.123.80
CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:H/VI:N/VA:N/SC:L/SI:N/SA:N

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 1 Oct 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 15 Nov 2026.

What to do

Upgrade n8n and n8n-io/n8n to 2.40.1, 2.39.6 or 1.123.80.

Affected software

ProductAffectedFixed in
n8n-ion8nAffected
  • >=2.40.0 <2.40.1
Fixed in
  • 2.40.1
n8n-ion8nAffected
  • >=2.0.0 <2.39.6
Fixed in
  • 2.39.6
n8n-ion8nAffected
  • <1.123.80
Fixed in
  • 1.123.80
GitHubn8n-io/n8npkg:github/n8n-io/n8nOther threatsAffected
  • <1.123.80
  • >=2.0.0 <2.39.6
  • >=2.40.0 <2.40.1
Fixed in
  • 1.123.80
  • 2.39.6
  • 2.40.1

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

AI-suggested

Users should upgrade n8n to versions 1.123.80 or later, 2.39.6 or later, or 2.40.1 or later where this vulnerability is fixed. Since this is a software vulnerability with fixed versions available, applying the official patches is the recommended remediation. No vendor advisory content was provided to indicate otherwise.

Description

n8n versions before 1.123.80, from 2.0.0 before 2.39.6, and from 2.40.0 before 2.40.1 contain an authorization bypass vulnerability in the credential test endpoint that resolves project-scoped variables without validating caller access. Attackers can specify an arbitrary project ID in the request body to interpolate sensitive variables into credential test requests sent to attacker-controlled hosts for exfiltration.

References

Community reviews

Loading reviews…