Security readout for executives and security teams
Plain-English summary
Vitest Browser Mode exposed a powerful browser-control API in affected versions. If that API metadata is reachable by an attacker, they could abuse it to alter project configuration and cause attacker-controlled Node.js code execution. This is critical for exposed development or CI environments using affected Vitest versions.
Executive priority
Prioritize rapid remediation where affected Vitest Browser Mode runs in shared CI, remote development, or network-accessible test infrastructure. Lower priority may be reasonable for isolated local-only use, but version upgrades should still be tracked promptly.
Technical view
Affected Vitest versions expose a cdp() API that proxies raw Chrome DevTools Protocol methods without allowWrite or allowExec enforcement. The advisory describes abuse of CDP capabilities to overwrite vite.config.ts and trigger Node.js code execution. Fixed versions are 3.2.5, 4.1.8, and 5.0.0-beta.4.
Likely exposure
Exposure is most likely in development, test, or CI systems running Vitest Browser Mode where its browser API metadata is reachable beyond trusted local boundaries. Standard production applications are not identified as affected unless they expose this Vitest Browser Mode surface.
Exploitation context
The source bundle does not show CISA KEV listing or confirmed active exploitation. The CVSS vector is network, low complexity, no privileges, and no user interaction, but exploitation depends on attacker reachability to exposed Browser Mode API metadata.
Researcher notes
Key control failure is unrestricted CDP proxying through cdp(), bypassing intended allowWrite and allowExec gates. Evidence names CWE-749 and CWE-862. Do not assume broader Vite or Vitest runtime exposure beyond the affected Browser Mode versions listed in the advisory.
Mitigation direction
- Upgrade Vitest 3.x to 3.2.5 or later.
- Upgrade Vitest 4.x to 4.1.8 or later.
- Upgrade Vitest 5 beta to 5.0.0-beta.4 or later.
- Avoid exposing Vitest Browser Mode APIs to untrusted networks.
- Review the GitHub advisory for any branch-specific guidance.
Validation and detection
- Inventory package manifests and lockfiles for affected Vitest ranges.
- Identify projects or CI jobs using Vitest Browser Mode.
- Confirm resolved Vitest versions match fixed releases.
- Check whether Browser Mode endpoints are reachable outside trusted hosts.
- Review dependency update results and rerun the relevant test suite.
Public sources used
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
Conservative CVE-to-ATT&CK context
These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.
ATT&CK lookup starting points
Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.
CWE-749: Exact CWE lookup
Use the exact CWE identifier as the starting point before reviewing related ATT&CK behavior. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.
Open ATT&CK lookupCWE-862: Authorization and privilege behavior lookup
Authorization weaknesses can support privilege escalation and valid-account review, depending on exploit path. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.
Open ATT&CK lookupExecution behavior lookup
The CVE wording references code or command execution, so execution technique review may help defensive triage. This is a Glexia inferred lookup path, not an official MITRE, ATT&CK, or CVE Program mapping.
Open ATT&CK lookupCVE-2026-53633 mapping review
Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.
Open ATT&CK lookup- Severity
- Critical
- CVSS
- 9.8 (3.1)
- Known Exploited
- No
- Published
Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
CNA and ADP enrichment extracted from CVE v5
These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.
SSVC decision data
CVSS vector scores
1 official scoreWe collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H3.95.9GitHub_MVulnerability scoring details
Base CVSS 3.1 score
9.8CriticalVector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
Vulnerability timeline
Timeline events are normalized from CVE metadata, CNA source timelines, ADP timelines, and KEV metadata when present.
- CVE reservedCVE Program
The CVE ID was reserved by the assigning CNA.
- CVE publishedCVE Program
The CVE record was published.
- CVE updatedCVE Program
The CVE record metadata indicates this as the latest update time.
ADP provider summaries
Source materials
- CVE List V5 sourceCVE List V5
- https://github.com/vitest-dev/vitest/security/advisories/GHSA-g8mr-85jm-7xhmCVE reference, GitHub_M · x_refsource_CONFIRM
- https://github.com/vitest-dev/vitest/pull/10444CVE reference, GitHub_M · x_refsource_MISC
- https://github.com/vitest-dev/vitest/pull/10450CVE reference, GitHub_M · x_refsource_MISC
- https://github.com/vitest-dev/vitest/pull/10456CVE reference, GitHub_M · x_refsource_MISC
- https://github.com/vitest-dev/vitest/commit/385a1aefd4c2bfa5e7d58bf7c6834c929969f2c7CVE reference, GitHub_M · x_refsource_MISC
- https://github.com/vitest-dev/vitest/commit/63e3b2eee4d58da56786a6333f517b9b492528c7CVE reference, GitHub_M · x_refsource_MISC
- https://github.com/vitest-dev/vitest/commit/e4067b3b150005fd42cf75f994300119245806b9CVE reference, GitHub_M · x_refsource_MISC
- https://github.com/vitest-dev/vitest/releases/tag/v3.2.5CVE reference, GitHub_M · x_refsource_MISC
- https://github.com/vitest-dev/vitest/releases/tag/v4.1.8CVE reference, GitHub_M · x_refsource_MISC
- https://github.com/vitest-dev/vitest/releases/tag/v5.0.0-beta.4CVE reference, GitHub_M · x_refsource_MISC
Products and packages named in the record
CWE details
CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.
Exposed Dangerous Method or Function
Exposed Dangerous Method or Function represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.
Missing Authorization
Missing Authorization represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.