Vite 5.4.19 introduces subtle but potentially impactful refinements over its predecessor, version 5.4.18. While the core functionality remains consistent, indicated by identical dependencies like Rollup, esbuild, and PostCSS, a key change lies in the dist section. Specifically, the unpackedSize has slightly increased from 3,276,648 bytes in version 5.4.18 to 3,278,469 bytes in version 5.4.19. This suggests internal optimizations, bug fixes, or minor feature enhancements that contribute to a marginally larger package size upon unpacking. Developers should evaluate if it impacts the overall app performance after upgrading Vite version.
Crucially, the releaseDate is different. Version 5.4.19 was released on "2025-04-30T05:57:48.896Z", approximately 20 days after version 5.4.18 released on "2025-04-10T06:47:16.885Z". It's important for developers to verify changelogs and upgrade their local versions of Vite.
Both versions share the same dependencies as development tools, including ws, cac, ufo, and others, ensuring consistent tooling for development workflows. Peer dependencies also remain the same, indicating compatibility with essential front-end libraries and frameworks. The minor version bump suggests that upgrading from 5.4.18 should not require major code modifications, minimizing disruption. For developers seeking cutting-edge Vite features and potential performance gains, upgrading to 5.4.19 is recommended, after reviewing the changelog for specific improvements and verifying compatibility with existing projects.
All the vulnerabilities related to the version 5.4.19 of the package
esbuild enables any website to send any requests to the development server and read the response
esbuild allows any websites to send any request to the development server and read the response due to default CORS settings.
esbuild sets Access-Control-Allow-Origin: * header to all requests, including the SSE connection, which allows any websites to send any request to the development server and read the response.
https://github.com/evanw/esbuild/blob/df815ac27b84f8b34374c9182a93c94718f8a630/pkg/api/serve_other.go#L121 https://github.com/evanw/esbuild/blob/df815ac27b84f8b34374c9182a93c94718f8a630/pkg/api/serve_other.go#L363
Attack scenario:
http://malicious.example.com).fetch('http://127.0.0.1:8000/main.js') request by JS in that malicious web page. This request is normally blocked by same-origin policy, but that's not the case for the reasons above.http://127.0.0.1:8000/main.js.In this scenario, I assumed that the attacker knows the URL of the bundle output file name. But the attacker can also get that information by
/index.html: normally you have a script tag here/assets: it's common to have a assets directory when you have JS files and CSS files in a different directory and the directory listing feature tells the attacker the list of files/esbuild SSE endpoint: the SSE endpoint sends the URL path of the changed files when the file is changed (new EventSource('/esbuild').addEventListener('change', e => console.log(e.type, e.data)))The scenario above fetches the compiled content, but if the victim has the source map option enabled, the attacker can also get the non-compiled content by fetching the source map file.
npm inpm run watchfetch('http://127.0.0.1:8000/app.js').then(r => r.text()).then(content => console.log(content)) in a different website's dev tools.Users using the serve feature may get the source code stolen by malicious websites.