Summary
n8n: Send Email Node Arbitrary File Read and SSRF via Nodemailer Content-Object Type Confusion
Workarounds
If upgrading is not immediately possible, administrators should consider the following temporary mitigations:
- Audit active workflows for Send Email nodes that map untrusted webhook or external data directly into the text or HTML body fields, and remove or restrict those workflows.
- Restrict public webhook access at the network or reverse-proxy level to prevent unauthenticated callers from reaching sensitive workflows.
- Restrict workflow creation and editing permissions to fully trusted users only.
These workarounds do not fully remediate the risk and should only be used as short-term mitigation measures.
Impact
The n8n Send Email node did not enforce that its message fields were strings, so a crafted untrusted non-string value from a workflow expression could be treated by the underlying mail library as a file path or URL. This could allow disclosure of local files on the n8n host.
Exploitation requires a pre-existing active workflow with an unauthenticated webhook, valid SMTP credentials configured on the Send Email node, and untrusted input mapped directly into the text or HTML body field. This is not a default n8n configuration.
An object is accessed using a type that is incompatible with its actual type, causing the runtime to interpret memory incorrectly. Typical impact: memory safety violations, unexpected behavior, or code execution.
Affected versions
Security releases
Kodem intelligence
Severity tells you how bad this could be in the worst case. It does not tell you whether you are exposed. Exploitability and impact are functions of runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A vulnerable package can sit in your dependency tree and never run.
Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter. Kodem's runtime-powered SCA identifies whether this CVE is reachable in your applications.
Already deployed Kodem?
See it in your environmentNew to Kodem? Get a demo →Remediation advice
The issue has been fixed in n8n versions 1.123.67, 2.31.5, and 2.32.1. Users should upgrade to one of these versions or later to remediate the vulnerability.
Frequently Asked Questions
- What is GHSA-2X35-3FW4-9JR4? GHSA-2X35-3FW4-9JR4 is a high-severity type confusion vulnerability in n8n (npm), affecting versions < 1.123.67. It is fixed in 1.123.67, 2.32.1, 2.31.5. An object is accessed using a type that is incompatible with its actual type, causing the runtime to interpret memory incorrectly.
- Which versions of n8n are affected by GHSA-2X35-3FW4-9JR4? n8n (npm) versions < 1.123.67 is affected.
- Is there a fix for GHSA-2X35-3FW4-9JR4? Yes. GHSA-2X35-3FW4-9JR4 is fixed in 1.123.67, 2.32.1, 2.31.5. Upgrade to this version or later.
- Is GHSA-2X35-3FW4-9JR4 exploitable, and should I be worried? Whether GHSA-2X35-3FW4-9JR4 is exploitable in your environment depends on whether the vulnerable code is present and reachable. A CVSS score is a worst-case rating; it does not account for your specific deployment, configuration, or usage patterns. Kodem, an Intelligent Application Security platform, uses runtime intelligence to show which vulnerabilities actually execute in production, so you can focus on the ones that represent real risk. Get a demo
- What actually determines whether GHSA-2X35-3FW4-9JR4 is exploitable, and how bad it is? Exploitability and impact are not fixed properties of a CVE. They depend on runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A high CVSS score on a dependency that never runs is not the same as real risk. Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter.
- How do I fix GHSA-2X35-3FW4-9JR4?
- Upgrade
n8nto 1.123.67 or later - Upgrade
n8nto 2.32.1 or later - Upgrade
n8nto 2.31.5 or later
- Upgrade