GHSA-2x35-3fw4-9jr4: n8n Send Email Node Arbitrary File Vulnerability

HIGH
Share
CWE-843 CWE-918 CWE-200
Published
Advisory Summary

GHSA-2x35-3fw4-9jr4 is a HIGH send email node arbitrary file vulnerability (CWE-843: Access of Resource Using Incompatible Type ('Type Confusion')) affecting n8n libraries in the npm ecosystem. The issue involves send email node arbitrary file read and ssrf via nodemailer content-object type confusion. Remediation is available by upgrading affected packages to version 1.123.67, 2.32.1, 2.31.5.

GHSA-2x35-3fw4-9jr4 at a Glance

CVE Identifier N/A
GHSA Identifier GHSA-2x35-3fw4-9jr4
Severity HIGH
CVSS v3.1 Base Score N/A
CWE Classification CWE-843: Access of Resource Using Incompatible Type ('Type Confusion')
Affected Product n8n
Package Ecosystem npm
Published Date
Last Updated

How to Fix GHSA-2x35-3fw4-9jr4

To remediate this vulnerability, upgrade all affected n8n dependencies to a patched release. Both direct and transitive dependencies should be checked, as frameworks or security libraries may pull in vulnerable versions transitively.

n8n fixed: 1.123.67 
npm install n8n@1.123.67
n8n fixed: 2.32.1 
npm install n8n@2.32.1
n8n fixed: 2.31.5 
npm install n8n@2.31.5
Verify Direct and Transitive Dependencies

Run the following command in your project directory to verify that all resolved dependencies use the patched release: 

npm ls n8n

How to Check if You Are Affected

To determine whether your Node.js application is affected by GHSA-2x35-3fw4-9jr4, inspect your project dependencies using npm:

npm ls n8n

Analyze the terminal output to locate any version of n8n in your dependency tree. If any resolved version matches the vulnerable ranges listed in the table below (for example, versions earlier than 1.123.67), your application is affected.

Note: The npm ls n8n command inspects dependencies declared in your package.json and lockfile; it does not perform automated runtime dynamic scanning.

Technical Details

Vulnerability Mechanism & Technical Analysis

This vulnerability is classified under CWE-843: Access of Resource Using Incompatible Type ('Type Confusion'), where the product allocates or initializes a resource such as a pointer, object, or variable using one type, but it later accesses that resource using a type that is incompatible with the original type. In n8n, software state validation or input boundaries are circumvented during processing. Review the official source advisory statement below for specific affected components, classes, and reproduction details.

Source Advisory Statement

## 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. ## Patches 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. ## 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.

GHSA-2x35-3fw4-9jr4 Affected n8n Versions

3 component(s)
Fixed Versions:
1.123.672.32.12.31.5
Product / Package Ecosystem Affected Versions Fixed Version
n8n
npm/n8n
npm
< 1.123.67
1.123.67
n8n
npm/n8n
npm
≥ 2.32.0
< 2.32.1
2.32.1
n8n
npm/n8n
npm
≥ 2.0.0-rc.0
< 2.31.5
2.31.5

References

GitHub Advisory / Wiki ADVISORY
https://github.com/n8n-io/n8n/security/advisories/GHSA-2x35-3fw4-9jr4
Security Fix Commit FIX COMMIT
https://github.com/n8n-io/n8n/commit/f69dfc6dd2178a14ea1624d2e1d403c2e755042f
n8n Source Repository REPOSITORY
https://github.com/n8n-io/n8n
n8n Release RELEASE
https://github.com/n8n-io/n8n/releases/tag/n8n@1.123.67
n8n Release RELEASE
https://github.com/n8n-io/n8n/releases/tag/n8n@2.31.5
n8n Release RELEASE
https://github.com/n8n-io/n8n/releases/tag/n8n@2.32.1

Frequently Asked Questions

What is GHSA-2x35-3fw4-9jr4?
GHSA-2x35-3fw4-9jr4 is a security vulnerability in n8n involving Send Email Node Arbitrary File Read and SSRF via Nodemailer Content-Object Type Confusion under CWE-843: Access of Resource Using Incompatible Type ('Type Confusion').
Which n8n versions are affected?
Affected versions include releases prior to 1.123.67, 2.32.1, 2.31.5 across affected packages: n8n.
What version fixes GHSA-2x35-3fw4-9jr4?
Upgrading to 1.123.67, 2.32.1, 2.31.5 (or the latest patched release for your respective branch) resolves the vulnerability.
Is n8n affected?
Yes, n8n is affected in releases prior to 1.123.67, 2.32.1, 2.31.5. Upgrade your dependency to 1.123.67, 2.32.1, 2.31.5 or later.
What CWE is associated with GHSA-2x35-3fw4-9jr4?
GHSA-2x35-3fw4-9jr4 is classified under CWE-843: Access of Resource Using Incompatible Type ('Type Confusion') (The product allocates or initializes a resource such as a pointer, object, or variable using one type, but it later accesses that resource using a type that is incompatible with the original type.).
How can I check npm dependencies for GHSA-2x35-3fw4-9jr4?
Run the dependency tree command: 'npm ls n8n'. This command lists direct and transitive dependencies in your build configuration so you can verify if a vulnerable version is resolved.
Machine-readable OSV JSON OSV v1.5 Schema
Normalized schema output
View Raw JSON 
{
  "schema_version" : "1.4.0",
  "id" : "GHSA-2x35-3fw4-9jr4",
  "modified" : "2026-07-22T22:09:11Z",
  "published" : "2026-07-22T22:09:11Z",
  "aliases" : [ ],
  "summary" : "n8n: Send Email Node Arbitrary File Read and SSRF via Nodemailer Content-Object Type Confusion",
  "details" : "## Impact\n\nThe 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.\n\nExploitation 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.\n\n## Patches\n\nThe 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.\n\n## Workarounds\n\nIf upgrading is not immediately possible, administrators should consider the following temporary mitigations:\n- 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.\n- Restrict public webhook access at the network or reverse-proxy level to prevent unauthenticated callers from reaching sensitive workflows.\n- Restrict workflow creation and editing permissions to fully trusted users only.\n\nThese workarounds do not fully remediate the risk and should only be used as short-term mitigation measures.",
  "severity" : [ {
    "type" : "CVSS_V4",
    "score" : "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"
  } ],
  "affected" : [ {
    "package" : {
      "ecosystem" : "npm",
      "name" : "n8n"
    },
    "ranges" : [ {
      "type" : "ECOSYSTEM",
      "events" : [ {
        "introduced" : "0"
      }, {
        "fixed" : "1.123.67"
      } ]
    } ]
  }, {
    "package" : {
      "ecosystem" : "npm",
      "name" : "n8n"
    },
    "ranges" : [ {
      "type" : "ECOSYSTEM",
      "events" : [ {
        "introduced" : "2.32.0"
      }, {
        "fixed" : "2.32.1"
      } ]
    } ]
  }, {
    "package" : {
      "ecosystem" : "npm",
      "name" : "n8n"
    },
    "ranges" : [ {
      "type" : "ECOSYSTEM",
      "events" : [ {
        "introduced" : "2.0.0-rc.0"
      }, {
        "fixed" : "2.31.5"
      } ]
    } ]
  } ],
  "references" : [ {
    "type" : "WEB",
    "url" : "https://github.com/n8n-io/n8n/security/advisories/GHSA-2x35-3fw4-9jr4"
  }, {
    "type" : "WEB",
    "url" : "https://github.com/n8n-io/n8n/commit/f69dfc6dd2178a14ea1624d2e1d403c2e755042f"
  }, {
    "type" : "PACKAGE",
    "url" : "https://github.com/n8n-io/n8n"
  }, {
    "type" : "WEB",
    "url" : "https://github.com/n8n-io/n8n/releases/tag/n8n@1.123.67"
  }, {
    "type" : "WEB",
    "url" : "https://github.com/n8n-io/n8n/releases/tag/n8n@2.31.5"
  }, {
    "type" : "WEB",
    "url" : "https://github.com/n8n-io/n8n/releases/tag/n8n@2.32.1"
  } ],
  "database_specific" : {
    "cwe_ids" : [ "CWE-200", "CWE-843", "CWE-918" ],
    "severity" : "HIGH",
    "github_reviewed" : true,
    "github_reviewed_at" : "2026-07-22T22:09:11Z",
    "nvd_published_at" : null
  }
}