Vitest is a testing framework powered by Vite. Prior to versions 3.2.7, 4.1.10, and 5.0.0-beta.6, Browser Mode provider commands including upload, takeScreenshot, screenshotMatcher, stopChunkTrace, deleteTracing, and annotateTraces accept browser-supplied file paths without enforcing the allowWrite permission gate or confining paths to the project root. A client that can reach the Browser Mode API can read arbitrary local files, create or overwrite image and trace files, or delete files accessible to the Vitest process even when allowWrite is false. This issue is fixed in versions 3.2.7, 4.1.10, and 5.0.0-beta.6.
CVE-2026-73653
This critical-severity CVE scores 9.4 under a secondary CVSS source (NVD's own analysis pending). EPSS exploit probability: 0.6%, top 52% of all CVEs by exploit prediction. GitHub Security Advisory data not yet ingested — confidence will rise once GHSA publishes (typical lag: hours to days for open-source ecosystem CVEs; never for infrastructure-only CVEs).
- High severity, but no confirmed exploitation yet
No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.
- CVSS v3
- 9.4
- EG Score
- 9.4(medium)
- EG Risk
- 47(Track)EG Risk 47/100SSVC: Track
EG Risk is EchelonGraph's 0–100 priority score: it fuses intrinsic severity with real-world exploitation and automatability so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner. Distinct from the 0–10 EG Score (severity).
How it’s computedSeverity94% × 45%Exploitation1% × 40%Automatability30% × 15%Action: Routine — remediate on your standard cadence. - EPSS PROB
- 1%
- EPSS %ILE
- 48%
- KEV
- Not listed
Published
August 13, 2026
Last Modified
August 13, 2026
Advisory Details (10)
Auto-updated Aug 13, 2026v5.0.0-beta.6
Patch available: vitest-dev/vitest v5.0.0-beta.6 (pre-release)
https://github.com/vitest-dev/vitest/releases/tag/v5.0.0-beta.6v4.1.10
Patch available: vitest-dev/vitest v4.1.10
https://github.com/vitest-dev/vitest/releases/tag/v4.1.10v3.2.7
Patch available: vitest-dev/vitest v3.2.7
https://github.com/vitest-dev/vitest/releases/tag/v3.2.7commit b795e36b3496 (vitest-dev/vitest)
Patch available: vitest-dev/vitest v3.2.7 (contains commit b795e36b3496)
https://github.com/vitest-dev/vitest/commit/b795e36b34969bec50b47a9f29d26f799a6a04fbcommit 5c18dd267ff7 (vitest-dev/vitest)
Patch available: vitest-dev/vitest v4.1.10 (contains commit 5c18dd267ff7)
https://github.com/vitest-dev/vitest/commit/5c18dd267ff7f47f24cab2f615a16b37d90feb7fcommit 33f96a145ef0 (vitest-dev/vitest)
Patch available: vitest-dev/vitest v5.0.0-beta.6 (contains commit 33f96a145ef0)
https://github.com/vitest-dev/vitest/commit/33f96a145ef09ca6a43b4e555eb273e64a87be23fix(browser): check fs access in builtin commands [backport to v4]
Patch available: vitest-dev/vitest v4.1.10 (PR #10680 merged 2026-07-01)
https://github.com/vitest-dev/vitest/pull/10680fix(browser): check fs access in builtin commands [backport to v3]
Patch available: vitest-dev/vitest v3.2.7 (PR #10679 merged 2026-07-01)
https://github.com/vitest-dev/vitest/pull/10679fix(browser): check fs access in builtin commands
Patch available: vitest-dev/vitest v5.0.0-beta.6 (PR #10674 merged 2026-07-01)
https://github.com/vitest-dev/vitest/pull/10674Browser Mode provider commands bypass the file-access permission gate · Advisory · vitest-dev/vitest · GitHub
https://github.com/vitest-dev/vitest/security/advisories/GHSA-p63j-vcc4-9vmvVendor Advisories for CVE-2026-73653(1)
These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.
Affected Packages
(1 across 1 ecosystem)
npm(1)
| Package | Vulnerable range | Fixed in | Dependents |
|---|---|---|---|
| @vitest/browser | — | 4.1.10 | — |
Weakness Classification(3)
MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.
Data Freshness Timeline
(refreshed 5× in last 7d / 5× in last 30d)
Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. Most recent first.
- 2026-08-15 03:49 UTCEG score recompute
- 2026-08-15 01:31 UTCEPSS rescore
- 2026-08-13 19:19 UTCEG score recompute
- 2026-08-13 18:32 UTCEG score recompute
- 2026-08-13 18:31 UTCMITRE cvelistV5first tracked
Related CVEs(same CWE)
Same CWE
10 shownCWE-22 · CWE-862
Frequently asked(5)
What is CVE-2026-73653?
When was CVE-2026-73653 disclosed?
Is CVE-2026-73653 actively exploited?
What is the CVSS score of CVE-2026-73653?
How do I remediate CVE-2026-73653?
Dependency Blast Radius
See which npm, PyPI, Go, and Maven packages are affected by CVE-2026-73653
Is Your Infrastructure Affected by CVE-2026-73653?
EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.