Quick answers
- Is CVE-2026-73653 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-73653 being exploited in the wild.
- How severe is CVE-2026-73653?
- Low severity, with a CVSS score of 3.1, published 21 July 2026.
- Which products and versions are affected?
- @vitest/browser (npm) SEMVER:introduced=4.0.0,fixed=4.1.10.
- Is there a fix for CVE-2026-73653?
- Yes. @vitest/browser (npm): upgrade to 4.1.10 or later. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
- How is CVE-2026-73653 attacked?
- It is attacked over the network.
- Am I affected by CVE-2026-73653?
- Check whether you run @vitest/browser (npm) at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.
How to fix
- @vitest/browser (npm): upgrade to 4.1.10 or later
npm install @vitest/browser@4.1.10
Technical details
Vitest Browser Mode exposes Node.js-side provider commands (upload, takeScreenshot, screenshotMatcher, stopChunkTrace, deleteTracing, annotateTraces) that perform file operations without enforcing the allowWrite permission gate or confining paths to the project directory. The vulnerability is a missing authorization check (CWE-862) combined with path traversal (CWE-22), allowing arbitrary file read/write/delete via client-supplied paths and traversal sequences. Attack requires network access to the Browser Mode API; no authentication or user interaction is required. The fix adds allowWrite checks and path confinement to the project root for all file-touching commands. Patches are available in v3.2.7, v4.1.10, and v5.0.0-beta.6.
Affected products
- Vitest Browser <3.2.7, >=4.0.0 <4.1.10, >=5.0.0-beta.1 <5.0.0-beta.6
Identifiers
- CVE-2026-73653
- GHSA-p63j-vcc4-9vmv
Timeline
- 2026-07-21: disclosed
- 2026-07-21: patched: Fixed in v3.2.7, v4.1.10, v5.0.0-beta.6