Security readout for executives and security teams
Plain-English summary
Vitest Browser Mode can let an unauthenticated client bypass intended file protections. If its API is reachable, the client may read sensitive local files, overwrite or create files, and delete files available to the Vitest process. This could expose source code, credentials, test data, or disrupt development and CI environments.
Executive priority
Treat reachable Browser Mode deployments as an immediate remediation priority because compromise can expose confidential files and alter or delete data without authentication. Prioritize internet-facing, shared CI, and sensitive development environments. Upgrade promptly; isolated installations not using Browser Mode can follow after exposure is verified.
Technical view
Several Browser Mode provider commands accept browser-controlled paths without checking allowWrite or restricting access to the project root. A network-reachable client can therefore perform path traversal-style reads and writes with the Vitest process permissions. Fixed releases add protections in 3.2.7, 4.1.10, and 5.0.0-beta.6.
Likely exposure
Exposure requires an affected Vitest version with Browser Mode operating and its API reachable by a potentially hostile client. Internet-exposed development servers are highest risk, but shared CI runners, developer networks, and untrusted test content may also create exposure. Installations not using Browser Mode are less likely to be exploitable through this flaw.
Exploitation context
The CVSS 3.1 score is 9.4 because exploitation is network-based, low-complexity, unauthenticated, and requires no user interaction. The supplied sources do not report observed exploitation, and the CVE is not identified as being in CISA KEV. Public proof-of-concept status is not established by the bundle.
Researcher notes
The affected commands include upload, takeScreenshot, screenshotMatcher, stopChunkTrace, deleteTracing, and annotateTraces. The core weaknesses are insufficient path confinement and missing authorization enforcement, mapped to CWE-22, CWE-552, and CWE-862. The bundle establishes filesystem access with process privileges but does not establish code execution or exploitation in the wild.
Mitigation direction
- Upgrade 3.x installations to Vitest 3.2.7 or later.
- Upgrade 4.x installations to Vitest 4.1.10 or later.
- Upgrade affected 5.0 beta installations to 5.0.0-beta.6 or later.
- Until upgraded, prevent untrusted clients from reaching the Browser Mode API.
- Run Vitest with minimal filesystem permissions to limit potential impact.
Validation and detection
- Inventory Vitest versions in developer systems, CI images, lockfiles, and build environments.
- Confirm whether Browser Mode is enabled in affected installations.
- Determine whether the Browser Mode API is reachable beyond trusted local processes.
- Verify deployed versions are 3.2.7, 4.1.10, 5.0.0-beta.6, or newer within their release lines.
- Review accessible environments for unexpected image, trace, or file changes.
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-22: File access and web shell behavior lookup
File traversal and upload weaknesses can lead teams to review file, web shell, execution, and collection telemetry. 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-552: 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 lookupCVE-2026-73653 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.4 (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:L
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:L3.95.5GitHub_MVulnerability scoring details
Base CVSS 3.1 score
9.4CriticalVector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:L
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-p63j-vcc4-9vmvCVE reference, GitHub_M · x_refsource_CONFIRM
- https://github.com/vitest-dev/vitest/pull/10674CVE reference, GitHub_M · x_refsource_MISC
- https://github.com/vitest-dev/vitest/pull/10679CVE reference, GitHub_M · x_refsource_MISC
- https://github.com/vitest-dev/vitest/pull/10680CVE reference, GitHub_M · x_refsource_MISC
- https://github.com/vitest-dev/vitest/commit/33f96a145ef09ca6a43b4e555eb273e64a87be23CVE reference, GitHub_M · x_refsource_MISC
- https://github.com/vitest-dev/vitest/commit/5c18dd267ff7f47f24cab2f615a16b37d90feb7fCVE reference, GitHub_M · x_refsource_MISC
- https://github.com/vitest-dev/vitest/commit/b795e36b34969bec50b47a9f29d26f799a6a04fbCVE reference, GitHub_M · x_refsource_MISC
- https://github.com/vitest-dev/vitest/releases/tag/v3.2.7CVE reference, GitHub_M · x_refsource_MISC
- https://github.com/vitest-dev/vitest/releases/tag/v4.1.10CVE reference, GitHub_M · x_refsource_MISC
- https://github.com/vitest-dev/vitest/releases/tag/v5.0.0-beta.6CVE 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.
Improper Limitation of a Pathname to a Restricted Directory ('Path Traversal')
Improper Limitation of a Pathname to a Restricted Directory ('Path Traversal') represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.
Files or Directories Accessible to External Parties
Files or Directories Accessible to External Parties 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.