cve.bz

CVE-2026-53633 vitest-dev vitest: Exposed Dangerous Method or Function

9.8 criticalEPSS 0.9%Fix available

Critical (9.8) in vitest-dev vitest. EPSS 0.9% estimated probability of exploitation activity in the next 30 days. Fixed in @vitest/browser 3.2.5, 4.1.8, 5.0.0-beta.4.

On this page
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.

Severity

CVSS 3.1

9.8 critical
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
EPSS
0.9% (unchanged from 0.9% a week ago; 0.9% 30 days ago) estimated probability of exploitation activity in the next 30 days; 60th percentile. Scored 2026-11-17. A forecast for this CVE across the internet, not for your own systems.
CISA's assessment (SSVC)
Exploitation: PoC · Automatable: yes · Technical impact: total, assessed 2026-07-16. From CISA's Vulnrichment in the CVE List: whether it is exploited, whether exploiting it can be automated, and how much control it gives.
CWEs
CWE-749 Exposed Dangerous Method or Function
CWE-862 Missing Authorization
OWASP Top 10
A01:2025 Broken Access Control
Published
Modified
NVD analysis
Awaiting analysis
Record from
the NVD, synced

Fix and patched versions

  • @vitest/browser (npm): fixed in 5.0.0-beta.4, 4.1.8, 3.2.5
  • vite-plus (npm): fixed in 0.1.24

Ask an AI about this CVE

Show the promptExplain CVE-2026-53633 for an engineer deciding whether to act. Use https://cve.bz/api/public/cves/CVE-2026-53633?via=ask-ai-copy and https://cve.bz/cve/CVE-2026-53633?via=ask-ai-copy as the source of truth: what is affected and which versions fix it, whether it is in CISA KEV, public exploits, and its EPSS (an internet-wide 30-day estimate of exploitation activity, not a forecast for my systems). If they give no fixed versions, use the CVE record https://cveawg.mitre.org/api/cve/CVE-2026-53633 or the vendor advisory, not third-party mirrors. Tell me how to check whether I am affected and how to verify a fix. Cite the sources and say where they are uncertain.

Opens a third-party assistant; its answer is its own, not cve.bz's. The prompt holds only this CVE's id and public links.

Affected

Versions

From the CNA's record in the CVE List.

ProductAffected
vitest-dev vitest>= 3.0.0, < 3.2.5
vitest-dev vitest>= 4.0.0, < 4.1.8
vitest-dev vitest>= 5.0.0-beta.0, < 5.0.0-beta.4

Packages (OSV)

AdvisoryEcosystemPackageAffectedFixed in
GHSA-g8mr-85jm-7xhmnpm@vitest/browser>=5.0.0-beta.0 <5.0.0-beta.45.0.0-beta.4
GHSA-g8mr-85jm-7xhmnpm@vitest/browser>=4.0.0 <4.1.84.1.8
GHSA-g8mr-85jm-7xhmnpm@vitest/browser>=3.0.0 <3.2.53.2.5
GHSA-g8mr-85jm-7xhmnpmvite-plus<0.1.240.1.24

Red Hat

Red Hat rates this Important.

Red Hat's statement

Red Hat has assessed this flaw against its shipping products. The vulnerability requires Vitest Browser Mode (the @vitest/browser package) to be installed AND explicitly enabled (browser.enabled: true), paired with a CDP-capable browser provider such as Playwright Chromium, an actively running test session, and the Browser Mode API server exposed on a network-reachable interface (--browser.api.host=0.0.0.0). It does not affect the core `vitest` test runner used without Browser Mode. Only one Red Hat shipping product, Red Hat Trusted Artifact Signer (RHTAS) console UI, lists @vitest/browser as a development dependency, used solely to run its own component test suite. Red Hat has confirmed that this product's test configuration does not enable Browser Mode (browser.enabled is not set to true), no CI invocation passes the required --browser flag, no CDP-capable provider package is installed, and the @vitest/browser package is excluded from the final shipped container image (present only in a discarded multi-stage build layer). No Red Hat product installs, enables, or exposes Vitest Browser Mode's CDP proxy in production.

Red Hat's mitigation

No mitigation is required for Red Hat shipping products, as Vitest Browser Mode and its CDP proxy feature are not enabled or reachable in any Red Hat product's build, test, or runtime configuration. Development teams that do enable Vitest Browser Mode with a CDP-capable provider (Playwright or WebdriverIO) should avoid exposing the Browser Mode API server to untrusted networks (do not set --browser.api.host=0.0.0.0 or equivalent) and should upgrade to @vitest/browser 3.2.5, 4.1.8, 5.0.0-beta.4, or later, and vite-plus 0.1.24 or later.

ProductPackageStateAdvisory
Red Hat Trusted Artifact Signerrhtas/rhtas-console-ui-rhel9Not affected

Contains Red Hat Security Data © Red Hat, Inc., licensed under CC BY 4.0. Source: https://access.redhat.com/security/data. Modified: reformatted. Red Hat's page for CVE-2026-53633.

Attack patterns (CAPEC)

  • CAPEC-500 WebView Injection
  • CAPEC-665 Exploitation of Thunderbolt Protection Flaws Likelihood: Low · Severity: Very High

The attack patterns MITRE's CAPEC relates to this record's weaknesses, as MITRE names them. Credits.

References

Check your stackJSON