vite: Vite Vitejs Improper Access Control Vulnerability
There is evidence it is being used against people now, on something Phylax follows.
Does it affect what I run?
Checked in your browser. The version you type is not sent anywhere.
Who is affected
- vite (npm): from 6.2.0, before 6.2.4
- vite (npm): from 6.1.0, before 6.1.3
- vite (npm): from 6.0.0, before 6.0.13
- vite (npm): from 5.0.0, before 5.4.16
- vite (npm): every version, before 4.5.11
The fix
vite (npm) fixed in 6.2.4
npmnpm install vite@6.2.4pnpmpnpm add vite@6.2.4yarnyarn add vite@6.2.4bunbun add vite@6.2.4Check what is installednpm ls vitePaste into Cursor, Lovable or Claude CodeUpgrade the npm dependency vite to 6.2.4 or the nearest later release, to fix CVE-2025-31125. 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.3
npmnpm install vite@6.1.3pnpmpnpm add vite@6.1.3yarnyarn add vite@6.1.3bunbun add vite@6.1.3Check what is installednpm ls vitePaste into Cursor, Lovable or Claude CodeUpgrade the npm dependency vite to 6.1.3 or the nearest later release, to fix CVE-2025-31125. 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.13
npmnpm install vite@6.0.13pnpmpnpm add vite@6.0.13yarnyarn add vite@6.0.13bunbun add vite@6.0.13Check what is installednpm ls vitePaste into Cursor, Lovable or Claude CodeUpgrade the npm dependency vite to 6.0.13 or the nearest later release, to fix CVE-2025-31125. 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.16
npmnpm install vite@5.4.16pnpmpnpm add vite@5.4.16yarnyarn add vite@5.4.16bunbun add vite@5.4.16Check what is installednpm ls vitePaste into Cursor, Lovable or Claude CodeUpgrade the npm dependency vite to 5.4.16 or the nearest later release, to fix CVE-2025-31125. 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.11
npmnpm install vite@4.5.11pnpmpnpm add vite@4.5.11yarnyarn add vite@4.5.11bunbun add vite@4.5.11Check what is installednpm ls vitePaste into Cursor, Lovable or Claude CodeUpgrade the npm dependency vite to 4.5.11 or the nearest later release, to fix CVE-2025-31125. 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
Exploited · Confirmed
It is in CISA's Known Exploited Vulnerabilities catalogue.
Exploited · Confirmed
CISA's assessment in the CVE record says exploitation is active.
CISA Vulnrichment (SSVC and KEV fields inside CVE records)Stated
Exploitable · Confirmed
EPSS puts the chance of exploitation in the next 30 days at 75%.
FIRST EPSSStated
Timeline
- First published here, as "Listed".
- Level changed from "Listed" to "Act now".
- Fixed releases changed: added vite 6.2.4, vite 6.1.3, vite 6.0.13, vite 5.4.16, vite 4.5.11.
- Evidence added: CISA's assessment in the CVE record says exploitation is active. (CISA Vulnrichment (SSVC and KEV fields inside CVE records))
- Evidence added: EPSS rates exploitation in the next 30 days as more likely than not. (FIRST EPSS)