dbcve.org
CWE-749Weakness · CWE-749

CVE-2026-53633

CRITICAL · 9.8 CVSS v3.1 Published 2026-07-14
Patch available
A vendor patch is available. No clean upgrade release — apply the published patch.
See remediation →
100/100
Remediation priority · Urgent
Remotely reachable No privileges Zero-click Patch available 5 weeks old

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
Vitest is a testing framework powered by Vite. From 3.0.0 until 3.2.5, 4.1.8, and 5.0.0-beta.4, Vitest Browser Mode exposed a cdp() API that forwarded raw Chrome DevTools Protocol methods without being gated by allowWrite or allowExec, allowing a remote client with exposed browser API metadata to use CDP Page.setDownloadBehavior and Runtime.evaluate to overwrite vite.config.ts and execute attacker-controlled Node.js code. This issue is fixed in versions 3.2.5, 4.1.8, and 5.0.0-beta.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · high confidence

Vitest Browser Mode exposes a cdp() API that forwards raw Chrome DevTools Protocol methods without being gated by allowWrite or allowExec controls. This allows a remote attacker with exposed browser API metadata to use CDP methods (Page.setDownloadBehavior and Runtime.evaluate) to overwrite vite.config.ts and execute arbitrary Node.js code on the server.

MitigationUpgrade Vitest to version 3.2.5, 4.1.8, or 5.0.0-beta or later. If immediate upgrading is not feasible, disable Vitest Browser Mode and ensure the Vitest server is not exposed to untrusted networks.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
Low
Privileges
None
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Identify installed Vitest version
    Run 'npm list vitest' or check package.json dependencies to determine the exact version of Vitest installed in your project
    Affected if Version is lower than 3.2.5, 4.1.8, or 5.0.0-beta (or if the version cannot be determined)
  2. Verify Browser Mode configuration
    Search for 'browser: true' in vitest.config.ts, vitest.config.js, or vitest.workspace.ts files, and check if the project uses @vitest/browser package
    Affected if Browser Mode is enabled (browser: true setting exists in Vitest configuration)
  3. Check Vitest server network exposure
    Examine configuration for 'host: true' or similar settings in vitest.config, and review startup scripts for --host flag or exposed port configurations
    Affected if The Vitest server is configured to listen on network interfaces accessible to untrusted networks (host binding to non-localhost)
  4. Inspect allowWrite and allowExec settings
    Review vitest.config.ts for allowFiles, allowWrite, or allowExec options under browser configuration to see if they are properly restricted
    Affected if allowWrite or allowExec controls are not explicitly configured or are set to permissive values (such as allowing arbitrary file writes)
  5. Check for exposed browser API metadata
    Review network configuration and determine if Vitest's browser API endpoints (typically on port 5173 or configured port) are accessible from untrusted networks
    Affected if Vitest server with Browser Mode is exposed to the internet or untrusted internal networks

A user is affected if they are running Vitest versions below 3.2.5/4.1.8/5.0.0-beta with Browser Mode enabled and the server is network-exposed, allowing remote attackers to leverage the unrestricted cdp() API.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

dbcve · scoped
Patch available Apply the vendor patch
Vendor patch github.com →
Interim mitigation

Upgrade Vitest to version 3.2.5, 4.1.8, or 5.0.0-beta or later. If immediate upgrading is not feasible, disable Vitest Browser Mode and ensure the Vitest server is not exposed to untrusted networks.

Recommended fix High confidence

Upgrade to Vitest 3.2.5 (for 3.x users), 4.1.8 (for 4.x users), or 5.0.0-beta (for 5.x beta users)

  1. Check the currently installed Vitest version by running `npm list vitest` or viewing package.json
  2. Determine which major version branch you are currently on (3.x, 4.x, or 5.x)
  3. Upgrade to the appropriate fixed version: run `npm install [email protected]` for 3.x users, `npm install [email protected]` for 4.x users, or `npm install [email protected]` for 5.x beta users
  4. After upgrading, verify the new version is installed with `npm list vitest`
  5. Test that your existing test suite runs correctly with the updated version
  6. If using Browser Mode, ensure the cdp() API now properly enforces allowWrite/allowExec restrictions
Caveat Review Vitest changelogs between your current version and the target fixed version for any breaking changes to Browser Mode or configuration APIs

Generated from the published advisory — verify against the referenced sources before acting.

Have this fixed Scoped from the published advisory
  • Consultation2.0 h
  • Implementation2.0 h
  • Testing3.0 h
  • Review / QA1.0 h
8.0 hours of engineering $1,390
Get the patch applied

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,224.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-53633 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2026-53633 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data