CVE-2026-53633: CWE-749: Exposed Dangerous Method or Function in vitest-dev vitest
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.
AI Analysis
Technical Summary
Vitest versions 3.0.0 up to but not including 3.2.5, versions before 4.1.8, and version 5.0.0-beta.4 exposed a cdp() API in Browser Mode that forwarded raw Chrome DevTools Protocol (CDP) methods without enforcing allowWrite or allowExec restrictions. This allowed a remote client with access to exposed browser API metadata to invoke CDP methods such as Page.setDownloadBehavior and Runtime.evaluate. Exploiting this, an attacker could overwrite the vite.config.ts file and execute arbitrary Node.js code on the host. The vulnerability is identified as CWE-749 (Exposed Dangerous Method or Function) and CWE-862 (Missing Authorization). The issue is fixed in Vitest versions 3.2.5, 4.1.8, and 5.0.0-beta.
Potential Impact
Successful exploitation allows an unauthenticated remote attacker to execute arbitrary Node.js code by leveraging the exposed cdp() API to overwrite configuration files and run attacker-controlled commands. This leads to full system compromise with high confidentiality, integrity, and availability impact as indicated by the CVSS score of 9.8.
Mitigation Recommendations
A fix is available in Vitest versions 3.2.5, 4.1.8, and 5.0.0-beta. Users should upgrade to these or later versions to remediate the vulnerability. There is no indication that temporary mitigations exist; upgrading is the recommended action.
CVE-2026-53633: CWE-749: Exposed Dangerous Method or Function in vitest-dev vitest
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.
CVSS v3.1
Score 9.8critical
Affected software
pkg:npm/vitest-dev/vitestRun on your own infrastructure? Check whether these packages are installed with threat-finder — our free open-source scanner.
AI-Powered Analysis
Machine-generated threat intelligence
Technical Analysis
Vitest versions 3.0.0 up to but not including 3.2.5, versions before 4.1.8, and version 5.0.0-beta.4 exposed a cdp() API in Browser Mode that forwarded raw Chrome DevTools Protocol (CDP) methods without enforcing allowWrite or allowExec restrictions. This allowed a remote client with access to exposed browser API metadata to invoke CDP methods such as Page.setDownloadBehavior and Runtime.evaluate. Exploiting this, an attacker could overwrite the vite.config.ts file and execute arbitrary Node.js code on the host. The vulnerability is identified as CWE-749 (Exposed Dangerous Method or Function) and CWE-862 (Missing Authorization). The issue is fixed in Vitest versions 3.2.5, 4.1.8, and 5.0.0-beta.
Potential Impact
Successful exploitation allows an unauthenticated remote attacker to execute arbitrary Node.js code by leveraging the exposed cdp() API to overwrite configuration files and run attacker-controlled commands. This leads to full system compromise with high confidentiality, integrity, and availability impact as indicated by the CVSS score of 9.8.
Mitigation Recommendations
A fix is available in Vitest versions 3.2.5, 4.1.8, and 5.0.0-beta. Users should upgrade to these or later versions to remediate the vulnerability. There is no indication that temporary mitigations exist; upgrading is the recommended action.
Technical Details
- Data Version
- 5.2
- Assigner Short Name
- GitHub_M
- Date Reserved
- 2026-06-09T20:16:59.647Z
- Cvss Version
- 3.1
- State
- PUBLISHED
- Remediation Level
- null
Threat ID: 6a56962968715ace431dcac6
Added to database: 07/14/2026, 20:03:53 UTC
Last enriched: 07/29/2026, 21:16:19 UTC
Last updated: 08/27/2026, 10:52:09 UTC
Views: 101
Community Reviews
0 reviewsCrowdsource mitigation strategies, share intel context, and vote on the most helpful responses. Sign in to add your voice and help keep defenders ahead.
Want to contribute mitigation steps or threat intel context? Sign in or create an account to join the community discussion.
Actions
Updates to AI analysis require Pro Console access. Upgrade inside Console → Billing.
Need more coverage?
Upgrade to Pro Console for AI refresh and higher limits.
For incident response and remediation, OffSeq services can help resolve threats faster.
Latest Threats
Check if your credentials are on the dark web
Instant breach scanning across billions of leaked records. Free tier available.