This weekExploitable · Confirmed
vite, vite-plus: Vite: Files outside `server.fs.allow` could be served when project paths match system paths on non-Windows machine
There is evidence it can be used, or an emergency alert, without the proof that makes it urgent.
Does it affect what I run?
Checked in your browser. The version you type is not sent anywhere.
Who is affected
- vite (npm): from 8.3.0, before 8.3.3
- vite (npm): from 8.2.0, before 8.2.4
- vite (npm): from 8.0.0, before 8.1.6
- vite (npm): from 7.0.0, before 7.3.7
- vite (npm): every version, before 6.4.4
- vite-plus (npm): every version, before 1.1.0
The fix
vite (npm) fixed in 8.3.3
npmnpm install vite@8.3.3pnpmpnpm add vite@8.3.3yarnyarn add vite@8.3.3bunbun add vite@8.3.3Check what is installednpm ls vitePaste into Cursor, Lovable or Claude CodeUpgrade the npm dependency vite to 8.3.3 or the nearest later release, to fix CVE-2026-112946. Change only what the upgrade needs: the manifest, the lockfile, and any code that breaks because of it. Do not change anything else and do not run commands unrelated to this upgrade. Then run the tests, tell me what changed, and show me the diff before committing.vite (npm) fixed in 8.2.4
npmnpm install vite@8.2.4pnpmpnpm add vite@8.2.4yarnyarn add vite@8.2.4bunbun add vite@8.2.4Check what is installednpm ls vitePaste into Cursor, Lovable or Claude CodeUpgrade the npm dependency vite to 8.2.4 or the nearest later release, to fix CVE-2026-112946. Change only what the upgrade needs: the manifest, the lockfile, and any code that breaks because of it. Do not change anything else and do not run commands unrelated to this upgrade. Then run the tests, tell me what changed, and show me the diff before committing.vite (npm) fixed in 8.1.6
npmnpm install vite@8.1.6pnpmpnpm add vite@8.1.6yarnyarn add vite@8.1.6bunbun add vite@8.1.6Check what is installednpm ls vitePaste into Cursor, Lovable or Claude CodeUpgrade the npm dependency vite to 8.1.6 or the nearest later release, to fix CVE-2026-112946. Change only what the upgrade needs: the manifest, the lockfile, and any code that breaks because of it. Do not change anything else and do not run commands unrelated to this upgrade. Then run the tests, tell me what changed, and show me the diff before committing.vite (npm) fixed in 7.3.7
npmnpm install vite@7.3.7pnpmpnpm add vite@7.3.7yarnyarn add vite@7.3.7bunbun add vite@7.3.7Check what is installednpm ls vitePaste into Cursor, Lovable or Claude CodeUpgrade the npm dependency vite to 7.3.7 or the nearest later release, to fix CVE-2026-112946. Change only what the upgrade needs: the manifest, the lockfile, and any code that breaks because of it. Do not change anything else and do not run commands unrelated to this upgrade. Then run the tests, tell me what changed, and show me the diff before committing.vite (npm) fixed in 6.4.4
npmnpm install vite@6.4.4pnpmpnpm add vite@6.4.4yarnyarn add vite@6.4.4bunbun add vite@6.4.4Check what is installednpm ls vitePaste into Cursor, Lovable or Claude CodeUpgrade the npm dependency vite to 6.4.4 or the nearest later release, to fix CVE-2026-112946. Change only what the upgrade needs: the manifest, the lockfile, and any code that breaks because of it. Do not change anything else and do not run commands unrelated to this upgrade. Then run the tests, tell me what changed, and show me the diff before committing.vite-plus (npm) fixed in 1.1.0
npmnpm install vite-plus@1.1.0pnpmpnpm add vite-plus@1.1.0yarnyarn add vite-plus@1.1.0bunbun add vite-plus@1.1.0Check what is installednpm ls vite-plusPaste into Cursor, Lovable or Claude CodeUpgrade the npm dependency vite-plus to 1.1.0 or the nearest later release, to fix CVE-2026-112946. Change only what the upgrade needs: the manifest, the lockfile, and any code that breaks because of it. Do not change anything else and do not run commands unrelated to this upgrade. Then run the tests, tell me what changed, and show me the diff before committing.
Fix commands generated from the advisory's versions. No model wrote them.
In plain words
Brief pending: here are the facts and the fix. The explanation in plain words follows when it has been written and checked.
Evidence
Exploitable · Confirmed
CISA's assessment in the CVE record says a proof of concept is public.
CISA Vulnrichment (SSVC and KEV fields inside CVE records)Stated
Timeline
- First published here, as "For your digest".
- Level changed from "For your digest" to "This week".
- Evidence added: CISA's assessment in the CVE record says a proof of concept is public. (CISA Vulnrichment (SSVC and KEV fields inside CVE records))