Skip to content

fix(security): upgrade vite to ^6.4.2 — fix Arbitrary File Read via WebSocket [HIGH]#6

Open
aarlint wants to merge 1 commit intomainfrom
yeet/fix-vite
Open

fix(security): upgrade vite to ^6.4.2 — fix Arbitrary File Read via WebSocket [HIGH]#6
aarlint wants to merge 1 commit intomainfrom
yeet/fix-vite

Conversation

@aarlint
Copy link
Copy Markdown
Owner

@aarlint aarlint commented Apr 28, 2026

Security Fix: Vite Arbitrary File Read via WebSocket (HIGH)

Scanner & Findings

Finding ID Source Severity Advisory
c003596a52017408 npm-audit HIGH GHSA-p9ff-h696-f583

Vulnerability Fixed

  • GHSA-p9ff-h696-f583: vite >=6.0.0 <=6.4.1 — Vite Dev Server WebSocket vulnerability allows arbitrary file read. An attacker with network access to the dev server could read files outside the project root through a crafted WebSocket message.

What Changed

vite is a direct devDependency. The installed version was 6.4.1, which is in the vulnerable range >=6.0.0 <=6.4.1.

Updated the vite version specifier in package.json from ^6.2.0 to ^6.4.2, then ran npm install. The lockfile now resolves vite at 6.4.2.

-    "vite": "^6.2.0"
+    "vite": "^6.4.2"

Why This Is Safe

vite uses semantic versioning. Moving from 6.4.1 to 6.4.2 is a patch release — no breaking changes. The project's existing build configuration and plugins remain compatible.

Manual Verification Steps

  1. Check out this branch and run npm ci.
  2. Confirm npm ls vite shows version 6.4.2.
  3. Run npm audit — the vite advisory GHSA-p9ff-h696-f583 should no longer appear.
  4. Run npm run build to confirm the build still succeeds.
  5. (Optional) Run npm run dev and verify the dev server starts correctly.

Scan Run Reference

Scan date: 2026-04-28, commit 8f4e82e. Full summary: VULN-2 scan artifacts.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant