vitest (npm) has 3 known vulnerabilities, the worst rated CRITICAL. Upgrade to 5.0.0-rc.2 or later to clear all of them. No malicious-package signal is recorded.
52 packages depend on it
an advisory here reaches each of them
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, 64th percentile of all CVEs
CyberXYZ composite out of 10
fig. 01 — GHSA-5xrq-8626-4rwp, the advisory selected below
Arbitrary file can be read on Windows when Vitest UI server is listening, especially when exposed to the network.
Full advisory text at GitHub advisory, NVD or OSV.
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 3 known vulnerabilities for vitest (npm), the worst rated CRITICAL, and no malicious-package signal. Whether it is acceptable depends on the version you run.
Yes. CyberXYZ records 3 known vulnerabilities for vitest (npm), the worst rated CRITICAL. They are GHSA-5xrq-8626-4rwp, GHSA-9crc-q9x8-hgqq, GHSA-82fw-gwwq-j7x9.
5.0.0-rc.2 or later clears every advisory recorded for vitest (npm). Check the release you pick before installing it.
Search vitest in CyberXYZ Check at https://cyberxyz.io/check?q=vitest. The xyz Scanner checks a project's dependencies, and CyberXYZ Proxy checks each package as it is installed.
Checked 2026-11-14 at 10:27 UTC. The most recent advisory here was published 2026-09-08. Updated continuously from NVD, GHSA, OSV and CNA feeds.