| Component | n8n |
| Severity | high (CVSS 8.8) |
| CVSS vector | CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H |
| Published (NVD) | 2026-07-22 |
| Last modified | 2026-07-27 |
| Affected versions | n8n < 1.123.64 n8n < 1.123.64 n8n >= 2.0.0, < 2.29.8 n8n >= 2.0.0, < 2.29.8 n8n = 2.30.0 n8n = 2.30.0 |
| Fixed in | 1.123.64, 2.29.8 |
| Weakness | CWE-917 |
| CISA KEV | not listed |
NVD description
n8n contains a sanitizer bypass vulnerability in the legacy expression evaluator's computed-member handler. An authenticated user with workflow create or modify permissions can craft a malicious expression to bypass the sanitizer and achieve host-level code execution as the n8n process. The legacy expression engine is the default in affected versions. Fixed in n8n 1.123.64, 2.29.8, and 2.30.1.
What to do
- Upgrade n8n to
1.123.64or later (or the patched release of your branch: 2.29.8). - Do not expose the component's API or UI to the internet without authentication in front of it.
Sources
- NVD: CVE-2026-65591
- https://github.com/n8n-io/n8n/security/advisories/GHSA-pm35-fqvh-cq5g
- https://www.vulncheck.com/advisories/n8n-before-sanitizer-bypass-remote-code-execution
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...