Vulnerability in @vitest/browser (CVE-2026-53633)
Summary
Vulnerability in @vitest/browser (CVE-2026-53633). Successful exploitation can lead to full system takeover. Exploitable via browser.api.allowWrite. Mitigation: upgrade to 3.2.5 or later.
Original description
The description as published by the source.
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.
Source: GitHub Security Advisories (Global) NVD GitHub Advisory
Auto-generated summary
Assembled by SecPulse from the source data (CVSS, CWE, affected versions) using templates — no AI involved. Check the original description and references below for exact details.
A vulnerability tracked as CVE-2026-53633 has been found in @vitest/browser.
Attackers can target a specific entry point like browser.api.allowWrite over the network to misuse the product.
Successful exploitation can lead to full system takeover. CVSS score: 9.8/10.
What to do: upgrade @vitest/browser to 3.2.5 or later.
If unsure, ask your IT team or search "@vitest/browser CVE-2026-53633" on the vendor's site.
CVE-2026-53633 (@vitest/browser) — CWE-749 / CVSS v3 9.8
Attack vector: remote (network-reachable) / unauthenticated / no user interaction
Attack surface: browser.api.allowWrite / browser.api.allowExec / api.allowWrite / api.allowExec
Patched: 3.2.5 — apply immediately
Plan: 1) Audit SBOM/dependencies, 2) Stage→prod upgrade, 3) Add WAF/proxy monitoring on affected endpoints, 4) Hunt IOCs in logs.
Refs: see the GHSA / vendor advisory / patched release linked on this page.
A vulnerability (CWE-749) exists in @vitest/browser. Attackers reach the vulnerable code path via browser.api.allowWrite without authentication.
Check the vendor advisory for the affected versions of @vitest/browser. Attack surface: browser.api.allowWrite / browser.api.allowExec / api.allowWrite / api.allowExec.
Severity: Critical (CVSS 9.8/10). Successful exploitation can lead to full system takeover.
Update to 3.2.5.
Until the patch is applied: disable the affected feature, apply WAF rules, or restrict access via network ACLs.
Search webserver/proxy logs for unusual request patterns matching this CVE's known IOCs. Run grep -r '@vitest/browser' . against your dependency files (package-lock.json, requirements.txt, go.sum) to find affected services.
Response actions
Concrete steps and command examples for SOC/SRE teams to execute in order
-
1Identify exposure identify
grep -r '@vitest/browser' . | grep -v node_modulesリポジトリと本番環境の依存ファイル (package-lock.json / requirements.txt / go.sum / Gemfile.lock 等) で
@vitest/browserを grep し、稼働しているサービス・バージョンを把握する。 -
2Apply patch patch
Upgrade @vitest/browser to 3.2.5ステージング環境で 3.2.5 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスを含めること。
-
3Post-deployment verification verify
Confirm patched version is live in productionパッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番ではアクセスログ・WAF でアラート再発が無いか継続監視。
Affected packages
References
- advisory github.com
- advisory nvd.nist.gov
- advisory github.com
- package github.com
- patch github.com
- patch github.com
- patch github.com
- patch github.com
- patch github.com
- patch github.com
- web github.com
- web github.com
- web github.com
- web github.com