Skip to content

Update dependency vite to v7 [SECURITY]#11264

Merged
nbudin merged 1 commit intomainfrom
renovate/npm-vite-vulnerability
Apr 7, 2026
Merged

Update dependency vite to v7 [SECURITY]#11264
nbudin merged 1 commit intomainfrom
renovate/npm-vite-vulnerability

Conversation

@nbudin
Copy link
Copy Markdown
Contributor

@nbudin nbudin commented Apr 7, 2026

ℹ️ Note

This PR body was truncated due to platform limits.

This PR contains the following updates:

Package Change Age Confidence
vite (source) ^6.4.2^7.0.0 age confidence

GitHub Vulnerability Alerts

CVE-2026-39364

Summary

The contents of files that are specified by server.fs.deny can be returned to the browser.

Impact

Only apps that match the following conditions are affected:

Details

On the Vite dev server, files that should be blocked by server.fs.deny (e.g., .env, *.crt) can be retrieved with HTTP 200 responses when query parameters such as ?raw, ?import&raw, or ?import&url&inline are appended.

PoC

  1. Start the dev server: pnpm exec vite root --host 127.0.0.1 --port 5175 --strictPort
  2. Confirm that server.fs.deny is enforced (expect 403): curl -i http://127.0.0.1:5175/src/.env | head -n 20
    image
  3. Confirm that the same files can be retrieved with query parameters (expect 200):
    image

CVE-2026-39363

Summary

server.fs check was not enforced to the fetchModule method that is exposed in Vite dev server's WebSocket.

Impact

Only apps that match the following conditions are affected:

  • explicitly exposes the Vite dev server to the network (using --host or server.host config option)
  • WebSocket is not disabled by server.ws: false

Arbitrary files on the server (development machine, CI environment, container, etc.) can be exposed.

Details

If it is possible to connect to the Vite dev server’s WebSocket without an Origin header, an attacker can invoke fetchModule via the custom WebSocket event vite:invoke and combine file://... with ?raw (or ?inline) to retrieve the contents of arbitrary files on the server as a JavaScript string (e.g., export default "...").

The access control enforced in the HTTP request path (such as server.fs.allow) is not applied to this WebSocket-based execution path.

PoC

  1. Start the dev server on the target
    Example (used during validation with this repository):

    pnpm -C playground/alias exec vite --host 0.0.0.0 --port 5173
  2. Confirm that access is blocked via the HTTP path (example: arbitrary file)

    curl -i 'http://localhost:5173/@​fs/etc/passwd?raw'

    Result: 403 Restricted (outside the allow list)
    image

  3. Confirm that the same file can be retrieved via the WebSocket path
    By connecting to the HMR WebSocket without an Origin header and sending a vite:invoke request that calls fetchModule with a file://... URL and ?raw, the file contents are returned as a JavaScript module.

image image

CVE-2026-39365

Summary

Any files ending with .map even out side the project can be returned to the browser.

Impact

Only apps that match the following conditions are affected:

  • explicitly exposes the Vite dev server to the network (using --host or server.host config option)
  • have a sensitive content in files ending with .map and the path is predictable

Details

In Vite v7.3.1, the dev server’s handling of .map requests for optimized dependencies resolves file paths and calls readFile without restricting ../ segments in the URL. As a result, it is possible to bypass the server.fs.strict allow list and retrieve .map files located outside the project root, provided they can be parsed as valid source map JSON.

PoC

  1. Create a minimal PoC sourcemap outside the project root
    cat > /tmp/poc.map <<'EOF'
    {"version":3,"file":"x.js","sources":[],"names":[],"mappings":""}
    EOF
  2. Start the Vite dev server (example)
    pnpm -C playground/fs-serve dev --host 127.0.0.1 --port 18080
  3. Confirm that direct /@&#8203;fs access is blocked by strict (returns 403)
    image
  4. Inject ../ segments under the optimized deps .map URL prefix to reach /tmp/poc.map
    image

Release Notes

vitejs/vite (vite)

v7.3.2

Compare Source

Please refer to CHANGELOG.md for details.

v7.3.1

Compare Source

Features

v7.3.0

Compare Source

Features

v7.2.7

Compare Source

Bug Fixes

v7.2.6

Compare Source

7.2.6 (2025-12-01)

v7.2.4

Compare Source

Vite 8 is here!

Today, we're thrilled to announce the release of the next Vite major:

⚠ BREAKING CHANGES
  • remove import.meta.hot.accept resolution fallback (#​21382)
  • update default browser target (#​21193)
  • the epic rolldown-vite merge (#​21189)
Features
Bug Fixes
Performance Improvements
Documentation
Miscellaneous Chores
Code Refactoring
Tests
Beta Changelogs
8.0.0-beta.18 (2026-03-09)

See 8.0.0-beta.18 changelog

8.0.0-beta.17 (2026-03-09)

See 8.0.0-beta.17 changelog

8.0.0-beta.16 (2026-02-27)

See 8.0.0-beta.16 changelog

8.0.0-beta.15 (2026-02-19)

See 8.0.0-beta.15 changelog

8.0.0-beta.14 (2026-02-12)

See 8.0.0-beta.14 changelog

8.0.0-beta.13 (2026-02-05)

See 8.0.0-beta.13 changelog

8.0.0-beta.12 (2026-02-03)

See 8.0.0-beta.12 changelog

8.0.0-beta.11 (2026-01-29)

See 8.0.0-beta.11 changelog

8.0.0-beta.10 (2026-01-24)

See 8.0.0-beta.10 changelog

8.0.0-beta.9 (2026-01-22)

See 8.0.0-beta.9 changelog

8.0.0-beta.8 (2026-01-15)

See 8.0.0-beta.8 changelog

8.0.0-beta.7 (2026-01-08)

See 8.0.0-beta.7 changelog

8.0.0-beta.6 (2026-01-07)

See 8.0.0-beta.6 changelog

8.0.0-beta.5 (2025-12-25)

See 8.0.0-beta.5 changelog

8.0.0-beta.4 (2025-12-22)

See 8.0.0-beta.4 changelog

8.0.0-beta.3 (2025-12-18)

See 8.0.0-beta.3 changelog

8.0.0-beta.2 (2025-12-12)

See 8.0.0-beta.2 changelog

8.0.0-beta.1 (2025-12-08)

See 8.0.0-beta.1 changelog

8.0.0-beta.0 (2025-12-03)

See 8.0.0-beta.0 changelog

Rolldown-Vite changelogs

See rolldown-vite changelog

v7.2.3

Compare Source

Bug Fixes
Performance Improvements
Miscellaneous Chores

v7.2.2

Compare Source

Bug Fixes

v7.2.1

Compare Source

Vite 8 is here!

Today, we're thrilled to announce the release of the next Vite major:

⚠ BREAKING CHANGES
  • remove import.meta.hot.accept resolution fallback (#​21382)
  • update default browser target (#​21193)
  • the epic rolldown-vite merge (#​21189)
Features
Bug Fixes

Configuration

📅 Schedule: (UTC)

  • Branch creation
    • ""
  • Automerge
    • At any time (no schedule defined)

🚦 Automerge: Enabled.

Rebasing: Whenever PR is behind base branch, or you tick the rebase/retry checkbox.

🔕 Ignore: Close this PR and you won't be reminded about this update again.


  • If you want to rebase/retry this PR, check this box

This PR has been generated by Renovate Bot.

@nbudin nbudin force-pushed the renovate/npm-vite-vulnerability branch from 617d881 to 44da48f Compare April 7, 2026 15:52
@github-actions
Copy link
Copy Markdown
Contributor

github-actions bot commented Apr 7, 2026

Code Coverage Report: Only Changed Files listed

Package Base Coverage New Coverage Difference
Overall Coverage 🟢 53.11% 🟢 53.11% ⚪ 0%

Minimum allowed coverage is 0%, this run produced 53.11%

@nbudin nbudin merged commit 6861fa7 into main Apr 7, 2026
18 checks passed
@nbudin nbudin deleted the renovate/npm-vite-vulnerability branch April 7, 2026 15:59
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant