Critical· 9.8official fix available
CVE-2026-53633
A security flaw in the Vitest testing framework allows remote users to execute unauthorized code. This occurs because certain browser testing features do not properly restrict commands sent to the browser.
publishedJul 14, 2026
last modifiedJul 29, 2026
sourcesNVD
severity · cvss
9.8
critical · how bad it is
exploitation · epss
<1%
44th percentile · chance of exploitation in 30 days
(ai-assisted) A model wrote this summary from the official data, so double-check it against the source before you act on it. Read the official advisory →
auto-deletes from the system
counting…on Aug 28, 2026
An official fix is available, so this entry is kept for 30 days and then removed automatically.
01
Who is affected
Users of Vitest versions 3.0.0 through 3.2.5, 4.1.8, and 5.0.0-beta.4 that utilize Vitest Browser Mode.
02
Real-world impact
An attacker could overwrite your project's configuration files and run malicious Node.js code on your system.
03
Why this severity
This is a critical vulnerability because it allows a remote attacker to take control of the system without needing any special permissions or user interaction.
04
What to do about it
official fix available
recommended steps
- 01Upgrade Vitest to version 3.2.5 or later.
- 02Upgrade Vitest to version 4.1.8 or later.
- 03Upgrade Vitest to version 5.0.0-beta or later.
NVD-referenced vendor advisory
05
Timeline
- Jul 14, 2026 · 16d agoPublishedDisclosed and added to the National Vulnerability Database.
- Jul 29, 2026 · 17h agoAdvisory updatedThe NVD record was last revised.
- Jul 29, 2026 · 16h agoOfficial fix availableA vendor patch or mitigation now exists — see the remediation steps above.
06
How it’s attacked
Attack vectorNetwork (remote)
Attack complexityLow
Privileges requiredNone
User interactionNone needed
ScopeUnchanged
Confidentiality impactHigh
Integrity impactHigh
Availability impactHigh
07
References & advisories
- github.com/vitest-dev/vitest/commit/38…
- github.com/vitest-dev/vitest/commit/63…
- github.com/vitest-dev/vitest/commit/e4…
- github.com/vitest-dev/vitest/pull/1044…
- github.com/vitest-dev/vitest/pull/1045…
- github.com/vitest-dev/vitest/pull/1045…
- github.com/vitest-dev/vitest/releases/…
- github.com/vitest-dev/vitest/releases/…
- github.com/vitest-dev/vitest/releases/…
- github.com/vitest-dev/vitest/security/…
(ai-assisted) A model wrote this summary from the official data, so double-check it against the source before you act on it. Read the official advisory →