Skip to content
Applications

CVE-2026-47429

9.8
Critical
EPSS 0.92%Patch availableJul 15, 2026

Vitest on Windows allows path traversal and API abuse to read files and execute scripts.

common questions

Is CVE-2026-47429 being exploited?

Not confirmed. CVE-2026-47429 does not appear in CISA's Known Exploited Vulnerabilities catalog, which records only exploitation that has been observed and reported publicly. That is evidence of absence of a report, not evidence the flaw is unattacked. EPSS currently estimates a 0.92% probability of exploitation in the next 30 days.

How severe is CVE-2026-47429?

CVE-2026-47429 is rated Critical with a CVSS score of 9.8. Severity describes how bad exploitation would be, not how likely it is: pair it with exploitation evidence before deciding what to patch first.

Is there a patch for CVE-2026-47429?

Yes. A fix has been recorded for CVE-2026-47429. The vendor advisory is the authority on the exact fixed version — apply it from there rather than from a summary.

What does CVE-2026-47429 affect?

CVE-2026-47429 affects Vitest < 3.2.5 (Windows), Vitest < 4.1.0 (Windows), Deployments exposing Vitest UI/API. Confirm the exact affected versions against the vendor advisory before deciding you are exposed.

What should I do about CVE-2026-47429?

Upgrade to Vitest 3.2.5 or 4.1.0 and restrict UI/API access until patched.

Exploitation status reflects CISA's KEV catalog as we last synced it. Check the catalog directly.

executive summary
technical analysis
affected
Vitest < 3.2.5 (Windows)Vitest < 4.1.0 (Windows)Deployments exposing Vitest UI/API
impact

Windows Vitest UI/API allows \?\..\ path traversal to read arbitrary files and API write/rerun features can enable arbitrary script execution.

action required

Immediate action required

affected versions
vitest-dev vitest
  • affected< 3.2.5
  • affected>= 4.0.0 and < 4.1.0

As published in the CVE Program record. A version outside these ranges is not a statement that it is unaffected — vendors sometimes understate a range, and distribution-backported builds carry upstream numbers that do not reflect what was patched into them.

how to fix
Remediation steps are tailored for users whose stack is affected. Add this technology to your stack to see the fix checklist.
references
get alerted

Track only the vulnerabilities that affect your infrastructure.

start for free