EUVD-2026-56145
GHSA-9x27-5f6j-72hw
Severity by source
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/E:X/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:X
AC:H reflects the mandatory non-default configuration prerequisite; S:C and C:H capture cross-system SSRF reach and full local file disclosure impact.
Primary rating from Vendor (VulnCheck).
CVSS VectorVendor: VulnCheck
Lifecycle Timeline
4DescriptionCVE.org
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.
AnalysisAI
Type confusion in the Send Email node of the n8n workflow automation platform allows an attacker-supplied non-string expression value to pass uncoerced into Nodemailer, which then interprets it as a file path or URL rather than literal email content - enabling arbitrary local file disclosure and server-side request forgery (SSRF). Affected are n8n versions before 1.123.67, 2.x before 2.31.5, and 2.32.x before 2.32.1, as confirmed by GitHub Security Advisory GHSA-2x35-3fw4-9jr4. No public exploit code has been identified at time of analysis, and the vulnerability is not listed in the CISA KEV catalog; exploitation depends on a specific non-default workflow configuration that requires an unauthenticated webhook, pre-configured SMTP credentials, and direct mapping of untrusted input into the email body field.
Technical ContextAI
The root cause is CWE-843 (Access of Resource Using Incompatible Type - type confusion), arising because the n8n Send Email node fails to enforce that workflow expression outputs bound to the text or HTML body fields are coerced to JavaScript strings before being forwarded to Nodemailer. Nodemailer's content object model accepts either a plain string for email body content or a structured object that can reference a file path or URL for attachment or inline content; by omitting string enforcement at the expression evaluation boundary, n8n inadvertently allows a crafted expression result to be treated as the latter form. This is a flaw in n8n's input handling layer, not in Nodemailer itself - Nodemailer is behaving as designed. The affected package is npm/n8n across three version branches (CPE: cpe:2.3:a:n8n-io:n8n:*:*:*:*:*:*:*:*), and the fix commit (f69dfc6dd2178a14ea1624d2e1d403c2e755042f) enforces string coercion before the value reaches the mail library.
RemediationAI
Upgrade n8n to version 1.123.67 or later (stable branch), 2.31.5 or later (2.x branch), or 2.32.1 or later (2.32.x branch), as confirmed by GitHub Security Advisory GHSA-2x35-3fw4-9jr4 and patch commit f69dfc6dd2178a14ea1624d2e1d403c2e755042f. The vendor advisory is at https://github.com/n8n-io/n8n/security/advisories/GHSA-2x35-3fw4-9jr4. If immediate upgrading is not possible, administrators should audit all active workflows containing Send Email nodes and identify any that map untrusted webhook or external data directly into the text or HTML body fields without string coercion, then disable or restructure those specific workflows - this removes the exploitable data path without requiring downtime. Restricting public webhook access at the network perimeter or reverse-proxy layer (e.g., requiring VPN or IP allowlisting) prevents unauthenticated external callers from triggering vulnerable workflows, though this does not address insider-threat or misconfigured internal-network scenarios. Limiting workflow creation and editing permissions to a small set of fully trusted users reduces the surface area for accidental introduction of vulnerable patterns. The vendor explicitly notes that none of these workarounds fully remediate the risk and they should only be used as short-term measures until patching is possible.
n8n workflow automation (through 1.121.2) allows authenticated users to execute arbitrary code via the n8n service, with
n8n workflow automation (1.65.0 to 1.121.0) allows unauthenticated file access through form-based workflows. A critical
n8n has a fifth critical RCE vulnerability (CVSS 9.9) in the Expression evaluator, enabling code execution through craft
A prototype pollution vulnerability in the XML and GSuiteAdmin nodes of n8n workflow automation platform allows authenti
An authenticated user with workflow creation or modification privileges in n8n workflow automation platform can exploit
n8n-workflows Main Commit ee25413 allows attackers to execute a directory traversal via the download_workflow function w
Authenticated n8n users can hijack administrator accounts when LDAP authentication is enabled by manipulating their LDAP
The n8n package 0.218.0 for Node.js allows Escalation of Privileges. Rated high severity (CVSS 8.8), this vulnerability
SQL injection in n8n's Data Table Get node allows authenticated users with workflow modification permissions to execute
Authenticated users can exploit string formatting and exception handling in n8n's Python task executor to escape sandbox
n8n workflow automation platform Community Edition contains an authorization bypass vulnerability allowing authenticated
The n8n package 0.218.0 for Node.js allows Information Disclosure. Rated high severity (CVSS 7.5), this vulnerability is
Same technique Memory Corruption
View allShare
External POC / Exploit Code
Leaving vuln.today