Is CVE-2026-53633 exploited in the wild?

No. Junglewise Threat Intelligence has no report of CVE-2026-53633 being exploited in the wild.

How severe is CVE-2026-53633?

Critical severity, with a CVSS score of 9.8, published 14 July 2026.

Which products and versions are affected?

@vitest/browser (npm) SEMVER:introduced=5.0.0-beta.0,fixed=5.0.0-beta.4; vite-plus (npm) <= 0.1.23, SEMVER:introduced=0,fixed=0.1.24.

Is there a fix for CVE-2026-53633?

Yes. @vitest/browser (npm): upgrade to 5.0.0-beta.4 or later; vite-plus (npm): upgrade to 0.1.24 or later. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.

How is CVE-2026-53633 attacked?

It is attacked over the network, in a software library.

Am I affected by CVE-2026-53633?

Check whether you run @vitest/browser (npm) or vite-plus (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.

CVE-2026-53633: Vitest remote code execution in Browser Mode cdp API

Q: Is there a fix for CVE-2026-53633?

Yes. @vitest/browser (npm): upgrade to 5.0.0-beta.4 or later; vite-plus (npm): upgrade to 0.1.24 or later. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.

Q: How is CVE-2026-53633 attacked?

It is attacked over the network, in a software library.

Q: Am I affected by CVE-2026-53633?

Check whether you run @vitest/browser (npm) or vite-plus (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.

CVE-2026-53633 · Severity: critical · CVSS 9.8 · Published 2026-07-14

Vitest is a testing framework used by developers to verify their code. A vulnerability in its Browser Mode allows remote attackers to bypass security restrictions and execute malicious code on a developer's machine. This could lead to full system compromise, data theft, or unauthorized modification of project configuration files.

Technologies: @vitest/browser (npm), vite-plus (npm). Vendors: npm.

Quick answers

Is CVE-2026-53633 exploited in the wild?: No. Junglewise Threat Intelligence has no report of CVE-2026-53633 being exploited in the wild.
How severe is CVE-2026-53633?: Critical severity, with a CVSS score of 9.8, published 14 July 2026.
Which products and versions are affected?: @vitest/browser (npm) SEMVER:introduced=5.0.0-beta.0,fixed=5.0.0-beta.4; vite-plus (npm) <= 0.1.23, SEMVER:introduced=0,fixed=0.1.24.
Is there a fix for CVE-2026-53633?: Yes. @vitest/browser (npm): upgrade to 5.0.0-beta.4 or later; vite-plus (npm): upgrade to 0.1.24 or later. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
How is CVE-2026-53633 attacked?: It is attacked over the network, in a software library.
Am I affected by CVE-2026-53633?: Check whether you run @vitest/browser (npm) or vite-plus (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 5.0.0-beta.4 or later
```
npm install @vitest/browser@5.0.0-beta.4
```
vite-plus (npm): upgrade to 0.1.24 or later
```
npm install vite-plus@0.1.24
```

Technical details

A vulnerability exists in Vitest Browser Mode where the cdp() API forwarded raw Chrome DevTools Protocol (CDP) methods without being gated by allowWrite or allowExec security configurations. A remote client with access to browser API metadata could utilize CDP methods such as Page.setDownloadBehavior and Runtime.evaluate to overwrite the vite.config.ts file. This leads to the execution of attacker-controlled Node.js code. The issue is classified under CWE-749 (Exposed Dangerous Method or Function) and CWE-862 (Missing Authorization). Patches are available in versions 3.2.5, 4.1.8, and 5.0.0-beta.4.

Affected products

vitest-dev vitest >= 3.0.0, < 3.2.5
vitest-dev vitest >= 4.0.0, < 4.1.8
vitest-dev vitest >= 5.0.0-beta.0, < 5.0.0-beta.4

Identifiers

CVE-2026-53633
GHSA-g8mr-85jm-7xhm

Timeline

2026-07-14: advisory: NVD publication date
2026-05-28: patched: Fixes committed to repository

References

This page as Markdown. Free to reuse under CC BY 4.0 with a link back.