Skip to content
Patch Next
Sign inAdd to your agent

← Actionable
Critical, CVSS 9.4amended

@vitest/browser: Browser Mode provider commands bypass the file-access permission gate

CVE-2026-73653GHSA-p63j-vcc4-9vmv

What to do

Vendor fix available. Upgrade each affected package to the fixed version on its release line (@vitest/browser 5.0.0-beta.6, 4.1.10, 3.2.7), redeploy, then verify what is actually installed.

This page has no inventory attached, so it cannot say whether you are affected. A vendor fix is not proof that your deployment is fixed.

Add to your agent

Affected packages

  • npm @vitest/browser

    Affected
    >= 4.0.0, < 4.1.10< 3.2.7>= 5.0.0-beta.1, < 5.0.0-beta.6
    Fixed in
    5.0.0-beta.6, 3.2.7, 4.1.10

Sources

Severity and exploitation
Exploitation
No confirmed exploitation recorded. Patch Next marks exploitation only from CISA KEV.
CVSS
9.4 · CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:L
EPSS
  • CVE-2026-73653: 0.79% estimated exploitation activity in the next 30 days; percentile 56.31 (FIRST EPSS, 2026-11-03). This is a model estimate, not proof of exploitation or customer exposure.
Source description

As published by the source; long descriptions are shortened.

Summary Browser Mode exposes a set of built-in "commands" that run on the Node.js side of the test runner and can touch the local filesystem (taking screenshots, managing Playwright traces, uploading files for <input type="file", comparing screenshots). Several of these commands accept a file path from the browser and act on it without checking the allowWrite permission gate and without confining the path to the project directory. A client that can reach the Browser Mode API can therefore read, create, overwrite, or delete files anywhere the Vitest process can access, even when allowWrite is false. This matters most when the Browser Mode API is exposed to the network (for example test.api.host is set, or the dev server is reachable from another machine or origin). In that configuration allowWrite defaults to false precisely to block file access, and these commands bypass that protection. On a default localhost-only setup with trusted test code, there is no untrusted party in a…

Dates and revisions
Published by the source
Last modified by the source
Source last checked
  1. Revision 3 · amended ·

    Amended from ghsa record GHSA-p63j-vcc4-9vmv

  2. Revision 2 · amended ·

    Amended from osv record GHSA-p63j-vcc4-9vmv

  3. Revision 1 · created ·

    Published from ghsa record GHSA-p63j-vcc4-9vmv

Agent brief

Preview the exact text before you copy it. Commands are read-only suggestions; review them before running anything.

# Patch Next advisory brief: CVE-2026-73653

Advisory: @vitest/browser: Browser Mode provider commands bypass the file-access permission gate
IDs: CVE-2026-73653, GHSA-p63j-vcc4-9vmv
Record: https://patchnext.com/advisories/cve-2026-73653 (revision 3, source checked 26 Oct 2026, 13:01 UTC)
Inventory: none attached. This brief comes from a public page and does not say whether any deployment is affected.
Severity: Critical (CVSS 9.4)
Exploitation: no confirmed exploitation recorded. Patch Next confirms exploitation only from CISA KEV.
Vendor response: Vendor fix available; fixed versions by package: @vitest/browser 5.0.0-beta.6, 4.1.10, 3.2.7. A vendor fix does not mean a deployment is fixed.

## Affected components
- npm @vitest/browser: affected >= 4.0.0, < 4.1.10; < 3.2.7; >= 5.0.0-beta.1, < 5.0.0-beta.6; fixed in 5.0.0-beta.6, 3.2.7, 4.1.10

## Suggested inspection (read-only)
- `npm ls @vitest/browser --all`: lists every installed copy and version, including transitive ones. Run in the project root after `npm ci`.

## Supported action
Upgrade each affected component to a fixed version on its release line. For a transitive dependency, upgrade the parent package or add an override or constraint, then regenerate the lockfile. Redeploy every environment that ran an affected version.

## Required regression checks
- Run the test suite and a production build.
- Exercise the features that depend on @vitest/browser.
- Repeat the inspection and confirm that only fixed versions remain installed.

## Rollback considerations
- Keep the previous lockfile and deployment artifact. Rolling back reinstates the vulnerable version, so apply any documented mitigation while you fix forward.

## Unresolved questions
- Which deployments run an affected version?
- Exploitation status can change. Check again before lowering the priority.
- Mark the work resolved only after the fixed version is verified in production.

## Sources
- Verified: https://github.com/advisories/GHSA-p63j-vcc4-9vmv (GitHub-reviewed advisory GHSA-p63j-vcc4-9vmv lists affected ranges: npm @vitest/browser >=4.0.0 =0 =5.0.0-beta.1 <5.0.0-beta.6)
- Verified: https://osv.dev/vulnerability/GHSA-p63j-vcc4-9vmv (OSV record GHSA-p63j-vcc4-9vmv lists affected ranges: npm @vitest/browser >=4.0.0 =0 =5.0.0-beta.1 <5.0.0-beta.6 (fixed))

Commands are suggestions: review each one before running it.

Loading voting…