Search for packages
| purl | pkg:npm/n8n@2.9.3 |
| Vulnerability | Summary | Fixed by |
|---|---|---|
| This package is not known to be affected by vulnerabilities. | ||
| Vulnerability | Summary | Aliases |
|---|---|---|
| VCID-3bk2-zvud-c7et | n8n has Unauthenticated Expression Evaluation via Form Node A second-order expression injection vulnerability existed in n8n's Form nodes that could allow an unauthenticated attacker to inject and evaluate arbitrary n8n expressions by submitting crafted form data. When chained with an expression sandbox escape, this could escalate to remote code execution on the n8n host. The vulnerability requires a specific workflow configuration to be exploitable: 1. A form node with a field interpolating a value provided by an unauthenticated user, e.g. a form submitted value. 2. The field value must begin with an `=` character, which caused n8n to treat it as an expression and triggered a double-evaluation of the field content. For example, a workflow uses a multi-step Form where a downstream Form node renders user-provided input back in an HTML field and precedes it with an `=` sign: `=<h2>Thank you, {{ $input.first().json[\"Name\"] }}!</h2>` There is no practical reason for a workflow designer to prefix a field with `=` intentionally — the character is not rendered in the output, so the result would not match the designer's expectations. If added accidentally, it would be noticeable and very unlikely to persist. An unauthenticated attacker would need to either know about this specific circumstance on a target instance or discover a matching form by chance. Even when the preconditions are met, the expression injection alone is limited to data accessible within the n8n expression context. Escalation to remote code execution requires chaining with a separate sandbox escape vulnerability. Due to these real-world constraints — the unlikely workflow configuration, the need for an additional sandbox escape, and the difficulty of discovery — we have assessed the severity as High rather than Critical, diverging from the base CVSS score to better reflect actual exploitability. |
CVE-2026-27493
GHSA-75g8-rv7v-32f7 |
| VCID-axyq-35hd-skhq | n8n: Expression Sandbox Escape Leads to RCE Additional exploits in the expression evaluation of n8n have been identified and patched following [CVE-2025-68613](https://github.com/n8n-io/n8n/security/advisories/GHSA-v98v-ff95-f3cp). An authenticated user with permission to create or modify workflows could abuse crafted expressions in workflow parameters to trigger unintended system command execution on the host running n8n. |
CVE-2026-27577
GHSA-vpcf-gvg4-6qwr |
| VCID-dd53-wba6-f3c6 | n8n has Potential Remote Code Execution via Merge Node An authenticated user with permission to create or modify workflows could leverage the Merge node's SQL query mode to execute arbitrary code and write arbitrary files on the n8n server. |
CVE-2026-27497
GHSA-wxx7-mcgf-j869 |
| VCID-j3t9-jkr4-7fbc | n8n Vulnerable to Stored XSS via Various Nodes An authenticated user with permission to create or modify workflows could inject arbitrary scripts into pages rendered by the n8n application using different techniques on various nodes (Form Trigger node, Chat Trigger node, Send & Wait node, Webhook Node, and Chat Node). Scripts injected by a malicious workflow execute in the browser of any user who visits the affected page, enabling session hijacking and account takeover. |
CVE-2026-27578
GHSA-2p9h-rqjw-gm92 |
| VCID-ka79-3enj-fkew | n8n has Arbitrary File Read via Python Code Node Sandbox Escape An authenticated user with permission to create or modify workflows could use the Python Code node to escape the sandbox. The sandbox did not sufficiently restrict access to certain built-in Python objects, allowing an attacker to exfiltrate file contents or achieve RCE. On instances using internal Task Runners (default runner mode), this could result in full compromise of the n8n host. On instances using external Task Runners, the attacker might gain access to or impact other task executed on the Task Runner. - Task Runners must be enabled using `N8N_RUNNERS_ENABLED=true`. |
CVE-2026-27494
GHSA-mmgg-m5j7-f83h |
| VCID-srsg-ge6y-2ybu | n8n has an Authentication Bypass in its Chat Trigger Node When the Chat Trigger node is configured with n8n User Auth authentication, the authentication check could be circumvented. - This issue requires the Chat Trigger node to be configured with n8n User Auth authentication (non-default). |
GHSA-jh8h-6c9q-7gmw
|
| VCID-tfcu-w2ek-wkf9 | n8n has a Sandbox Escape in its JavaScript Task Runner An authenticated user with permission to create or modify workflows could exploit a vulnerability in the JavaScript Task Runner sandbox to execute arbitrary code outside the sandbox boundary. On instances using internal Task Runners (default runner mode), this could result in full compromise of the n8n host. On instances using external Task Runners, the attacker might gain access to or impact other task executed on the Task Runner. - Task Runners must be enabled using `N8N_RUNNERS_ENABLED=true`. |
CVE-2026-27495
GHSA-jjpj-p2wh-qf23 |