# CVE-2026-21893: n8n — Fixed in 1.120.3

📦 npm

Not in CISA KEV

# CVE-2026-21893 — n8n

[Fix: n8n-io/n8n@ae0669a](https://github.com/n8n-io/n8n/commit/ae0669a736cc496beeb296e115267862727ae838)

CVE-2026-21893 is a Improper Input Validation vulnerability in n8n. A fix is available for n8n — see the affected versions and patch details below.

n8n Vulnerable to Command Injection in Community Package Installation

Also known as[GHSA-7c4h-vh2m-743m](/vulnerability/GHSA-7c4h-vh2m-743m)

Published

Feb 4, 2026

Updated

Oct 28, 2026

Affected

1 pkg

Patched

1 / 1

Exploits

None indexed

Exploitation data as of Nov 10, 2026 · OSV.dev, NVD, FIRST.org (EPSS)

## Exploitation Status

### No confirmed exploitation observed yet

-   A successful exploit gives an attacker total control of the affected component, not partial access.
-   CISA’s own triage has not observed active exploitation or public proof-of-concept code for this CVE as of its last assessment.

Exploitation and automatability from CISA’s SSVC triage for CVE-2026-21893.

## EPSS Exploitation Probability

[via FIRST.org ↗](https://www.first.org/epss/)

1.5%probability of exploitation in next 30 days

Lower Risk0.00%

Lower risk than most CVEs75th percentile — riskier than 75% of all scored CVEsHighest risk

0.00%0.68%1.36%2.04%0.2%1.5%May 26Sep 26Nov 26

Probability of exploitation in the next 30 days, from [FIRST.org EPSS](https://www.first.org/epss/).

## Real-World Exposure

1 pkg affected

How broadly this vulnerability is actually deployed: weekly install volume shows current usage, and reverse-dependency count shows how many other packages break if it stays unpatched.

36other npm packages depend on this — each one inherits the vulnerability until it's patched upstream

`n8n`npm

150Kdownloads / week

## Description

#### 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.

## Affected Packages

1 total 1 fixed

Ecosystem

Package

Vulnerable range

Fix

📦npm

`n8n` 

≥ 0.187.0&&< 1.120.3

1.120.3`npm install n8n@1.120.3`

## Affected Products

1 product · 1 configurations

Application

`n8n`n8n

≥ 0.187.0 && < 1.120.3

range

## Detection & mitigation playbook

Open-source dependency

1.  ### Detect
    
    Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for n8n, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
    
2.  ### Fix
    
    Update n8n to 1.120.3 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2026-21893 is resolved across your whole dependency graph.
    
3.  ### Workarounds
    
    Stop passing untrusted input into the interpreter or shell: call the affected binary with an argument array rather than a composed command string, reject anything outside a strict allowlist of expected values, and run the component under an account that cannot reach beyond the work it legitimately does.
    

## Frequently Asked Questions

\### 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 wil

O3 Security · Impact-Aware SCA

### Is CVE-2026-21893 in your dependencies?

Find it across npm, including transitive dependencies.

[Scan my dependencies](/book-demo) [How O3 SCA works](/impact-aware-sca)