dbcve.org
VitestApplication · Vitest.dev

CVE-2026-47429

MEDIUM · 5.9 CVSS v3.1 Published 2026-07-14
Fix available
A fix is available. Upgrade to 3.2.5 / 4.1.0 or later.
See remediation →
68/100
Remediation priority · Elevated
Public exploit Remotely reachable No privileges Zero-click Patch available 5 weeks old

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
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.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · high confidence

Vitest UI/API server on Windows has a path traversal vulnerability where isFileServingAllowed is incorrectly applied to /__vitest_attachment__ endpoints, allowing \\?\..\ sequences to read files outside the project root. Additionally, exposed API write/rerun features (saveTestFile, rerun) can be exploited for arbitrary script execution.

MitigationUpgrade Vitest to version 3.2.5 or 4.1.0 or later to obtain the patched isFileServingAllowed implementation and secured API endpoints.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
VitestApplication
Affected:< 3.2.5>= 4.0.0, < 4.1.0

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
High
Privileges
None
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
None
Availability
None

CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:N/A:N

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Confirm Windows environment
    Check if the operating system is Windows by running 'systeminfo | findstr /B /C:"OS Name"' or 'echo %OS%'
    Affected if Running on Windows (this vulnerability only affects Windows systems)
  2. Check installed Vitest version
    Run 'npm list vitest' or 'vitest --version' to get the installed version number
    Affected if Version is earlier than 3.2.5 or 4.1.0 (the patched versions)
  3. Verify Vitest UI server is active
    Check if the dev server with UI is running - look for process listening on port 51204 (default Vitest UI port) or check package.json for vitest --ui flag in scripts
    Affected if Vitest UI server is running and accessible on the network/localhost
  4. Inspect API endpoint accessibility
    Attempt a GET request to http://localhost:51204/__vitest_attachment__/test (or verify in browser devtools if UI is open)
    Affected if The /__vitest_attachment__ endpoint responds without additional authorization checks
  5. Check for exposed write API features
    Review vitest.config.(ts|js|mjs) for any custom API configurations or examine network requests when using the UI 'Rerun' or 'Save' features for test files
    Affected if saveTestFile or rerun API endpoints are exposed without authentication

A user is affected if running Vitest with UI/API server enabled on Windows and the installed version is below 3.2.5 or 4.1.0, with the vulnerable endpoints accessible.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

dbcve · scoped
Upgrade available Upgrade to 3.2.5 / 4.1.0 or later
Fixed in 3.2.54.1.0
Vendor patch github.com →
Interim mitigation

Upgrade Vitest to version 3.2.5 or 4.1.0 or later to obtain the patched isFileServingAllowed implementation and secured API endpoints.

Recommended fix High confidence

Upgrade to Vitest 3.2.5+ or 4.1.0+

  1. Check current Vitest version using `npm list vitest` or `pnpm list vitest`
  2. For projects on Vitest 3.x: upgrade to version 3.2.5 or later using `npm install vitest@^3.2.5`
  3. For projects on Vitest 4.x: upgrade to version 4.1.0 or later using `npm install vitest@^4.1.0`
  4. For projects on older versions (1.x or 2.x): upgrade to either 3.2.5+ or 4.1.0+ based on compatibility requirements
  5. Verify the upgrade was successful by running `npm list vitest`
  6. Test that the Vitest server starts correctly and the path traversal vulnerability is resolved
Caveat Upgrading between major version branches (e.g., 2.x to 3.x or 3.x to 4.x) may introduce breaking changes; review the changelog for your target version before upgrading

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Vitest Scoped from the published advisory
  • Consultation1.0 h
  • Implementation1.0 h
  • Testing2.0 h
  • Review / QA1.0 h
5.0 hours of engineering $860
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $1,376.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-47429 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2026-47429 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data