Is vite 6.3 vulnerable?
npm · 8 releases from 6.3.0 to 6.3.7 · latest vite is 8.3.5 · checked 1 Nov 2026
Yes: 10 known advisories
Yes. vite 6.3.7, the last 6.3 release, is affected by 10 known security advisories (2 high, 7 medium, 1 low), including CVE-2026-112942, CVE-2026-39363, CVE-2026-112946. 3 more affect earlier 6.3.x releases. Upgrade to 6.4.4 or later to fix all of them.
npm install vite@6.4.4Advisories affecting vite 6.3.7
Vite: Cross origin script execution through Vite custom middleware
- Affected
- >=8.3.0 <8.3.3 · >=8.2.0 <8.2.4 · >=8.0.0 <8.1.6 · >=7.0.0 <7.3.7 · <6.4.4
- Fixed in
- 6.4.4, 7.3.7, 8.1.6, 8.2.4, 8.3.3
Vite: Files outside `server.fs.allow` could be served when project paths match system paths on non-Windows machine
- Affected
- >=8.3.0 <8.3.3 · >=8.2.0 <8.2.4 · >=8.0.0 <8.1.6 · >=7.0.0 <7.3.7 · <6.4.4
- Fixed in
- 6.4.4, 7.3.7, 8.1.6, 8.2.4, 8.3.3
launch-editor: Editor CLI flag misinterpretation causing arbitrary command execution for some editors
- Affected
- >=8.3.0 <8.3.3 · >=8.2.0 <8.2.4 · >=8.0.0 <8.1.6 · >=7.0.0 <7.3.7 · <6.4.4
- Fixed in
- 6.4.4, 7.3.7, 8.1.6, 8.2.4, 8.3.3
launch-editor: `fs.existsSync()` existence check can be bypassed on Windows
- Affected
- >=8.3.0 <8.3.3 · >=8.2.0 <8.2.4 · >=8.0.0 <8.1.6 · >=7.0.0 <7.3.7 · <6.4.4
- Fixed in
- 6.4.4, 7.3.7, 8.1.6, 8.2.4, 8.3.3
launch-editor: escapeCmdArgs() omits % escaping on Windows
- Affected
- >=8.3.0 <8.3.3 · >=8.2.0 <8.2.4 · >=8.0.0 <8.1.6 · >=7.0.0 <7.3.7 · <6.4.4
- Fixed in
- 6.4.4, 7.3.7, 8.1.6, 8.2.4, 8.3.3
launch-editor: NTLMv2 hash disclosure via UNC path handling on Windows
- Affected
- >=8.0.0 <8.0.16 · >=7.0.0 <7.3.5 · <6.4.3
- Fixed in
- 6.4.3, 7.3.5, 8.0.16
vite: `server.fs.deny` bypass on Windows alternate paths
- Affected
- >=8.0.0 <8.0.16 · >=7.0.0 <7.3.5 · <6.4.3
- Fixed in
- 6.4.3, 7.3.5, 8.0.16
Vite Vulnerable to Path Traversal in Optimized Deps `.map` Handling
- Affected
- >=8.0.0 <8.0.5 · >=7.0.0 <7.3.2 · <6.4.2
- Fixed in
- 6.4.2, 7.3.2, 8.0.5
Vite Vulnerable to Arbitrary File Read via Vite Dev Server WebSocket
- Affected
- >=8.0.0 <8.0.5 · >=7.0.0 <7.3.2 · >=6.0.0 <6.4.2
- Fixed in
- 6.4.2, 7.3.2, 8.0.5
vite allows server.fs.deny bypass via backslash on Windows
- Affected
- >=7.1.0 <7.1.11 · >=7.0.0 <7.0.8 · >=6.0.0 <6.4.1 · >=2.9.18 <5.4.21 · >=3.2.9 <5.4.21 · >=4.5.3 <5.4.21 · >=5.2.6 <5.4.21
- Fixed in
- 5.4.21, 6.4.1, 7.0.8, 7.1.11
Fixed within 6.3.x, affecting earlier releases
Vite middleware may serve files starting with the same name with the public directory
- Affected
- >=7.1.0 <7.1.5 · >=7.0.0 <7.0.7 · >=6.0.0 <6.3.6 · <5.4.20
- Fixed in
- 5.4.20, 6.3.6, 7.0.7, 7.1.5
Vite's `server.fs` settings were not applied to HTML files
- Affected
- >=7.1.0 <7.1.5 · >=7.0.0 <7.0.7 · >=6.0.0 <6.3.6 · <5.4.20
- Fixed in
- 5.4.20, 6.3.6, 7.0.7, 7.1.5
Vite's server.fs.deny bypassed with /. for files under project root
- Affected
- >=6.3.0 <6.3.4 · >=6.2.0 <6.2.7 · >=6.0.0 <6.1.6 · >=5.0.0 <5.4.19 · <4.5.14
- Fixed in
- 4.5.14, 5.4.19, 6.1.6, 6.2.7, 6.3.4
Which of your client projects are still on vite 6.3?
NPMscan reads the lockfiles in every GitHub repo you pick, finds the exact vite version each one installs, and checks it against these advisories. Each finding comes with the command that fixes it.
Other vite versions
Advisory data from OSV.dev (opens OSV.dev in a new tab), which includes the GitHub Advisory Database. Release list from the npm registry. Refreshed daily.