Your RSA-2048 keys break in 2030. Find every one of them before attackers do.
📦
📦 npm
Not in CISA KEV
CRITICAL severity

OS Command Injection in strong-nginx-controllerGHSA-4v9w-pvwr-38h3

CRITICAL

GHSA-4v9w-pvwr-38h3 is a critical-severity (CVSS 9.8) OS Command Injection vulnerability in strong-nginx-controller. No vendor fix is recorded yet; mitigation options are listed below.

Also known asCVE-2020-7621SNYK-JS-STRONGNGINXCONTROLLER-564248
Published
Updated
Affected
1 pkg
Patched
See advisory
Exploits
None indexed
Exploitation data as of Oct 10, 2026 · OSV.dev, NVD, FIRST.org (EPSS)

EPSS Exploitation Probability

via FIRST.org ↗
3.0%probability of exploitation in next 30 days
Lower Risk0.00%
Lower risk than most CVEs87th percentile — riskier than 87% of all scored CVEsHighest risk
1.24%2.00%2.76%3.52%1.7%3.0%Apr 26Aug 26Oct 26

Probability of exploitation in the next 30 days, from FIRST.org EPSS.

How urgent is this, really

GHSA-4v9w-pvwr-38h3 by exploitation likelihood (EPSS) against impact (CVSS). Outside the shaded patch-first corner.

Where this sits among everything scored

Of 385,386 CVEs with a current EPSS score, this one falls in the < 10% band (highlighted). Counts from FIRST.org, log-scaled.

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.

1other npm packages depend on this — each one inherits the vulnerability until it's patched upstream
strong-nginx-controllernpm
168downloads / week

Description

strong-nginx-controller through 1.0.2 is vulnerable to Command Injection. It allows execution of arbitrary command as part of the '_nginxCmd()' function.

Affected Packages

1 total
EcosystemPackageVulnerable rangeFix
📦npmstrong-nginx-controllerall versionsNo fix

Affected Products

1 product · 1 configurations
Application
strongloop nginx controlleribm
≤ 1.0.2
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 strong-nginx-controller, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.

  2. Remediation status

    No patched version of strong-nginx-controller has shipped for GHSA-4v9w-pvwr-38h3 yet. Where your build allows, override or pin the dependency away from the vulnerable range, and apply any maintainer-recommended mitigation.

  3. Mitigate without a patch

    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

strong-nginx-controller through 1.0.2 is vulnerable to Command Injection. It allows execution of arbitrary command as part of the '_nginxCmd()' function.
O3 Security · Impact-Aware SCA

Is GHSA-4v9w-pvwr-38h3 in your dependencies?

Find it across npm, including transitive dependencies.

Scan my dependencies How O3 SCA works