Vitest is a testing framework powered by Vite. Prior to 3.2.5 and 4.1.0, the Vitest UI/API server on Windows used isFileServingAllowed incorrectly for /__vitest_attachment__, allowing \\?\\..\\ path traversal to read files outside the project; exposed API write and rerun features such as saveTestFile and rerun could also allow arbitrary script execution. This issue is fixed in versions 3.2.5 and 4.1.0.
CVE-2026-47429
CRITICALPre-NVD 9.89.8—Trending — 3 sources updated this weekElevated
EchelonGraph scoreMEDIUM confidence
This critical-severity CVE scores 9.8 under a secondary CVSS source (NVD's own analysis pending). EPSS exploit probability: 1.0%, top 40% 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).
Triggered by: NVD CVSS baseline
Sources: epss, secondary
9.8
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
- High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS: 1%CVSS: 9.8Exploit: NoneExposed: 0
A fix is available — apply it.
- CVSS v3
- 9.8
- EG Score
- 9.8(medium)
- EG Risk
- 75(Attend)EG Risk 75/100SSVC: Attend
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 computedSeverity98% × 45%Exploitation40% × 40%Automatability100% × 15%Action: Remediate soon — notable exploitation risk. - EPSS
- 59.9%
- KEV
- Not listed
Published
June 1, 2026
Last Modified
July 21, 2026
Advisory Details (7)
Auto-updated Jul 16, 2026🔬 Proof of concept available. Patch available. Sources: github_pr, github_release, github, github_commit.
github Patch Available🟡 PoC Available
Arbitrary file can be read and executed when Vitest UI server is listening · Advisory · vitest-dev/vitest · GitHub
https://github.com/vitest-dev/vitest/security/advisories/GHSA-5xrq-8626-4rwpgithub_release Patch Available
v4.1.0
Patch available: vitest-dev/vitest v4.1.0
https://github.com/vitest-dev/vitest/releases/tag/v4.1.0github_release Patch Available
v3.2.5
Patch available: vitest-dev/vitest v3.2.5
https://github.com/vitest-dev/vitest/releases/tag/v3.2.5github_pr Patch Available
feat(api): add `allowWrite` and `allowExec` options to `api`
Patch available: vitest-dev/vitest v4.1.0-beta.3 (PR #9350 merged 2026-01-29)
https://github.com/vitest-dev/vitest/pull/9350github_pr Patch Available
feat(api): add `allowWrite` and `allowExec` options to `api` [backport to v3]
Patch available: vitest-dev/vitest v3.2.5 (PR #10445 merged 2026-05-28)
https://github.com/vitest-dev/vitest/pull/10445github_commit Patch Available
commit af88b1f5d828 (vitest-dev/vitest)
Patch available: vitest-dev/vitest v3.2.5 (contains commit af88b1f5d828)
https://github.com/vitest-dev/vitest/commit/af88b1f5d82844a4761ea9a977156c98e2b14ca8github_commit Patch Available
commit 20e00ef7808d (vitest-dev/vitest)
Patch available: vitest-dev/vitest v4.1.0-beta.3 (contains commit 20e00ef7808d)
https://github.com/vitest-dev/vitest/commit/20e00ef7808de6d330c5e2fda530f686e08f1c8dVendor Advisories for CVE-2026-47429(2)
These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.
Patch Availability(1)
| Vendor / Ecosystem | Fixed in / Patch | Released | Source |
|---|---|---|---|
| redhat | prometheus3-13-main-3.13.1-0.1.hum1 | 2026-07-13 | redhat |
Patches are aggregated from vendor advisories (Red Hat, Microsoft, Cisco, GitHub) and package ecosystems (OSV, GHSA). Multiple rows for the same upstream release have been deduplicated.
Affected Packages
(1 across 1 ecosystem)
npm(1)
| Package | Vulnerable range | Fixed in | Dependents |
|---|---|---|---|
| vitest | — | 3.2.6 | — |
Weakness Classification(1)
MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.
Data Freshness Timeline
(refreshed 9× in last 7d / 11× 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-07-23 03:17 UTCEG score recompute
- 2026-07-22 14:08 UTCEPSS rescore
- 2026-07-21 15:24 UTCEPSS rescore
- 2026-07-20 17:08 UTCEPSS rescore
- 2026-07-19 14:31 UTCEPSS rescore
- 2026-07-19 02:29 UTCEPSS rescore
- 2026-07-18 10:04 UTCEPSS rescore
- 2026-07-16 17:03 UTCEPSS rescore
- 2026-07-16 09:58 UTCVendor advisory
- 2026-07-16 01:34 UTCVendor advisory
- 2026-07-15 16:57 UTCEPSS rescore
- 2026-06-14 23:18 UTCEPSS rescore
- 2026-06-13 23:00 UTCEPSS rescore
- 2026-06-12 23:12 UTCEPSS rescore
- 2026-06-01 14:50 UTCEG score recompute
Related CVEs(same vendor + same CWE)
Same vendor
10 shownredhat
Frequently asked(5)
What is CVE-2026-47429?
CVE-2026-47429 is a critical vulnerability published on June 1, 2026. Vitest is a testing framework powered by Vite. Prior to 3.2.5 and 4.1.0, the Vitest UI/API server on Windows used isFileServingAllowed incorrectly for /vitest_attachment, allowing \\?\\..\\ path traversal to read files outside the project; exposed API write and rerun features such as saveTestFile…
When was CVE-2026-47429 disclosed?
CVE-2026-47429 was first published in the National Vulnerability Database on June 1, 2026, with the most recent update on July 21, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-47429 actively exploited?
CVE-2026-47429 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 59.9% percentile likelihood of exploitation in the next 30 days — higher percentiles indicate greater predicted risk.
What is the CVSS score of CVE-2026-47429?
CVE-2026-47429 has a CVSS v3 base score of 9.8 (NVD).
How do I remediate CVE-2026-47429?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-47429, EchelonGraph cross-links them in the Vendor Advisories panel below — those typically contain the canonical remediation steps, fixed version numbers, and any vendor-specific mitigations.
Dependency Blast Radius
See which npm, PyPI, Go, and Maven packages are affected by CVE-2026-47429
Is Your Infrastructure Affected by CVE-2026-47429?
EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.