CVE-2026-47429: Vitest is a testing framework powered by Vite

This week

CRITICAL 9.8REMOTEUPGRADE

CVE-2026-47429 is a critical-severity flaw (CVSS 9.8) affecting vitest. Below: why it ranks where it does, which versions are affected, what to do, and the exact commands.

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.

Why this priority

Critical severity
Public exploit reference
CISA SSVC: automatable with total technical impact
Remotely exploitable, no login, no user action

A fixed release or distro patch exists.

Risk facts

CVSS score	9.8 (Critical)
Attack vector	Network (remote)
Attack complexity	Low
Privileges needed	None
User interaction	None
EPSS exploit chance	0.9% (top 41%)
CISA exploited list	No
Weakness	CWE-22
Published	2026-07-14
Last modified	2026-10-24

Publisher (CNA): GitHub, Inc. · Vendor: vitest.dev

Last updated 2026-10-24 · Sources: CVE Program, NVD, CISA KEV, EPSS and vendor advisories · How we score

Am I affected?

Timeline

2026-07-14 20:17 UTCPublished CVE record published
2026-10-24 21:10 UTCUpdated Record last modified

vitest.dev vitest UPGRADE

Affected: < 3.2.5 · >= 4.0.0 and < 4.1.0

Fixed in: 3.2.5, 4.1.0

Safe to downgrade to: a release before 4.0.0

1. Check installed version

npm ls vitest

2. UPGRADE to 3.2.5

npm install vitest@">=3.2.5"

3. If no update is available yet, DOWNGRADE to a release before 4.0.0

npm view vitest versions npm install vitest@"<4.0.0"

Downgrade risk

Downgrading can break dependent software and may reopen older bugs. Read the distro advisory first and test on a non-production host.

After downgrade

Restart the service, and keep the package held until a fixed release ships.

Exact fixes by distribution

npm · vitest · FIXED · 4.1.0 · vulnerable: >= 4.0.0, < 4.1.0 · source

npm install vitest@">=4.1.0" npm ls vitest

Fedora 46 · conda · FIXED · 26.9.4-2.fc46 · FEDORA-2026-09931756f1 · source

sudo dnf upgrade --advisory=FEDORA-2026-09931756f1

Public exploits and detection

Public code exists for this CVE. Treat unpatched systems as at risk, and only run PoCs in a lab.

GitHub PoC: az9713/cve-lite-on-pi (0 stars)
Write-up: github.com/vitest-dev/vitest/security/advisories/GHSA-5xrq-8626-4rwp

Verify at the official source NVD · CVE Program · Report a problem with this page
Scores and fixes here are computed automatically from those and other public sources. Confirm with the vendor advisory before changing production systems.

Quick answers

How do I fix CVE-2026-47429?

vitest: upgrade to 3.2.5, 4.1.0. Exact commands for each OS are on this page.

Is CVE-2026-47429 being exploited?

CVE-2026-47429 is not on the CISA Known Exploited Vulnerabilities list at the time of the last update. Check again, as this can change.

What does CVE-2026-47429 affect?

CVE-2026-47429 affects vitest. Severity is critical (CVSS 9.8). 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 proje

How urgent is CVE-2026-47429?

Priority 62/100. Critical severity; Public exploit reference; CISA SSVC: automatable with total technical impact; Remotely exploitable, no login, no user action

Software pages

Windows vulnerabilities

References

← Back to latest CVEs