CVE-2026-21893: n8n Vulnerable to Command Injection in Community Package Installation

Published Feb 4, 2026
·
Updated

Impact A Command Injection vulnerability was identified in n8n’s community package installation functionality. The issue allowed authenticated users with administrative permissions to execute arbitrary system commands on the n8n host under specific conditions.

Important context

- Exploitation requires administrative access to the n8n instance. - The affected functionality is restricted to trusted users who are already permitted to install third-party community packages. - No unauthenticated or low-privilege exploitation is possible. - There is no evidence of exploitation in the wild.

Because administrative users can already extend n8n with custom or community code, the vulnerability does not meaningfully expand the threat model beyond existing administrator capabilities. However, it represents a violation of secure coding practices and has therefore been addressed.

Patches Users are advised to upgrade to n8n version 1.120.3 or later, which fully resolves the issue.

As a general security best practice, n8n instance owners should ensure that: - Administrative access is limited to trusted users only. - Community packages are installed only from trusted sources. - Instances are kept up to date with the latest security releases.

Other sources

n8n is an open source workflow automation platform. From version 0.187.0 to before 1.120.3, a command injection vulnerability was identified in n8n’s community package installation functionality. The issue allowed authenticated users with administrative permissions to execute arbitrary system commands on the n8n host under specific conditions. This issue has been patched in version 1.120.3.

MITRE

Affected Software

3 affected componentsFixes available
npm/n8n>=0.187.0<1.120.3
npm/n8n>=0.187.0<1.120.3
1.120.3
n8n N8n Node.js>=0.187.0<1.120.3

Event History

Feb 4, 2026
CVE Published
via MITRE·05:36 PM
Data Sourced
via MITRE·05:36 PM
DescriptionWeakness
Advisory Published
via GitHub·05:49 PM
Data Sourced
via GitHub·05:49 PM
DescriptionWeaknessAffected Software
Data Sourced
via NVD·06:16 PM
DescriptionSeverityWeakness
Data Sourced
via NVD·06:16 PM
RemedyAffected Software
Free Weekly Intel

Don't miss critical vulnerabilities

Join thousands of security professionals who receive our weekly digest of trending CVEs, zero-days, and exploited vulnerabilities.

No spam. Unsubscribe anytime.

Frequently Asked Questions

1

What is the severity of CVE-2026-21893?

CVE-2026-21893 is classified as a high-severity vulnerability due to its potential for arbitrary command execution.

2

What impact does CVE-2026-21893 have on affected systems?

CVE-2026-21893 allows authenticated users with administrative permissions to execute arbitrary system commands on the affected n8n instance.

3

How do I fix CVE-2026-21893?

To remediate CVE-2026-21893, upgrade to n8n version 1.120.3 or later.

4

Who is affected by CVE-2026-21893?

CVE-2026-21893 affects instances of n8n running versions between 0.187.0 and 1.120.3.

5

Can I still use n8n if I’m on a vulnerable version due to CVE-2026-21893?

If you are on a vulnerable version, it is recommended to avoid using community package installation features until you have upgraded to a secure version.

Contact

SecAlerts Pty Ltd.
132 Wickham Terrace
Fortitude Valley,
QLD 4006, Australia
info@secalerts.co
By using SecAlerts services, you agree to our services end-user license agreement. This website is safeguarded by reCAPTCHA and governed by the Google Privacy Policy and Terms of Service. All names, logos, and brands of products are owned by their respective owners, and any usage of these names, logos, and brands for identification purposes only does not imply endorsement. If you possess any content that requires removal, please get in touch with us.
© 2026 SecAlerts Pty Ltd.
ABN: 70 645 966 203, ACN: 645 966 203