This weekExploitable · Confirmed
vite: Vite bypasses server.fs.deny when using ?raw??
There is evidence it can be used, or an emergency alert, without the proof that makes it urgent.
Does it affect what I run?
vite (npm)
Checked in your browser. The version you type is not sent anywhere.
Who is affected
- vite (npm): from 6.2.0, before 6.2.3
- vite (npm): from 6.1.0, before 6.1.2
- vite (npm): from 6.0.0, before 6.0.12
- vite (npm): from 5.0.0, before 5.4.15
- vite (npm): every version, before 4.5.10
The fix
vite (npm) fixed in 6.2.3
npmnpm install vite@6.2.3pnpmpnpm add vite@6.2.3yarnyarn add vite@6.2.3bunbun add vite@6.2.3Check what is installednpm ls vitePaste into Cursor, Lovable or Claude CodeUpgrade the npm dependency vite to 6.2.3 or the nearest later release, to fix CVE-2025-30208. 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.1.2
npmnpm install vite@6.1.2pnpmpnpm add vite@6.1.2yarnyarn add vite@6.1.2bunbun add vite@6.1.2Check what is installednpm ls vitePaste into Cursor, Lovable or Claude CodeUpgrade the npm dependency vite to 6.1.2 or the nearest later release, to fix CVE-2025-30208. 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.0.12
npmnpm install vite@6.0.12pnpmpnpm add vite@6.0.12yarnyarn add vite@6.0.12bunbun add vite@6.0.12Check what is installednpm ls vitePaste into Cursor, Lovable or Claude CodeUpgrade the npm dependency vite to 6.0.12 or the nearest later release, to fix CVE-2025-30208. 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 5.4.15
npmnpm install vite@5.4.15pnpmpnpm add vite@5.4.15yarnyarn add vite@5.4.15bunbun add vite@5.4.15Check what is installednpm ls vitePaste into Cursor, Lovable or Claude CodeUpgrade the npm dependency vite to 5.4.15 or the nearest later release, to fix CVE-2025-30208. 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 4.5.10
npmnpm install vite@4.5.10pnpmpnpm add vite@4.5.10yarnyarn add vite@4.5.10bunbun add vite@4.5.10Check what is installednpm ls vitePaste into Cursor, Lovable or Claude CodeUpgrade the npm dependency vite to 4.5.10 or the nearest later release, to fix CVE-2025-30208. 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
EPSS puts the chance of exploitation in the next 30 days at 75%.
FIRST EPSSStated
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: EPSS rates exploitation in the next 30 days as more likely than not. (FIRST EPSS)
- 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))