N8n vulnerabilities
We track 9 vulnerabilities in N8n products. 9 are rated high or critical, and none are known to be exploited. The most recent was published on July 8, 2026.
Latest N8n vulnerabilities
- 8.8 High severity
n8n: Improper Neutralization of Special Elements used in an SQL Command
n8n before 1.123.61, 2.x before 2.27.4, and 2.28.x before 2.28.1 contains a SQL injection vulnerability in the legacy MySQL v1 node's executeQuery operation. The operation substitutes evaluated {{ ... }} expression values directly into the raw SQL string witho
- 7.4 High severity
n8n: Incorrect Authorization
n8n before 1.123.55, 2.25.7, and 2.26.2 contains an authorization bypass in the POST /workflows/{workflowId}/test-runs/new endpoint, which authorizes access using the workflow:read scope instead of workflow:execute. An authenticated user with read-only access
- 8.8 High severity
n8n: Improper Access Control
The Execute Command node in n8n allows authenticated users to execute arbitrary commands on the host system where n8n runs. Attackers with user access or compromised credentials can exploit this node to run malicious commands, potentially leading to data exfil
- 7.7 High severity
n8n: Improper Authorization
n8n before 2.8.0 contains an authentication bypass vulnerability allowing authenticated SSO users to disable SSO enforcement through the API. Attackers can create local password credentials to authenticate directly, bypassing organizational SSO policies and id
- 9.6 Critical severity
n8n: Improper Neutralization of Special Elements used in an SQL Command
n8n before version 2.4.0 contains a sql injection vulnerability in MySQL, PostgreSQL, and Microsoft SQL nodes that allows authenticated users to inject arbitrary SQL through unescaped identifier values in node configuration parameters. Attackers with workflow
- 9.9 Critical severity
n8n: Server-Side Request Forgery
n8n before 2.20.0 contains a credential exfiltration vulnerability in the POST /rest/dynamic-node-parameters/options endpoint that allows authenticated users to bypass Allowed HTTP Request Domains restrictions. Attackers with credential access can cause the n8
- 9.9 Critical severity
N8n: Improper Neutralization of Directives in Dynamically Evaluated Code
n8n contains a critical Remote Code Execution (RCE) vulnerability in its workflow Expression evaluation system. Expressions supplied by authenticated users during workflow configuration may be evaluated in an execution context that is not sufficiently isolated
- 9.9 Critical severity
N8n: Improper Control of Generation of Code
Using string formatting and exception handling, an attacker may bypass n8n's python-task-executor sandbox restrictions and run arbitrary unrestricted Python code in the underlying operating system. The vulnerability can be exploited via the Code block by an au
- 8.8 High severity
N8n: Unrestricted Upload of File with Dangerous Type
An arbitrary file upload vulnerability in the Chat Trigger component of N8N v1.95.3, v1.100.1, and v1.101.1 allows attackers to execute arbitrary code via uploading a crafted HTML file.