chore(deps): bump vite to 6.4.3 (security)#58
Merged
Conversation
Resolves two Dependabot alerts: - GHSA-fx2h-pf6j-xcff (high): vite server.fs.deny bypass on Windows alternate paths - GHSA-v6wh-96g9-6wx3 (medium): launch-editor NTLMv2 hash disclosure via UNC paths on Windows Both CVEs affect Vite's dev server on Windows only. This project uses Vite for the production build (`npm run build`), not as a live dev server (`npm run serve` runs http-server), so practical exposure is nil. Bumping anyway to clear the alerts and live up to the SECURITY.md "continuous scanning" claim. Lockfile-only change; declared range `^6.0.0` already permits 6.4.3. Verified: `npm run build` passes.
Contributor
Deploying xsltdebugx with
|
| Latest commit: |
724ee32
|
| Status: | ✅ Deploy successful! |
| Preview URL: | https://0a46e378.xsltdebugx.pages.dev |
| Branch Preview URL: | https://chore-bump-vite-6-4-3.xsltdebugx.pages.dev |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
What
Bumps Vite from 6.4.2 → 6.4.3 to resolve two Dependabot alerts.
server.fs.denybypass on Windows alternate pathsPractical exposure
Both CVEs affect Vite's dev server on Windows. This project uses Vite only for the production build (
npm run build);npm run serveuses http-server, not Vite dev. So practical exposure was nil — bumping to clear the alerts and live up to theSECURITY.md"continuous scanning" claim.Diff
Lockfile-only change; the declared range
^6.0.0inpackage.jsonalready permits 6.4.3, so no manifest edit needed.Verification
npm run buildpasses locally (Vite 6.4.3, 172ms, expected output).