CVE-2026-72766: n8n before 1.123.67 Arbitrary File Read via Send Email Node
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.
Affected Software
Remediation
Recommended actions to resolve this vulnerability, in priority order.
- Upgrade
Upgrade
n8nto a version that resolves this vulnerability.Fixed in 1.123.67 - Upgrade
Upgrade
n8nto a version that resolves this vulnerability.Fixed in 2.31.5 - Upgrade
Upgrade
n8nto a version that resolves this vulnerability.Fixed in 2.32.1
Event History
Frequently Asked Questions
What is the severity of CVE-2026-72766?
The severity of CVE-2026-72766 is rated at 40, indicating a high level of risk.
How do I fix CVE-2026-72766?
To fix CVE-2026-72766, upgrade n8n to version 1.123.67 or later, or to 2.31.5 or later.
What type of vulnerability is CVE-2026-72766?
CVE-2026-72766 is classified as a type confusion vulnerability related to SSRF in the Send Email node.
Which versions of n8n are affected by CVE-2026-72766?
CVE-2026-72766 affects n8n versions prior to 1.123.67, as well as 2.x prior to 2.31.5 and 2.32.x before 2.32.1.
What components of n8n does CVE-2026-72766 impact?
CVE-2026-72766 impacts the Send Email node, specifically regarding its handling of non-string message fields.