# CVE-2026-53633: Vitest: Exposed Browser Mode API Can Proxy CDP and Overwrite Config Files, Leading to RCE

> Remote attackers can exploit exposed Browser Mode APIs to overwrite configuration files and execute arbitrary code in Vitest projects.

- **Severity:** Critical 9.8 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 14 Jul 2026
- **Updated:** 29 Jul 2026
- **Also known as:** CLSA-2026-1790459317, CLSA-2026-1792160942, CLSA-2026-1792160962, CLSA-2026-1792161477, CLSA-2026-1792161653, CLSA-2026-1792161665, CLSA-2026-1792161724, CLSA-2026-1792161771, CLSA-2026-1792161834, CLSA-2026-1792161880, CLSA-2026-1792161945, CLSA-2026-1792162013, CLSA-2026-1792162039, CLSA-2026-1792162063, GHSA-g8mr-85jm-7xhm, MINI-5wwf-2j35-h5vm, MINI-c2p9-6mfm-cp9w

## What is CVE-2026-53633?

CVE-2026-53633 is a critical code injection vulnerability in vitest-dev vitest, published on 14 Jul 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

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.

Weakness: CWE-862 (Missing Authorization), CWE-749 (Exposed Dangerous Method or Function)

## Which versions are affected by CVE-2026-53633?

8 open source packages ship an affected version, including @vitest/browser and vite-plus.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `@vitest/browser` | npm | From 3.0.0 | 3.2.5 |
| `@vitest/browser` | npm | From 3.0.0 | 3.2.5 |
| `@vitest/browser` | npm | From 4.0.0 | 4.1.8 |
| `@vitest/browser` | npm | From 4.0.0 | 4.1.8 |
| `@vitest/browser` | npm | From 5.0.0-beta.0 | 5.0.0-beta.4 |
| `@vitest/browser` | npm | From 5.0.0-beta.0 | 5.0.0-beta.4 |
| `vite-plus` | npm | All versions | 0.1.24 |
| `vite-plus` | npm | All versions | 0.1.24 |

## How do I fix CVE-2026-53633?

Upgrade @vitest/browser to a fixed version for your release line: 3.2.5, 4.1.8 or 5.0.0-beta.4.

## Is CVE-2026-53633 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-53633 exists.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-53633 and fix it if it is affected.

What it is: CVE-2026-53633 is a critical code injection vulnerability in vitest-dev vitest, published on 14 Jul 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-53633 exists.

Affected packages and fixed versions:
- @vitest/browser (npm): affected from 3.0.0; fixed in 3.2.5
- @vitest/browser (npm): affected from 3.0.0; fixed in 3.2.5
- @vitest/browser (npm): affected from 4.0.0; fixed in 4.1.8
- @vitest/browser (npm): affected from 4.0.0; fixed in 4.1.8
- @vitest/browser (npm): affected from 5.0.0-beta.0; fixed in 5.0.0-beta.4
- @vitest/browser (npm): affected from 5.0.0-beta.0; fixed in 5.0.0-beta.4
- vite-plus (npm): affected all versions; fixed in 0.1.24
- vite-plus (npm): affected all versions; fixed in 0.1.24

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-53633/ (Markdown: https://insights.sbomify.com/CVE-2026-53633/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-53633
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-53633
- OSV: https://osv.dev/vulnerability/CVE-2026-53633

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-53633/
Summaries are generated and may contain mistakes; the official description above is the record.