Versions of open before 6.0.0 are vulnerable to command injection when unsanitized user input is passed in.
Full advisory text at GitHub advisory.
npm package report
Is open safe?
open (npm) has 1 known vulnerability, the worst rated CRITICAL. Upgrade to 6.0.0 or later to clear it. No malicious-package signal is recorded.
// reach
8 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.5
medium
CyberXYZ composite out of 10
fig. 01 — GHSA-28xh-wpgr-7fm8, the advisory selected below
// 1 advisories
Is open safe to install?
CyberXYZ does not call a package safe in absolute terms. It records 1 known vulnerability for open (npm), the worst rated CRITICAL, and no malicious-package signal. Whether it is acceptable depends on the version you run.
Does open have known vulnerabilities?
Yes. CyberXYZ records 1 known vulnerability for open (npm), the worst rated CRITICAL. They are GHSA-28xh-wpgr-7fm8.
Which version of open should I use?
6.0.0 or later clears every advisory recorded for open (npm). Check the release you pick before installing it.
How do I check open before installing?
Search open in CyberXYZ Check at https://cyberxyz.io/check?q=open. The xyz Scanner checks a project's dependencies, and CyberXYZ Proxy checks each package as it is installed.
Checked 2026-11-14 at 07:03 UTC. The most recent advisory here was published 2019-06-20. Updated continuously from NVD, GHSA, OSV and CNA feeds.