Medium, CVSS 6.5npmAmendedPublished
Vitest: Servers misapply server.fs.deny, serving .env, private keys, .git, and the API token file
CVE-2026-112948 · GHSA-p458-7748-mcp3
- Affected
- npm @vitest/ui >= 5.0.0-beta.6, < 5.0.5
- Fixed in
- 5.0.5· Vendor fix available
- Issue
- In Vitest 5, Vite's server.fs.deny is not applied as intended on Vitest's dev servers. Depending on the server, files that Vite refuses to serve by default (such as .env, private keys and certificates, .npmrc, and .git) or Vitest's own API token file (.vitest-secret-token) can be read over plain HTTP by a client that can reach the server. In Browser Mode with test.projects, a malicious website can also read .env values through the developer's browser. This only applies when Vitest runs an HTTP server, which happens with the UI (--ui), Browser Mode, or api enabled. Plain vitest and vitest run don't listen on any port and are not affected. The fix ships in vitest, and @vitest/ui and @vitest/browser are listed because they are what enables the affected setups. Both pin vitest to the same version as a peer dependency, so upgrading either one also requires the patched vitest. Users who enable api without @vitest/ui or @vitest/browser are also affected and should upgrade vitest.…
Recommended action: Upgrade to 5.0.5 or later, then redeploy and verify.A vendor fix does not resolve your finding until you verify it in your own systems.