CVE-2026-47429

MEDIUMNVD 5.95.9
EchelonGraph scoreMEDIUM confidence

This medium-severity CVE scores 5.9 under NVD CVSS v3. EPSS exploit probability: 0.9%, top 42% 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, nvd
Trending — 4 sources updated this weekElevated
5.9EG
EchelonGraph verdictMonitorLow exploitation likelihood right now — keep watching.
  • Lower severity and no public exploit yet
CISA-KEV: Not listedEPSS PROB: 1%CVSS: 5.9Exploit: Elevated riskExposed: 0

A fix is available — apply it.

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.

CVSS v3
5.9
EG Score
5.9(medium)
EG Risk
58(Attend)
EG Risk 58/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 computed
Severity59% × 45%
Exploitation40% × 40%
Automatability100% × 15%
Action: Remediate soon — notable exploitation risk.
EPSS PROB
1%
EPSS %ILE
58%
KEV
Not listed

Published

June 1, 2026

Last Modified

August 6, 2026

Advisory Details (7)

Auto-updated Aug 1, 2026
🔬 Proof of concept available. Patch available. Sources: github_commit, github_pr, github_release, github.
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-4rwp
github_release Patch Available

v4.1.0

Patch available: vitest-dev/vitest v4.1.0

https://github.com/vitest-dev/vitest/releases/tag/v4.1.0
github_release Patch Available

v3.2.5

Patch available: vitest-dev/vitest v3.2.5

https://github.com/vitest-dev/vitest/releases/tag/v3.2.5
github_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/9350
github_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/10445
github_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/af88b1f5d82844a4761ea9a977156c98e2b14ca8
github_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/20e00ef7808de6d330c5e2fda530f686e08f1c8d

Vendor 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 / EcosystemFixed in / PatchReleasedSource
redhatprometheus3-13-main-3.13.1-0.1.hum12026-07-13redhat

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)
PackageVulnerable rangeFixed inDependents
vitest3.2.6

Weakness Classification(1)

MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.

Data Freshness Timeline

(refreshed 8× in last 7d / 35× 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.

Showing the most recent 100 of 132 total refreshes for this CVE.

  1. 2026-09-16 05:15 UTCEPSS rescore
  2. 2026-09-14 06:10 UTCEG score recompute
  3. 2026-09-14 06:10 UTCVendor advisory
  4. 2026-09-13 16:47 UTCEPSS rescore
  5. 2026-09-13 01:06 UTCOSV refresh
  6. 2026-09-11 14:53 UTCEPSS rescore
  7. 2026-09-11 09:37 UTCEPSS rescore
  8. 2026-09-10 09:34 UTCEPSS rescore
  9. 2026-09-08 22:00 UTCEPSS rescore
  10. 2026-09-07 16:01 UTCEPSS rescore
  11. 2026-09-06 13:47 UTCEPSS rescore
  12. 2026-09-04 05:06 UTCEPSS rescore
  13. 2026-09-02 14:12 UTCEPSS rescore
  14. 2026-09-01 13:54 UTCEPSS rescore
  15. 2026-08-30 19:17 UTCEPSS rescore
  16. 2026-08-30 01:22 UTCEPSS rescore
  17. 2026-08-28 21:41 UTCEPSS rescore
  18. 2026-08-27 14:25 UTCEPSS rescore
  19. 2026-08-26 14:46 UTCEPSS rescore
  20. 2026-08-25 13:49 UTCEPSS rescore
  21. 2026-08-25 03:57 UTCEG score recompute
  22. 2026-08-25 03:57 UTCVendor advisory
  23. 2026-08-23 13:56 UTCEG score recompute
  24. 2026-08-23 13:56 UTCVendor advisory
  25. 2026-08-23 00:19 UTCEPSS rescore
Show 75 more
  1. 2026-08-21 23:49 UTCEPSS rescore
  2. 2026-08-21 14:52 UTCEG score recompute
  3. 2026-08-21 14:52 UTCVendor advisory
  4. 2026-08-20 22:55 UTCEPSS rescore
  5. 2026-08-20 10:18 UTCEG score recompute
  6. 2026-08-20 10:18 UTCVendor advisory
  7. 2026-08-19 17:04 UTCEPSS rescore
  8. 2026-08-18 13:48 UTCEPSS rescore
  9. 2026-08-17 13:47 UTCEPSS rescore
  10. 2026-08-17 13:18 UTCVendor advisory
  11. 2026-08-16 15:01 UTCEG score recompute
  12. 2026-08-16 15:01 UTCVendor advisory
  13. 2026-08-16 14:56 UTCEPSS rescore
  14. 2026-08-16 02:14 UTCEPSS rescore
  15. 2026-08-15 15:44 UTCEG score recompute
  16. 2026-08-15 15:44 UTCVendor advisory
  17. 2026-08-15 01:30 UTCEPSS rescore
  18. 2026-08-14 06:16 UTCEG score recompute
  19. 2026-08-14 06:16 UTCVendor advisory
  20. 2026-08-13 22:00 UTCEPSS rescore
  21. 2026-08-13 07:59 UTCEG score recompute
  22. 2026-08-13 07:59 UTCVendor advisory
  23. 2026-08-12 13:51 UTCEPSS rescore
  24. 2026-08-12 08:57 UTCEG score recompute
  25. 2026-08-12 08:57 UTCVendor advisory
  26. 2026-08-11 10:29 UTCEG score recompute
  27. 2026-08-11 10:29 UTCVendor advisory
  28. 2026-08-11 00:00 UTCEPSS rescore
  29. 2026-08-10 12:12 UTCVendor advisory
  30. 2026-08-09 13:56 UTCEG score recompute
  31. 2026-08-09 13:56 UTCVendor advisory
  32. 2026-08-09 13:46 UTCEPSS rescore
  33. 2026-08-08 16:37 UTCEPSS rescore
  34. 2026-08-08 15:39 UTCVendor advisory
  35. 2026-08-07 16:52 UTCEG score recompute
  36. 2026-08-07 16:52 UTCVendor advisory
  37. 2026-08-06 18:35 UTCEG score recompute 3.90
  38. 2026-08-06 18:35 UTCVendor advisory
  39. 2026-08-06 18:35 UTCNVD updateCVSS v3 → 5.9 · severity → MEDIUM
  40. 2026-08-06 16:47 UTCEG score recompute
  41. 2026-08-06 16:47 UTCVendor advisory
  42. 2026-08-06 13:47 UTCEPSS rescore
  43. 2026-08-06 12:46 UTCVendor advisory
  44. 2026-08-06 08:43 UTCVendor advisory
  45. 2026-08-06 04:42 UTCVendor advisory
  46. 2026-08-06 00:41 UTCVendor advisory
  47. 2026-08-05 20:40 UTCEG score recompute
  48. 2026-08-05 20:40 UTCVendor advisory
  49. 2026-08-05 19:17 UTCEPSS rescore
  50. 2026-08-04 22:42 UTCEG score recompute
  51. 2026-08-04 22:42 UTCVendor advisory
  52. 2026-08-04 15:10 UTCEPSS rescore
  53. 2026-08-04 10:39 UTCEPSS rescore
  54. 2026-08-04 03:56 UTCVendor advisory
  55. 2026-08-03 23:54 UTCVendor advisory
  56. 2026-08-03 19:53 UTCVendor advisory
  57. 2026-08-03 15:51 UTCEG score recompute
  58. 2026-08-03 15:51 UTCVendor advisory
  59. 2026-08-03 10:36 UTCEPSS rescore
  60. 2026-08-03 01:56 UTCVendor advisory
  61. 2026-08-02 21:54 UTCVendor advisory
  62. 2026-08-02 17:53 UTCVendor advisory
  63. 2026-08-02 13:51 UTCVendor advisory
  64. 2026-08-02 09:49 UTCVendor advisory
  65. 2026-08-02 05:48 UTCEG score recompute
  66. 2026-08-02 05:48 UTCVendor advisory
  67. 2026-08-02 02:27 UTCEPSS rescore
  68. 2026-08-02 01:46 UTCVendor advisory
  69. 2026-08-01 21:44 UTCVendor advisory
  70. 2026-08-01 17:42 UTCVendor advisory
  71. 2026-08-01 13:40 UTCEG score recompute
  72. 2026-08-01 13:40 UTCVendor advisory
  73. 2026-08-01 04:16 UTCEPSS rescore
  74. 2026-07-31 15:23 UTCVendor advisory
  75. 2026-07-31 10:14 UTCVendor advisory

Frequently asked(5)

What is CVE-2026-47429?
CVE-2026-47429 is a medium 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 August 6, 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 1% probability of exploitation in the next 30 days, which ranks it in the top 41.6% of all scored CVEs.
What is the CVSS score of CVE-2026-47429?
CVE-2026-47429 has a CVSS v3 base score of 5.9 (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

Explore →

Is Your Infrastructure Affected by CVE-2026-47429?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.