CVE-2026-47429 vitest-dev CVE debrief

Who should care

Developers and administrators using Vitest for testing purposes should be aware of this critical vulnerability. The issue allows for path traversal and arbitrary script execution, which can lead to severe consequences. Affected operator, platform, vulnerability-management, and security-team impact should be reviewed.

Technical summary

The vulnerability exists in the Vitest UI/API server on Windows, where the isFileServingAllowed function is used incorrectly for /__vitest_attachment__. This allows an attacker to perform path traversal and read files outside the project. Additionally, exposed API features such as saveTestFile and rerun can be used to execute arbitrary scripts. The issue is fixed in versions 3.2.5 and 4.1.0. Affected product deployments should be identified, and owners should be assigned for follow-up.

Defensive priority

High

Recommended defensive actions

• Update Vitest to version 3.2.5 or 4.1.0
• Restrict access to the Vitest UI/API server
• Monitor for suspicious activity
• Implement additional security measures to prevent path traversal and script execution
• Review compensating controls for exposed systems while remediation is scheduled and verified
• Check relevant monitoring, detection, and logs for exposed assets that need extra review
• Track exceptions, retest remediated assets, and close the item only after evidence is documented

Evidence notes

The CVE record was published on 2026-07-14T20:17:02.460Z and was last modified on 2026-07-21T16:17:12.920Z. The NVD entry is currently awaiting analysis. There is limited information available about the vulnerability, and defenders should verify the affected scope and severity. The Vitest UI/API server on Windows used isFileServingAllowed incorrectly for /__vitest_attachment__, allowing path traversal to read files outside the project.

Sources and references

Methodology and review provenance

AI-assisted synthesis based on stored public vulnerability evidence. System validation, approval state, and publication status do not by themselves establish human review of this revision. PatchSiren helps prioritize defensive review and does not prove exposure or remediation on any system.