CVE-2026-21893
Command Injection in n8n Community Package Allows Remote Code Execution
Publication date: 2026-02-04
Last updated on: 2026-02-20
Assigner: GitHub, Inc.
Description
Description
CVSS Scores
EPSS Scores
| Probability: | |
| Percentile: |
Meta Information
Affected Vendors & Products
| Vendor | Product | Version / Range |
|---|---|---|
| n8n | n8n | From 0.187.0 (inc) to 1.120.3 (exc) |
Helpful Resources
Exploitability
| CWE ID | Description |
|---|---|
| CWE-20 | The product receives input or data, but it does not validate or incorrectly validates that the input has the properties that are required to process the data safely and correctly. |
| CWE-78 | The product constructs all or part of an OS command using externally-influenced input from an upstream component, but it does not neutralize or incorrectly neutralizes special elements that could modify the intended OS command when it is sent to a downstream component. |
Attack-Flow Graph
AI Powered Q&A
Can you explain this vulnerability to me?
This vulnerability is a command injection issue found in the n8n workflow automation platform, specifically in its community package installation functionality. It affects versions from 0.187.0 up to but not including 1.120.3. Authenticated users with administrative permissions could exploit this flaw to execute arbitrary system commands on the host running n8n under certain conditions.
How can this vulnerability impact me? :
The vulnerability allows an attacker with administrative access to run arbitrary system commands on the server hosting n8n. This could lead to full system compromise, unauthorized data access, data modification, disruption of services, or further attacks within the network.
How does this vulnerability affect compliance with common standards and regulations (like GDPR, HIPAA)?:
I don't know
How can this vulnerability be detected on my network or system? Can you suggest some commands?
I don't know
What immediate steps should I take to mitigate this vulnerability?
To mitigate this vulnerability, upgrade the n8n platform to version 1.120.3 or later, where the command injection issue has been patched.
Ensure that only trusted users have administrative permissions, as the vulnerability requires authenticated users with such permissions to exploit.