UTC
High

Gmail and Brevo nodes accept non-string content, enabling local file read and SSRF

GHSA-95ph-833c-4wrp · published 2026-08-19

Severity
High
CVSS score
7.1
Chance of exploitation (EPSS)
No CVE
Fixed in
2.36.2
What it is

The Gmail (v1) and Brevo nodes passed message content to the mail composer without ensuring it was a string. An expression resolving to an object could carry a path or href property, which the composer used to read a local file or fetch a URL and attach the result to the outgoing message. An authenticated user able to run a workflow could read any file the n8n process could access or reach an internal address.

What to do

Upgrade n8n to 2.36.2 or later. If you start it from an MCP config with npx or uvx, pin that version so an old cached copy is not used.

The issue has been fixed in n8n versions 1.123.73, 2.35.4, and 2.36.2. Users should upgrade to one of these versions or later to remediate the vulnerability.

If you cannot upgrade yet

If upgrading is not immediately possible, administrators should consider the following temporary mitigations: Restrict n8n instance access to fully trusted users only. Disable the Gmail node by adding n8n-nodes-base.gmail to the NODES_EXCLUDE environment variable. Ensure the n8n process runs under a dedicated low-privilege OS user account to limit the impact of any file access. These workarounds do not fully remediate the risk and should only be used as short-term mitigation measures.

Affected
PackageRegistryAffectedFixed in
n8nnpm< 1.123.731.123.73
n8nnpm< 2.35.42.35.4
n8nnpm< 2.36.22.36.2

The impact, patch and workaround text comes from the advisory, shortened (published by n8n). Proof-of-concept and reproduction sections and code are left out; the original advisory has them.

Sources: GitHub Advisory Database, reviewed and malware advisories (CC BY 4.0, https://github.com/advisories); advisories published by Cursor (https://github.com/cursor/cursor/security/advisories); advisories published by OpenClaw (https://github.com/openclaw/openclaw/security/advisories); advisories published by vLLM (https://github.com/vllm-project/vllm/security/advisories); advisories published by Open WebUI (https://github.com/open-webui/open-webui/security/advisories); advisories published by n8n (https://github.com/n8n-io/n8n/security/advisories); advisories published by Flowise (https://github.com/FlowiseAI/Flowise/security/advisories); advisories published by Langflow (https://github.com/langflow-ai/langflow/security/advisories); advisories published by the MCP Python SDK project (https://github.com/modelcontextprotocol/python-sdk/security/advisories); advisories published by MLflow (https://github.com/mlflow/mlflow/security/advisories); CISA Known Exploited Vulnerabilities catalog (CC0). Data as of 2026-11-22. ShieldMap describes how each problem works and how to fix it; it does not publish exploit code. Report a correction to [email protected].