Skip to content

chore(deps): update dependency vite to v6.4.1 [security]#29

Merged
renovate[bot] merged 1 commit intomainfrom
renovate/npm-vite-vulnerability
Nov 29, 2025
Merged

chore(deps): update dependency vite to v6.4.1 [security]#29
renovate[bot] merged 1 commit intomainfrom
renovate/npm-vite-vulnerability

Conversation

@renovate
Copy link
Contributor

@renovate renovate bot commented Nov 27, 2025

This PR contains the following updates:

Package Change Age Adoption Passing Confidence
vite (source) 6.3.6 -> 6.4.1 age adoption passing confidence

GitHub Vulnerability Alerts

CVE-2025-62522

Summary

Files denied by server.fs.deny were sent if the URL ended with \ when the dev server is running on Windows.

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)
  • running the dev server on Windows

Details

server.fs.deny can contain patterns matching against files (by default it includes .env, .env.*, *.{crt,pem} as such patterns). These patterns were able to bypass by using a back slash(\). The root cause is that fs.readFile('/foo.png/') loads /foo.png.

PoC

npm create vite@latest
cd vite-project/
cat "secret" > .env
npm install
npm run dev
curl --request-target /.env\ http://localhost:5173
image

Release Notes

vitejs/vite (vite)

v6.4.1

Compare Source

Please refer to CHANGELOG.md for details.

v6.4.0

Compare Source

Please refer to CHANGELOG.md for details.

v6.3.7

Compare Source

Please refer to CHANGELOG.md for details.


Configuration

📅 Schedule: Branch creation - "" (UTC), 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 was generated by Mend Renovate. View the repository job log.

@github-actions
Copy link
Contributor

🔗 Redirect URIs Added to Logto

The following redirect URIs have been automatically added to the Logto application configuration:

Redirect URIs:

  • https://my-frontend-qa-pr-29.onrender.com/login-redirect
  • https://my-proxy-qa-pr-29.onrender.com/login-redirect

Post-logout redirect URIs:

  • https://my-frontend-qa-pr-29.onrender.com/login
  • https://my-proxy-qa-pr-29.onrender.com/login

These will be automatically removed when the PR is closed or merged.

@github-actions
Copy link
Contributor

github-actions bot commented Nov 27, 2025

ℹ️ API content change detected:

No structural change, nothing to display.

Preview documentation

Powered by Bump.sh

@renovate renovate bot force-pushed the renovate/npm-vite-vulnerability branch from 1c9f149 to cfaa99c Compare November 29, 2025 04:06
@edospadoni edospadoni temporarily deployed to renovate/npm-vite-vulnerability - my-frontend-qa PR #29 November 29, 2025 04:06 — with Render Destroyed
@renovate renovate bot merged commit 578985d into main Nov 29, 2025
11 checks passed
@renovate renovate bot deleted the renovate/npm-vite-vulnerability branch November 29, 2025 05:13
@github-actions
Copy link
Contributor

🗑️ Redirect URIs Removed from Logto

The following redirect URIs have been automatically removed from the Logto application configuration:

Redirect URIs:

  • https://my-frontend-qa-pr-29.onrender.com/login-redirect
  • https://my-proxy-qa-pr-29.onrender.com/login-redirect

Post-logout redirect URIs:

  • https://my-frontend-qa-pr-29.onrender.com/login
  • https://my-proxy-qa-pr-29.onrender.com/login

Cleanup completed for PR #29.

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