global-modules-path (npm) has 1 known vulnerability, the worst rated CRITICAL. Upgrade to 3.0.0 or later to clear it. No malicious-package signal is recorded.
0 direct dependencies
none carry a known advisory
Tracked for PyPI packages. HuggingFace models declare Python dependencies, so npm packages are not covered.
CVSS v3.1 base score out of 10
chance of exploitation in 30 days, 75th percentile of all CVEs
CyberXYZ composite out of 10
fig. 01 — GHSA-vvj3-85vf-fgmw, the advisory selected below
Versions of the package global-modules-path before 3.0.0 are vulnerable to Command Injection due to missing input sanitization or other checks and sandboxes…
Full advisory text at GitHub advisory or NVD.
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
CyberXYZ does not call a package safe in absolute terms. It records 1 known vulnerability for global-modules-path (npm), the worst rated CRITICAL, and no malicious-package signal. Whether it is acceptable depends on the version you run.
Yes. CyberXYZ records 1 known vulnerability for global-modules-path (npm), the worst rated CRITICAL. They are GHSA-vvj3-85vf-fgmw.
3.0.0 or later clears every advisory recorded for global-modules-path (npm). Check the release you pick before installing it.
Search global-modules-path in CyberXYZ Check at https://cyberxyz.io/check?q=global-modules-path. The xyz Scanner checks a project's dependencies, and CyberXYZ Proxy checks each package as it is installed.
Checked 2026-11-14 at 03:30 UTC. The most recent advisory here was published 2023-01-13. Updated continuously from NVD, GHSA, OSV and CNA feeds.