Versions of command-exists before 1.2.4 are vulnerable to command injection.
Full advisory text at GitHub advisory.
npm package report
Is command-exists safe?
command-exists (npm) has 1 known vulnerability, the worst rated CRITICAL. Upgrade to 1.2.4 or later to clear it. No malicious-package signal is recorded.
// reach
0 direct dependencies
none carry a known advisory
Create a free accountfor every dependency path, dependent and what to upgrade
// ai model usage
Tracked for PyPI packages. HuggingFace models declare Python dependencies, so npm packages are not covered.
cvss
9.0
critical
severity band, no base score published
epss
not scored
chance of exploitation in 30 days
xyz score
5.0
medium
CyberXYZ composite out of 10
fig. 01 — GHSA-cff4-rrq6-h78w, the advisory selected below
// 1 advisories
Is command-exists safe to install?
CyberXYZ does not call a package safe in absolute terms. It records 1 known vulnerability for command-exists (npm), the worst rated CRITICAL, and no malicious-package signal. Whether it is acceptable depends on the version you run.
Does command-exists have known vulnerabilities?
Yes. CyberXYZ records 1 known vulnerability for command-exists (npm), the worst rated CRITICAL. They are GHSA-cff4-rrq6-h78w.
Which version of command-exists should I use?
1.2.4 or later clears every advisory recorded for command-exists (npm). Check the release you pick before installing it.
How do I check command-exists before installing?
Search command-exists in CyberXYZ Check at https://cyberxyz.io/check?q=command-exists. The xyz Scanner checks a project's dependencies, and CyberXYZ Proxy checks each package as it is installed.
Checked 2026-11-14 at 10:52 UTC. The most recent advisory here was published 2019-06-03. Updated continuously from NVD, GHSA, OSV and CNA feeds.