How severe is GHSA-7c4h-vh2m-743m?

No CVSS score has been assigned to GHSA-7c4h-vh2m-743m yet. Review the advisory details and affected package list to assess your exposure.

Which packages are affected by GHSA-7c4h-vh2m-743m?

GHSA-7c4h-vh2m-743m affects the following packages: n8n (npm). Ecosystems affected: npm.

How do I fix GHSA-7c4h-vh2m-743m?

Update n8n to 1.120.3 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-7c4h-vh2m-743m is resolved across your whole dependency graph.

How do I detect GHSA-7c4h-vh2m-743m in my npm dependencies?

Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for n8n. O3's reachability analysis confirms whether the vulnerable code path is actually invoked in your application, so you act on real exposure instead of every transitive match.

How do I mitigate GHSA-7c4h-vh2m-743m if there is no patch (or I can't update yet)?

If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.

How does O3 Security protect against GHSA-7c4h-vh2m-743m?

O3 pinpoints whether GHSA-7c4h-vh2m-743m is reachable in your code and exactly where to fix it, then blocks exploitation in production at runtime until the patched version is deployed.

Is GHSA-7c4h-vh2m-743m actively exploited in the wild?

No public exploit code has been indexed for GHSA-7c4h-vh2m-743m yet. This does not mean the vulnerability cannot be exploited — absence of public exploits does not imply safety. Apply the recommended fix and use O3 Security to monitor your exposure.

What is the EPSS score for GHSA-7c4h-vh2m-743m?

GHSA-7c4h-vh2m-743m has an EPSS (Exploit Prediction Scoring System) score of 1.3%, placing it in the 68th percentile of all CVEs. EPSS is maintained by FIRST.org and estimates the probability that a vulnerability will be exploited in the wild within the next 30 days. This score indicates relatively lower exploitation probability, though the CVSS severity should still guide your patching priority.

What type of vulnerability is GHSA-7c4h-vh2m-743m?

GHSA-7c4h-vh2m-743m is classified as Improper Input Validation (CWE-20), OS Command Injection (CWE-78). These weakness types describe the underlying flaw category, which helps determine the potential impact and the right class of mitigation. This is a high-impact weakness class that often enables remote code execution or data exposure.

When was GHSA-7c4h-vh2m-743m published, and has it been updated?

GHSA-7c4h-vh2m-743m was published on February 4, 2026 and was last updated on February 4, 2026. Advisory data evolves as severity scores, affected ranges, and exploit intelligence are revised — always check the latest version of the advisory before acting.

📦 npm

GHSA-7c4h-vh2m-743m

n8n Vulnerable to Command Injection in Community Package Installation

Also known asCVE-2026-21893

Published

Feb 4, 2026

Updated

Feb 4, 2026

Affected

1 pkg

Patched

1 / 1

Exploits

None indexed

EPSS Exploitation Probability

via FIRST.org ↗

1.3%probability of exploitation in next 30 days

Lower Risk68th percentile+1.12%

EPSS (Exploit Prediction Scoring System) is a daily probability model maintained by FIRST.org. It estimates the likelihood a CVE will be exploited in production environments within the next 30 days, derived from real-world threat intelligence signals.

Blast Radius

1 pkg affected

Weekly download volume for affected packages — a proxy for how broadly this vulnerability is deployed.

n8nnpm

91Kdownloads / 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

Detection & mitigation playbook

Open-source dependency

Detect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for n8n. O3's reachability analysis confirms whether the vulnerable code path is actually invoked in your application, so you act on real exposure instead of every transitive match.
Fix
Update n8n to 1.120.3 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-7c4h-vh2m-743m is resolved across your whole dependency graph.
Workarounds
If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.
How O3 protects you
O3 pinpoints whether GHSA-7c4h-vh2m-743m is reachable in your code and exactly where to fix it, then blocks exploitation in production at runtime until the patched version is deployed.

Tailored to GHSA-7c4h-vh2m-743m. Runtime protection reduces exposure until a permanent patch is applied and verified — it complements patching, it doesn't replace it.

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 GHSA-7c4h-vh2m-743m in your dependencies?

O3 detects GHSA-7c4h-vh2m-743m across npm dependencies and uses function-level reachability to confirm whether the vulnerable code path is actually reachable — not just present. No false positives.

Scan my dependencies How O3 SCA works