| Component | n8n |
| Severity | high (CVSS 8.1) |
| CVSS vector | CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:H/A:H |
| Published (NVD) | 2026-08-11 |
| Last modified | 2026-09-18 |
| Affected versions | n8n < 1.123.67 n8n >= 2.0.0, < 2.31.5 n8n = 2.32.0 |
| Fixed in | 1.123.67, 2.31.5 |
| Weakness | CWE-1321 |
| CISA KEV | not listed |
NVD description
n8n before 1.123.67, 2.31.5, and 2.32.1 contains a prototype pollution vulnerability in the VM expression engine. An authenticated user able to create or edit a workflow expression can abuse the engine's array-element access to obtain a reference to a host built-in and pollute its prototype in the main n8n process (a sandbox escape), leading to a denial of service. Both self-hosted and cloud instances running the VM expression engine are affected.
What to do
- Upgrade n8n to
1.123.67or later (or the patched release of your branch: 2.31.5). - Do not expose the component's API or UI to the internet without authentication in front of it.
Sources
- NVD: CVE-2026-72769
- https://github.com/n8n-io/n8n/security/advisories/GHSA-hx4h-vr3m-45vh
- https://www.vulncheck.com/advisories/n8n-before-prototype-pollution-via-vm-expression-engine
Read more
Other n8n CVEs
n8n versions before 1.123.80 contain a credential tampering vulnerability where duplicate node IDs bypass the workflow credential tamper gua...
n8n versions before 1.123.80, from 2.0.0 before 2.39.6, and from 2.40.0 before 2.40.1 contain a stored DOM cross-site scripting vulnerabilit...
n8n versions before 1.123.80, from 2.0.0 before 2.39.6, and from 2.40.0 before 2.40.1 contain a path traversal vulnerability in the Supabase...
n8n versions before 2.39.6 and 2.40.0 before 2.40.1 fail to validate credential ownership during inline agent node-tool introspection. Attac...
n8n versions before 1.123.80, from 2.0.0 before 2.39.6, and from 2.40.0 before 2.40.1 contain a filter injection vulnerability in the Supaba...
n8n versions before 1.123.80, from 2.0.0 before 2.39.6, and from 2.40.0 before 2.40.1 contain a NoSQL injection vulnerability in the MongoDB...