🚨 [security] [js] Update vite 5.4.21 → 8.0.16 (major)

[depfu]

---

🚨 Your current dependencies have known security vulnerabilities 🚨

This dependency update fixes known security vulnerabilities. Please see the details below and assess their impact carefully. We recommend to merge and deploy this as soon as possible!

---

Here is everything you need to know about this upgrade. Please take a good look at what changed and the test results before merging this pull request.

What changed?

✳️ vite (5.4.21 → 8.0.16) · Repo · Changelog

Security Advisories 🚨

🚨 vite: `server.fs.deny` bypass on Windows alternate paths

More info than we can show here.

🚨 launch-editor: NTLMv2 hash disclosure via UNC path handling on Windows

More info than we can show here.

🚨 vite: `server.fs.deny` bypass on Windows alternate paths

More info than we can show here.

🚨 launch-editor: NTLMv2 hash disclosure via UNC path handling on Windows

More info than we can show here.

🚨 vite: `server.fs.deny` bypass on Windows alternate paths

More info than we can show here.

🚨 launch-editor: NTLMv2 hash disclosure via UNC path handling on Windows

More info than we can show here.

🚨 Vite: `server.fs.deny` bypassed with queries

More info than we can show here.

🚨 Vite Vulnerable to Arbitrary File Read via Vite Dev Server WebSocket

More info than we can show here.

🚨 Vite Vulnerable to Arbitrary File Read via Vite Dev Server WebSocket

More info than we can show here.

🚨 Vite Vulnerable to Path Traversal in Optimized Deps `.map` Handling

More info than we can show here.

🚨 Vite: `server.fs.deny` bypassed with queries

More info than we can show here.

🚨 Vite Vulnerable to Arbitrary File Read via Vite Dev Server WebSocket

More info than we can show here.

🚨 Vite Vulnerable to Path Traversal in Optimized Deps `.map` Handling

More info than we can show here.

🚨 Vite Vulnerable to Path Traversal in Optimized Deps `.map` Handling

More info than we can show here.

🚨 vite allows server.fs.deny bypass via backslash on Windows

More info than we can show here.

🚨 vite allows server.fs.deny bypass via backslash on Windows

More info than we can show here.

🚨 vite allows server.fs.deny bypass via backslash on Windows

More info than we can show here.

🚨 Vite middleware may serve files starting with the same name with the public directory

More info than we can show here.

🚨 Vite's `server.fs` settings were not applied to HTML files

More info than we can show here.

🚨 Vite middleware may serve files starting with the same name with the public directory

More info than we can show here.

🚨 Vite's `server.fs` settings were not applied to HTML files

More info than we can show here.

🚨 Vite's `server.fs` settings were not applied to HTML files

More info than we can show here.

🚨 Vite middleware may serve files starting with the same name with the public directory

More info than we can show here.

🚨 Vite's server.fs.deny bypassed with /. for files under project root

More info than we can show here.

🚨 Vite's server.fs.deny bypassed with /. for files under project root

More info than we can show here.

🚨 Vite's server.fs.deny bypassed with /. for files under project root

More info than we can show here.

🚨 Vite has an `server.fs.deny` bypass with an invalid `request-target`

More info than we can show here.

🚨 Vite has an `server.fs.deny` bypass with an invalid `request-target`

More info than we can show here.

🚨 Vite has an `server.fs.deny` bypass with an invalid `request-target`

More info than we can show here.

🚨 Vite allows server.fs.deny to be bypassed with .svg or relative paths

More info than we can show here.

🚨 Vite allows server.fs.deny to be bypassed with .svg or relative paths

More info than we can show here.

🚨 Vite allows server.fs.deny to be bypassed with .svg or relative paths

More info than we can show here.

🚨 Vite has a `server.fs.deny` bypassed for `inline` and `raw` with `?import` query

More info than we can show here.

🚨 Vite has a `server.fs.deny` bypassed for `inline` and `raw` with `?import` query

More info than we can show here.

🚨 Vite has a `server.fs.deny` bypassed for `inline` and `raw` with `?import` query

More info than we can show here.

🚨 Vite bypasses server.fs.deny when using ?raw??

More info than we can show here.

🚨 Vite bypasses server.fs.deny when using ?raw??

More info than we can show here.

🚨 Vite bypasses server.fs.deny when using ?raw??

More info than we can show here.

🚨 Websites were able to send any requests to the development server and read the response in vite

More info than we can show here.

Release Notes

Too many releases to show here. View the full release notes.

Commits

See the full diff on Github. The new version differs by more commits than we can show here.

🆕 esbuild (added, 0.28.1)

---

Depfu will automatically keep this PR conflict-free, as long as you don't add any commits to this branch yourself. You can also trigger a rebase manually by commenting with @depfu rebase.

All Depfu comment commands

@​depfu rebase

Rebases against your default branch and redoes this update

@​depfu recreate

Recreates this PR, overwriting any edits that you've made to it

@​depfu merge

Merges this PR once your tests are passing and conflicts are resolved

@​depfu cancel merge

Cancels automatic merging of this PR

@​depfu close

Closes this PR and deletes the branch

@​depfu reopen

Restores the branch and reopens this PR (if it's closed)

@​depfu pause

Ignores all future updates for this dependency and closes this PR

@​depfu pause [minor|major]

Ignores all future minor/major updates for this dependency and closes this PR

@​depfu resume

Future versions of this dependency will create PRs again (leaves this PR as is)

Go to the Depfu Dashboard to see the state of your dependencies and to customize how Depfu works.

[socket-security]

Review the following changes in direct dependencies. Learn more about Socket for GitHub.

Diff	Package	Supply Chain Security	Vulnerability	Quality	Maintenance	License
	npm/​postcss@​8.5.10 ⏵ 8.5.15	+1		+1
	npm/​vite@​5.4.21 ⏵ 8.0.16	+6	+19

View full report

[socket-security]

Warning

Review the following alerts detected in dependencies.

According to your organization's Security Policy, it is recommended to resolve "Warn" alerts. Learn more about Socket for GitHub.

Action	Severity	Alert  (click "▶" to expand/collapse)
Warn		Dynamic code execution: npm @emnapi/core Eval Type: Function Location: Package overview From: ? → npm/vite@8.0.16 → npm/@emnapi/core@1.10.0 ℹ Read more on: This package | This alert | What is dynamic code execution? Next steps: Take a moment to review the security alert above. Review the linked package source code to understand the potential risk. Ensure the package is not malicious before proceeding. If you're unsure how to proceed, reach out to your security team or ask the Socket team for help at support@socket.dev. Suggestion: Avoid packages that use dynamic code execution like eval(), since this could potentially execute any code. Mark the package as acceptable risk. To ignore this alert only in this pull request, reply with the comment @SocketSecurity ignore npm/@emnapi/core@1.10.0. You can also ignore all packages with @SocketSecurity ignore-all. To ignore an alert for all future pull requests, use Socket's Dashboard to change the triage state of this alert.
Warn		Dynamic code execution: npm @emnapi/core Eval Type: eval Location: Package overview From: ? → npm/vite@8.0.16 → npm/@emnapi/core@1.10.0 ℹ Read more on: This package | This alert | What is dynamic code execution? Next steps: Take a moment to review the security alert above. Review the linked package source code to understand the potential risk. Ensure the package is not malicious before proceeding. If you're unsure how to proceed, reach out to your security team or ask the Socket team for help at support@socket.dev. Suggestion: Avoid packages that use dynamic code execution like eval(), since this could potentially execute any code. Mark the package as acceptable risk. To ignore this alert only in this pull request, reply with the comment @SocketSecurity ignore npm/@emnapi/core@1.10.0. You can also ignore all packages with @SocketSecurity ignore-all. To ignore an alert for all future pull requests, use Socket's Dashboard to change the triage state of this alert.
Warn		Network access: npm @emnapi/core in module globalThis["fetch"] Module: globalThis["fetch"] Location: Package overview From: ? → npm/vite@8.0.16 → npm/@emnapi/core@1.10.0 ℹ Read more on: This package | This alert | What is network access? Next steps: Take a moment to review the security alert above. Review the linked package source code to understand the potential risk. Ensure the package is not malicious before proceeding. If you're unsure how to proceed, reach out to your security team or ask the Socket team for help at support@socket.dev. Suggestion: Packages should remove all network access that is functionally unnecessary. Consumers should audit network access to ensure legitimate use. Mark the package as acceptable risk. To ignore this alert only in this pull request, reply with the comment @SocketSecurity ignore npm/@emnapi/core@1.10.0. You can also ignore all packages with @SocketSecurity ignore-all. To ignore an alert for all future pull requests, use Socket's Dashboard to change the triage state of this alert.
Warn		Dynamic code execution: npm @emnapi/runtime Eval Type: Function Location: Package overview From: ? → npm/vite@8.0.16 → npm/@emnapi/runtime@1.10.0 ℹ Read more on: This package | This alert | What is dynamic code execution? Next steps: Take a moment to review the security alert above. Review the linked package source code to understand the potential risk. Ensure the package is not malicious before proceeding. If you're unsure how to proceed, reach out to your security team or ask the Socket team for help at support@socket.dev. Suggestion: Avoid packages that use dynamic code execution like eval(), since this could potentially execute any code. Mark the package as acceptable risk. To ignore this alert only in this pull request, reply with the comment @SocketSecurity ignore npm/@emnapi/runtime@1.10.0. You can also ignore all packages with @SocketSecurity ignore-all. To ignore an alert for all future pull requests, use Socket's Dashboard to change the triage state of this alert.
Warn		Network access: npm @tybys/wasm-util in module globalThis["fetch"] Module: globalThis["fetch"] Location: Package overview From: ? → npm/vite@8.0.16 → npm/@tybys/wasm-util@0.10.2 ℹ Read more on: This package | This alert | What is network access? Next steps: Take a moment to review the security alert above. Review the linked package source code to understand the potential risk. Ensure the package is not malicious before proceeding. If you're unsure how to proceed, reach out to your security team or ask the Socket team for help at support@socket.dev. Suggestion: Packages should remove all network access that is functionally unnecessary. Consumers should audit network access to ensure legitimate use. Mark the package as acceptable risk. To ignore this alert only in this pull request, reply with the comment @SocketSecurity ignore npm/@tybys/wasm-util@0.10.2. You can also ignore all packages with @SocketSecurity ignore-all. To ignore an alert for all future pull requests, use Socket's Dashboard to change the triage state of this alert.
Warn		Filesystem access: npm fdir with module fs Module: fs Location: Package overview From: ? → npm/vite@8.0.16 → npm/fdir@6.5.0 ℹ Read more on: This package | This alert | What is filesystem access? Next steps: Take a moment to review the security alert above. Review the linked package source code to understand the potential risk. Ensure the package is not malicious before proceeding. If you're unsure how to proceed, reach out to your security team or ask the Socket team for help at support@socket.dev. Suggestion: If a package must read the file system, clarify what it will read and ensure it reads only what it claims to. If appropriate, packages can leave file system access to consumers and operate on data passed to it instead. Mark the package as acceptable risk. To ignore this alert only in this pull request, reply with the comment @SocketSecurity ignore npm/fdir@6.5.0. You can also ignore all packages with @SocketSecurity ignore-all. To ignore an alert for all future pull requests, use Socket's Dashboard to change the triage state of this alert.
Warn		Filesystem access: npm tinyglobby with module fs Module: fs Location: Package overview From: ? → npm/vite@8.0.16 → npm/tinyglobby@0.2.17 ℹ Read more on: This package | This alert | What is filesystem access? Next steps: Take a moment to review the security alert above. Review the linked package source code to understand the potential risk. Ensure the package is not malicious before proceeding. If you're unsure how to proceed, reach out to your security team or ask the Socket team for help at support@socket.dev. Suggestion: If a package must read the file system, clarify what it will read and ensure it reads only what it claims to. If appropriate, packages can leave file system access to consumers and operate on data passed to it instead. Mark the package as acceptable risk. To ignore this alert only in this pull request, reply with the comment @SocketSecurity ignore npm/tinyglobby@0.2.17. You can also ignore all packages with @SocketSecurity ignore-all. To ignore an alert for all future pull requests, use Socket's Dashboard to change the triage state of this alert.

View full report