CVE-2026-72766: Access of Resource Using Incompatible Type ('Type Confusion') in n8n-io n8n
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.
AI Analysis
Technical Summary
CVE-2026-72766 is a type confusion vulnerability in the n8n Send Email node affecting versions prior to 1.123.67, 2.31.5, and 2.32.1. The vulnerability arises because the node does not enforce that message fields are strings. An attacker supplying a crafted non-string value via a workflow expression into the text or HTML body fields can cause the underlying Nodemailer library to interpret these values as file paths or URLs. This can lead to arbitrary local file disclosure and server-side request forgery (SSRF). Successful 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, which is not the default configuration.
Potential Impact
If exploited, this vulnerability can allow an attacker to disclose local files on the server or perform server-side request forgery (SSRF) via the Send Email node in n8n. However, exploitation requires a specific and non-default configuration, including an active workflow with an unauthenticated webhook and valid SMTP credentials. There are no known exploits in the wild as of the publication date.
Mitigation Recommendations
Patch status is not yet confirmed — check the vendor advisory for current remediation guidance. Until an official fix is available, 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.
CVE-2026-72766: Access of Resource Using Incompatible Type ('Type Confusion') in n8n-io n8n
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.
CVSS v4.0
Score 8.2high
Affected software
pkg:github/n8n-io/n8nRun on your own infrastructure? Check whether these packages are installed with threat-finder — our free open-source scanner.
AI-Powered Analysis
Machine-generated threat intelligence
Technical Analysis
CVE-2026-72766 is a type confusion vulnerability in the n8n Send Email node affecting versions prior to 1.123.67, 2.31.5, and 2.32.1. The vulnerability arises because the node does not enforce that message fields are strings. An attacker supplying a crafted non-string value via a workflow expression into the text or HTML body fields can cause the underlying Nodemailer library to interpret these values as file paths or URLs. This can lead to arbitrary local file disclosure and server-side request forgery (SSRF). Successful 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, which is not the default configuration.
Potential Impact
If exploited, this vulnerability can allow an attacker to disclose local files on the server or perform server-side request forgery (SSRF) via the Send Email node in n8n. However, exploitation requires a specific and non-default configuration, including an active workflow with an unauthenticated webhook and valid SMTP credentials. There are no known exploits in the wild as of the publication date.
Mitigation Recommendations
Patch status is not yet confirmed — check the vendor advisory for current remediation guidance. Until an official fix is available, 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.
Technical Details
- Data Version
- 5.2
- Assigner Short Name
- VulnCheck
- Date Reserved
- 2026-08-10T15:06:16.417Z
- Cvss Version
- 4.0
- State
- PUBLISHED
- Remediation Level
- null
Threat ID: 6a7b1519bf8831d539b28a61
Added to database: 08/11/2026, 12:27:05 UTC
Last enriched: 08/11/2026, 12:42:22 UTC
Last updated: 08/11/2026, 19:00:13 UTC
Views: 4
Community Reviews
0 reviewsCrowdsource mitigation strategies, share intel context, and vote on the most helpful responses. Sign in to add your voice and help keep defenders ahead.
Want to contribute mitigation steps or threat intel context? Sign in or create an account to join the community discussion.
Actions
Updates to AI analysis require Pro Console access. Upgrade inside Console → Billing.
Need more coverage?
Upgrade to Pro Console for AI refresh and higher limits.
For incident response and remediation, OffSeq services can help resolve threats faster.
Latest Threats
Check if your credentials are on the dark web
Instant breach scanning across billions of leaked records. Free tier available.