CVE-2026-112946 vitejs CVE debrief

Who should care

Defenders managing Vite projects, especially those using non-Windows machines and exposing the dev server to the network, should assess their exposure and verify if imported files could match host system paths.

Why it matters

Defenders should prioritize verifying exposure for Vite projects using non-Windows machines, especially those with explicitly exposed dev servers, and assess if imported files may match absolute host paths.

• Sensitive file exposure: Contents of files outside server.fs.allow could be returned to the browser.
• Path matching: Project imports could unintentionally serve host system files.
• Network exposure: Explicitly exposed Vite dev servers on non-Windows machines are vulnerable.
• Configuration review: Server configuration and file import patterns require review.

Technical summary

The Vite development server can serve files outside the server.fs.allow setting when a project's import paths match absolute system paths on non-Windows machines. This occurs when the dev server is explicitly exposed to the network, and the imported file's root-relative browser URL matches an absolute path of a readable file on the host. The sensitive file must not be matched by server.fs.deny, and the dev server must not be running on Windows. Defenders should prioritize verifying exposure for Vite projects using non-Windows machines, especially those with explicitly exposed dev servers.

Defensive priority

Defenders should prioritize verifying exposure for Vite projects using non-Windows machines, especially those with explicitly exposed dev servers, and assess if imported files may match absolute host paths.

Recommended defensive actions

• Verify if your Vite project imports files in a way that could match absolute paths on the host system.
• Check if your Vite dev server is exposed to the network and if server.fs.allow and server.fs.deny are properly configured.
• Update to a fixed version of Vite if your project is affected.
• 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.
• Confirm whether affected product deployments exist in managed environments and assign an owner for follow-up.

Evidence notes

The source corpus provides details on conditions for exploitation, including exposure of the Vite dev server to the network, specific file import patterns, and server configuration. The CVE record was published on 2026-10-21T16:47:42.000Z and has not been modified since then. There are no known exploit details, but defenders should prioritize verifying exposure for Vite projects using non-Windows machines, especially those with explicitly exposed dev servers.

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.