CVE-2026-53633
Vitest Browser Mode exposes CDP allowing remote RCE via overwritten vite.config.ts
Is CVE-2026-53633 being exploited?
Not confirmed. CVE-2026-53633 does not appear in CISA's Known Exploited Vulnerabilities catalog, which records only exploitation that has been observed and reported publicly. That is evidence of absence of a report, not evidence the flaw is unattacked. EPSS currently estimates a 0.90% probability of exploitation in the next 30 days.
How severe is CVE-2026-53633?
CVE-2026-53633 is rated Critical with a CVSS score of 9.8. Severity describes how bad exploitation would be, not how likely it is: pair it with exploitation evidence before deciding what to patch first.
Is there a patch for CVE-2026-53633?
Yes. A fix has been recorded for CVE-2026-53633. The vendor advisory is the authority on the exact fixed version — apply it from there rather than from a summary.
What does CVE-2026-53633 affect?
CVE-2026-53633 affects Vitest Browser Mode, Vitest v3.0.0–<3.2.5, Vitest v4.0.0–<4.1.8, Vitest v5.0.0-beta <5.0.0-beta.4. Confirm the exact affected versions against the vendor advisory before deciding you are exposed.
What should I do about CVE-2026-53633?
Upgrade to 3.2.5, 4.1.8 or >=5.0.0-beta.4; restrict CDP exposure; avoid Browser Mode on untrusted hosts
Exploitation status reflects CISA's KEV catalog as we last synced it. Check the catalog directly.
Remote code execution via Chrome DevTools Protocol; attacker can overwrite vite.config.ts and execute arbitrary Node.js code.
Immediate action required
- affected>= 3.0.0 and < 3.2.5
- affected>= 4.0.0 and < 4.1.8
- affected>= 5.0.0-beta.0 and < 5.0.0-beta.4
As published in the CVE Program record. A version outside these ranges is not a statement that it is unaffected — vendors sometimes understate a range, and distribution-backported builds carry upstream numbers that do not reflect what was patched into them.