Skip to main content
VulnerabilityPublished Updated

CVE-2026-72766: n8n · Type Confusion

Affects n8nSource CVE Database V5

0
Compare

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

Data as of 9 Nov 2026, 23:24 UTC

CVSS 4.0 base score
8.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.08.2
EPSS
0.4% chance of exploitation in 30 days – higher than 38% 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:N/UI:N/VC:H/VI:N/VA:N/SC:L/SI:N/SA:N

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 9 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, avoid using untrusted input directly in the Send Email node's message fields, especially in workflows with unauthenticated webhooks and configured SMTP credentials. Review and restrict workflow configurations to prevent exposure of these conditions.

Description

n8n before 1.123.67, 2.x before 2.31.5, and 2.32.x before 2.32.1 contain a type confusion vulnerability in the Send Email node, which does not enforce that its message fields are strings. A crafted non-string value supplied from a workflow expression into the text or HTML body field can be interpreted by the underlying mail library (Nodemailer) as a file path or URL, allowing arbitrary local file disclosure and server-side request forgery (SSRF). Exploitation requires a pre-existing active workflow with an unauthenticated webhook, valid SMTP credentials configured on the node, and untrusted input mapped directly into the body field; this is not a default configuration.

References

Community reviews

Loading reviews…