Skip to main content
VulnerabilityPublished Updated

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

Affects n8nSource CVE Database V5

0
Compare

Not known to be exploited · CVSS 7.2 High : upgrade to 1.123.67 soon.

Data as of 10 Nov 2026, 23:24 UTC

CVSS 4.0 base score
7.2High
How severe the flaw is on the 0–10 CVSS scale.

Thin evidence

One scorer or none
CVSS scores by source
CNA (VulnCheck)CVSS 4.07.2
EPSS
0.3% chance of exploitation in 30 days – higher than 29% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
Patch
Available – fixed in 1.123.67, 2.32.1, 2.31.5
CVSS:4.0/AV:N/AC:L/AT:P/PR:L/UI:N/VC:H/VI:N/VA:N/SC:H/SI:H/SA:L

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 11 Aug 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 10 Nov 2026.

What to do

Upgrade to a fixed release listed under Affected software.

Affected software

ProductAffectedFixed in
n8n-ion8nAffected
  • <1.123.67
Fixed in
  • 1.123.67
n8n-ion8nAffected
  • >=2.32.0 <2.32.1
Fixed in
  • 2.32.1
n8n-ion8nAffected
  • >=2.0.0-rc.0 <2.31.5
Fixed in
  • 2.31.5
GitHubn8n-io/n8npkg:github/n8n-io/n8nOther threatsAffected
  • <1.123.67
  • <2.31.5
  • <2.32.1
Fixed in
  • 1.123.67
  • 2.31.5
  • 2.32.1
npmn8npkg:npm/n8nOther threatsAffected
  • <1.123.67
  • >=2.32.0 <2.32.1
  • >=2.0.0-rc.0 <2.31.5
Fixed in
  • 1.123.67
  • 2.32.1
  • 2.31.5

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

AI-suggested

If you cannot patch yet, restrict Editor access to trusted users only and avoid sharing workflows that contain sensitive credentials.

Description

n8n before 1.123.67, 2.31.5, and 2.32.1 validates credential-access only for a node's top-level credentials and not for credentials referenced inside an Execute Sub-workflow node's inline workflow JSON. A member with Editor access to a shared workflow (when workflow sharing is enabled) who knows a target credential's ID can reference that credential in the inline JSON; it passes save-time and runtime validation and resolves in the parent workflow's project context, allowing the attacker to use or exfiltrate credentials they are not permitted to access.

References

Community reviews

Loading reviews…