Skip to content
Fencer Intel
critical 9.8

CVE-2026-53633 json

Vitest: Exposed Browser Mode API Can Proxy CDP and Overwrite Config Files, Leading to RCE

published 5mo ago modified 18d ago also EUVD-2026-44403 , GHSA-g8mr-85jm-7xhm

cvss
9.8
version 3.1, CNA
cisa kev
Not listed
not in CISA's catalog
epss
0.9%
EPSS 0.9% chance of exploitation in 30 days, percentile 59%
public exploits
0
none known

Summary

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.

Patch / fix

  • npm @vitest/browser 3.2.5, 4.1.8, 5.0.0-beta.4
  • npm vite-plus 0.1.24
  • vitest.dev vitest 3.2.5, 4.1.8, 5.0.0-beta.4
  • vitest.dev vitest/browser 3.2.5, 4.1.8, 5.0.0-beta.4
  • voidzero-dev vite-plus 0.1.24

Is CVE-2026-53633 in your dependencies? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.

Check with Fencer

Vendor advisories

What the vendors themselves say about their products: affected, fixed or not affected, and what to do.

red hat product security vex CVE-2026-53633 updated cvss 8.1

@vitest/browser: vite-plus: Vitest: Remote code execution via exposed Chrome DevTools Protocol API

  • Red Hat Trusted Artifact Signer rhtas/rhtas-console-ui-rhel9
    not affected: vulnerable code not present

Red Hat CSAF VEX © Red Hat, Inc., from https://security.access.redhat.com/data/csaf/v2/vex/; changed: reduced to product statuses and remediations. CC BY 4.0 · csaf

CISA SSVC

Exploitation
Proof of concept is public
Automatable
yes
Technical impact
total
Assessed
3mo ago

Exploit prediction

0.90% chance of exploitation in the next 30 days, higher than 59% of all scored CVEs (FIRST EPSS, 2026-11-11).

CVSS scores

assigned by version score vector
CNA 3.1 9.8 CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
GitHub 3.1 9.8 CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H

Affected packages

ecosystem package affected fixed in
npm @vitest/browser
>=5.0.0-beta.0, <5.0.0-beta.4
>=4.0.0, <4.1.8
>=3.0.0, <3.2.5
5.0.0-beta.4
4.1.8
3.2.5
npm vite-plus
<0.1.24
0.1.24

Affected products

  • vitest-dev vitest

Classification

Weakness
  • CWE-749 Exposed Dangerous Method or Function
  • CWE-862 Missing Authorization

References

Sources

Fencer Intel keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.

The maintainers of vitest-dev/vitest published their own advisory on GitHub. Reviewed sources take precedence over it.

CPEs and fixed versions use Anchore's correction of NVD's data: Added CPE configurations because not yet analyzed by NVD.