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.
Fix
Patch, vendor advisory and mitigation references on NVD 1
- https://github.com/n8n-io/n8n/security/advisories/GHSA-2x35-3fw4-9jr4 Vendor Advisory, Mitigation
Every line above is quoted from NVD, CISA, Microsoft, the vendor's own advisory or DISA; nothing is generated.
Change history 1
- First seenCVSS 8.2 · n8nNVD modified 2026-10-23 19:10
Affected (CPE criteria) 4
cpe:2.3:a:n8n:n8n:*:*:*:*:community:node.js:*:*cpe:2.3:a:n8n:n8n:*:*:*:*:enterprise:node.js:*:*cpe:2.3:a:n8n:n8n:2.32.0:*:*:*:community:node.js:*:*cpe:2.3:a:n8n:n8n:2.32.0:*:*:*:enterprise:node.js:*:*
References 2
- https://github.com/n8n-io/n8n/security/advisories/GHSA-2x35-3fw4-9jr4 Vendor Advisory, Mitigation
- https://www.vulncheck.com/advisories/n8n-before-arbitrary-file-read-via-send-email-node Third Party Advisory