Skip to content

Conversation

renovate[bot]
Copy link
Contributor

@renovate renovate bot commented Sep 16, 2025

Coming soon: The Renovate bot (GitHub App) will be renamed to Mend. PRs from Renovate will soon appear from 'Mend'. Learn more here.

This PR contains the following updates:

Package Change Age Adoption Passing Confidence
vite-5 (source) ^5.4.20 -> ^7.1.5 age adoption passing confidence

GitHub Vulnerability Alerts

CVE-2025-58752

Summary

Any HTML files on the machine were served regardless of the server.fs settings.

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)
  • appType: 'spa' (default) or appType: 'mpa' is used

This vulnerability also affects the preview server. The preview server allowed HTML files not under the output directory to be served.

Details

The serveStaticMiddleware function is in charge of serving static files from the server. It returns the viteServeStaticMiddleware function which runs the needed tests and serves the page. The viteServeStaticMiddleware function checks if the extension of the requested file is ".html". If so, it doesn't serve the page. Instead, the server will go on to the next middlewares, in this case htmlFallbackMiddleware, and then to indexHtmlMiddleware. These middlewares don't perform any test against allow or deny rules, and they don't make sure that the accessed file is in the root directory of the server. They just find the file and send back its contents to the client.

PoC

Execute the following shell commands:

npm  create  vite@latest
cd vite-project/
echo  "secret" > /tmp/secret.html
npm install
npm run dev

Then, in a different shell, run the following command:

curl -v --path-as-is 'http://localhost:5173/../../../../../../../../../../../tmp/secret.html'

The contents of /tmp/secret.html will be returned.

This will also work for HTML files that are in the root directory of the project, but are in the deny list (or not in the allow list). Test that by stopping the running server (CTRL+C), and running the following commands in the server's shell:

echo  'import path from "node:path"; import { defineConfig } from "vite"; export default defineConfig({server: {fs: {deny: [path.resolve(__dirname, "secret_files/*")]}}})'  >  [vite.config.js](http://vite.config.js)
mkdir secret_files
echo "secret txt" > secret_files/secret.txt
echo "secret html" > secret_files/secret.html
npm run dev

Then, in a different shell, run the following command:

curl -v --path-as-is 'http://localhost:5173/secret_files/secret.txt'

You will receive a 403 HTTP Response,  because everything in the secret_files directory is denied.

Now in the same shell run the following command:

curl -v --path-as-is 'http://localhost:5173/secret_files/secret.html'

You will receive the contents of secret_files/secret.html.

CVE-2025-58751

Summary

Files starting with the same name with the public directory were served bypassing the server.fs settings.

Impact

Only apps that match the following conditions are affected:

Details

The servePublicMiddleware function is in charge of serving public files from the server. It returns the viteServePublicMiddleware function which runs the needed tests and serves the page. The viteServePublicMiddleware function checks if the publicFiles variable is defined, and then uses it to determine if the requested page is public. In the case that the publicFiles is undefined, the code will treat the requested page as a public page, and go on with the serving function. publicFiles may be undefined if there is a symbolic link anywhere inside the public directory. In that case, every requested page will be passed to the public serving function. The serving function is based on the sirv library. Vite patches the library to add the possibility to test loading access to pages, but when the public page middleware disables this functionality since public pages are meant to be available always, regardless of whether they are in the allow or deny list.

In the case of public pages, the serving function is provided with the path to the public directory as a root directory. The code of the sirv library uses the join function to get the full path to the requested file. For example, if the public directory is "/www/public", and the requested file is "myfile", the code will join them to the string "/www/public/myfile". The code will then pass this string to the normalize function. Afterwards, the code will use the string's startsWith function to determine whether the created path is within the given directory or not. Only if it is, it will be served.

Since sirv trims the trailing slash of the public directory, the string's startsWith function may return true even if the created path is not within the public directory. For example, if the server's root is at "/www", and the public directory is at "/www/p", if the created path will be "/www/private.txt", the startsWith function will still return true, because the string "/www/private.txt" starts with  "/www/p". To achieve this, the attacker will use ".." to ask for the file "../private.txt". The code will then join it to the "/www/p" string, and will receive "/www/p/../private.txt". Then, the normalize function will return "/www/private.txt", which will then be passed to the startsWith function, which will return true, and the processing of the page will continue without checking the deny list (since this is the public directory middleware which doesn't check that).

PoC

Execute the following shell commands:

npm  create  vite@latest
cd vite-project/
mkdir p
cd p
ln -s a b
cd ..
echo  'import path from "node:path"; import { defineConfig } from "vite"; export default defineConfig({publicDir: path.resolve(__dirname, "p/"), server: {fs: {deny: [path.resolve(__dirname, "private.txt")]}}})' > vite.config.js
echo  "secret" > private.txt
npm install
npm run dev

Then, in a different shell, run the following command:

curl -v --path-as-is 'http://localhost:5173/private.txt'

You will receive a 403 HTTP Response,  because private.txt is denied.

Now in the same shell run the following command:

curl -v --path-as-is 'http://localhost:5173/../private.txt'

You will receive the contents of private.txt.

Related links


Release Notes

vitejs/vite (vite-5)

v7.1.5

Compare Source

Bug Fixes

v7.1.4

Compare Source

Bug Fixes
Miscellaneous Chores
Code Refactoring

v7.1.3

Compare Source

Features
Bug Fixes
Performance Improvements
Miscellaneous Chores
Code Refactoring
Tests

v7.1.2

Compare Source

Bug Fixes
Miscellaneous Chores

v7.1.1

Compare Source

Bug Fixes
Miscellaneous Chores

v7.1.0

Compare Source

Features
  • support files with more than 1000 lines by generateCodeFrame (#​20508) (e7d0b2a)
Bug Fixes
Tests

v7.0.7

Compare Source

Please refer to CHANGELOG.md for details.

v7.0.6

Compare Source

Bug Fixes
Miscellaneous Chores
Code Refactoring

v7.0.5

Compare Source

Bug Fixes
Miscellaneous Chores
Code Refactoring

v7.0.4

Compare Source

Bug Fixes
  • allow resolving bare specifiers to relative paths for entries (#​20379) (324669c)
Build System

v7.0.3

Compare Source

Bug Fixes
Miscellaneous Chores
Code Refactoring
  • minor changes to reduce diff between normal Vite and rolldown-vite (#​20354) (2e8050e)

v7.0.2

Compare Source

Bug Fixes

v7.0.1

Compare Source

Bug Fixes
Miscellaneous Chores

v7.0.0

Compare Source

v6.3.6

Compare Source

Please refer to CHANGELOG.md for details.

v6.3.5

Compare Source

v6.3.4

Compare Source

Bug Fixes
  • check static serve file inside sirv (#​19965) (c22c43d)
  • optimizer: return plain object when using require to import externals in optimized dependencies (#​19940) (efc5eab)
Code Refactoring

v6.3.3

Compare Source

v6.3.2

Compare Source

Features
Bug Fixes

v6.3.1

Compare Source

Bug Fixes

v6.3.0

Compare Source

v6.2.7

Compare Source

Please refer to CHANGELOG.md for details.

v6.2.6

Compare Source

Please refer to CHANGELOG.md for details.

v6.2.5

Compare Source

Please refer to CHANGELOG.md for details.

v6.2.4

Compare Source

Please refer to CHANGELOG.md for details.

v6.2.3

Compare Source

Please refer to CHANGELOG.md for details.

v6.2.2

Compare Source

v6.2.1

Compare Source

Features
  • add *?url&no-inline type and warning for .json?inline / .json?no-inline (#​19566) (c0d3667)
Bug Fixes
  • css: stabilize css module hashes with lightningcss in dev mode (#​19481) (92125b4)
  • deps: update all non-major dependencies (#​19555) (f612e0f)
  • reporter: fix incorrect bundle size calculation with non-ASCII characters (#​19561) (437c0ed)
  • sourcemap: combine sourcemaps with multiple sources without matched source (#​18971) (e3f6ae1)
  • ssr: named export should overwrite export all (#​19534) (2fd2fc1)
Performance Improvements
Miscellaneous Chores
Code Refactoring
Tests

v6.2.0

Compare Source

Bug Fixes
Miscellaneous Chores

v6.1.6

Compare Source

Please refer to CHANGELOG.md for details.

v6.1.5

Compare Source

Please refer to CHANGELOG.md for details.

v6.1.4

Compare Source

Please refer to CHANGELOG.md for details.

v6.1.3

Compare Source

Please refer to CHANGELOG.md for details.

v6.1.2

Compare Source

Please refer to CHANGELOG.md for details.

v6.1.1

Compare Source

Features
Bug Fixes
Miscellaneous Chores
Code Refactoring

v6.1.0

Compare Source

Features
Bug Fixes
Miscellaneous Chores
Code Refactoring

v6.0.15

Compare Source

Please refer to CHANGELOG.md for details.

v6.0.14

Compare Source

Please refer to CHANGELOG.md for details.

v6.0.13

Compare Source

Please refer to CHANGELOG.md for details.

v6.0.12

Compare Source

Please refer to CHANGELOG.md for details.

v6.0.11

Compare Source

Features

Configuration

📅 Schedule: Branch creation - "" in timezone America/New_York, Automerge - At any time (no schedule defined).

🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.

Rebasing: Whenever PR becomes conflicted, 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.

@cypress-app-bot
Copy link
Collaborator

See the guidelines for reviewing dependency updates for info on how to review dependency update PRs.

@renovate renovate bot force-pushed the renovate/npm-vite-5-vulnerability branch from 5e0f8ca to 4cb83c2 Compare September 16, 2025 19:42
@renovate renovate bot changed the title chore(deps): update dependency vite-5 to v6 [security] chore(deps): update dependency vite-5 to v7 [security] Sep 16, 2025
@@ -22,7 +22,7 @@
"devDependencies": {
"cross-env": "7.0.3",
"dedent": "^0.7.0",
"vite-5": "npm:vite@^5.4.20",
"vite-5": "npm:vite@^7.1.5",
Copy link

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Bug: Vite Package Alias Misalignment

The vite-5 package alias now points to Vite v7.1.5 instead of a v5.x version. This makes both vite-5 and vite-7 resolve to the same version, breaking the semantic naming convention and potentially causing unexpected behavior for code expecting Vite 5.x.

Fix in Cursor Fix in Web

@jennifer-shehane jennifer-shehane marked this pull request as draft September 16, 2025 20:07
@renovate renovate bot force-pushed the renovate/npm-vite-5-vulnerability branch from 4cb83c2 to 52e06c7 Compare September 16, 2025 22:42
@renovate renovate bot changed the title chore(deps): update dependency vite-5 to v7 [security] chore(deps): update dependency vite-5 to v6 [security] Sep 16, 2025
@renovate renovate bot force-pushed the renovate/npm-vite-5-vulnerability branch from 52e06c7 to 97432ba Compare September 16, 2025 22:49
@renovate renovate bot changed the title chore(deps): update dependency vite-5 to v6 [security] chore(deps): update dependency vite-5 to v7 [security] Sep 16, 2025
@renovate renovate bot force-pushed the renovate/npm-vite-5-vulnerability branch from 97432ba to 1abcf01 Compare September 17, 2025 13:42
@renovate renovate bot changed the title chore(deps): update dependency vite-5 to v7 [security] chore(deps): update dependency vite-5 to v6 [security] Sep 17, 2025
@renovate renovate bot force-pushed the renovate/npm-vite-5-vulnerability branch from 1abcf01 to 70a4322 Compare September 17, 2025 14:29
@renovate renovate bot changed the title chore(deps): update dependency vite-5 to v6 [security] chore(deps): update dependency vite-5 to v7 [security] Sep 17, 2025
@renovate renovate bot force-pushed the renovate/npm-vite-5-vulnerability branch from 70a4322 to fe4c40a Compare September 17, 2025 20:42
@renovate renovate bot changed the title chore(deps): update dependency vite-5 to v7 [security] chore(deps): update dependency vite-5 to v6 [security] Sep 17, 2025
@renovate renovate bot force-pushed the renovate/npm-vite-5-vulnerability branch from fe4c40a to 4fdc32d Compare September 17, 2025 20:48
@renovate renovate bot changed the title chore(deps): update dependency vite-5 to v6 [security] chore(deps): update dependency vite-5 to v7 [security] Sep 17, 2025
@renovate renovate bot force-pushed the renovate/npm-vite-5-vulnerability branch from 4fdc32d to dc837c7 Compare September 18, 2025 14:27
@renovate renovate bot changed the title chore(deps): update dependency vite-5 to v7 [security] chore(deps): update dependency vite-5 to v6 [security] Sep 18, 2025
@renovate renovate bot force-pushed the renovate/npm-vite-5-vulnerability branch from dc837c7 to 9d06487 Compare September 18, 2025 14:33
@renovate renovate bot changed the title chore(deps): update dependency vite-5 to v6 [security] chore(deps): update dependency vite-5 to v7 [security] Sep 18, 2025
@renovate renovate bot force-pushed the renovate/npm-vite-5-vulnerability branch from 9d06487 to ec4765a Compare September 18, 2025 14:42
@renovate renovate bot changed the title chore(deps): update dependency vite-5 to v7 [security] chore(deps): update dependency vite-5 to v6 [security] Sep 18, 2025
@renovate renovate bot force-pushed the renovate/npm-vite-5-vulnerability branch from ec4765a to 0f634a6 Compare September 18, 2025 14:56
@renovate renovate bot changed the title chore(deps): update dependency vite-5 to v6 [security] chore(deps): update dependency vite-5 to v7 [security] Sep 18, 2025
@renovate renovate bot force-pushed the renovate/npm-vite-5-vulnerability branch from 0f634a6 to e531465 Compare September 18, 2025 15:15
@renovate renovate bot changed the title chore(deps): update dependency vite-5 to v7 [security] chore(deps): update dependency vite-5 to v6 [security] Sep 18, 2025
@renovate renovate bot force-pushed the renovate/npm-vite-5-vulnerability branch 2 times, most recently from 8815342 to c7f8db9 Compare September 18, 2025 16:08
@renovate renovate bot changed the title chore(deps): update dependency vite-5 to v6 [security] chore(deps): update dependency vite-5 to v7 [security] Sep 23, 2025
@renovate renovate bot force-pushed the renovate/npm-vite-5-vulnerability branch from 993b945 to 409ee2f Compare September 23, 2025 14:58
@renovate renovate bot changed the title chore(deps): update dependency vite-5 to v7 [security] chore(deps): update dependency vite-5 to v6 [security] Sep 23, 2025
@renovate renovate bot force-pushed the renovate/npm-vite-5-vulnerability branch from 409ee2f to 7affeba Compare September 23, 2025 16:31
@renovate renovate bot changed the title chore(deps): update dependency vite-5 to v6 [security] chore(deps): update dependency vite-5 to v7 [security] Sep 23, 2025
@renovate renovate bot force-pushed the renovate/npm-vite-5-vulnerability branch from 7affeba to b825df9 Compare September 23, 2025 16:57
@renovate renovate bot changed the title chore(deps): update dependency vite-5 to v7 [security] chore(deps): update dependency vite-5 to v6 [security] Sep 23, 2025
@renovate renovate bot force-pushed the renovate/npm-vite-5-vulnerability branch from b825df9 to 1549003 Compare September 23, 2025 17:43
@renovate renovate bot changed the title chore(deps): update dependency vite-5 to v6 [security] chore(deps): update dependency vite-5 to v7 [security] Sep 23, 2025
@renovate renovate bot force-pushed the renovate/npm-vite-5-vulnerability branch from 1549003 to af54d8f Compare September 24, 2025 14:40
@renovate renovate bot changed the title chore(deps): update dependency vite-5 to v7 [security] chore(deps): update dependency vite-5 to v6 [security] Sep 24, 2025
@renovate renovate bot force-pushed the renovate/npm-vite-5-vulnerability branch from af54d8f to 5591d78 Compare September 24, 2025 14:47
@renovate renovate bot changed the title chore(deps): update dependency vite-5 to v6 [security] chore(deps): update dependency vite-5 to v7 [security] Sep 24, 2025
@renovate renovate bot force-pushed the renovate/npm-vite-5-vulnerability branch from 5591d78 to 31d43e6 Compare September 24, 2025 16:38
@renovate renovate bot changed the title chore(deps): update dependency vite-5 to v7 [security] chore(deps): update dependency vite-5 to v6 [security] Sep 24, 2025
@renovate renovate bot force-pushed the renovate/npm-vite-5-vulnerability branch from 31d43e6 to adbd83e Compare September 24, 2025 17:45
@renovate renovate bot changed the title chore(deps): update dependency vite-5 to v6 [security] chore(deps): update dependency vite-5 to v7 [security] Sep 24, 2025
@renovate renovate bot force-pushed the renovate/npm-vite-5-vulnerability branch from adbd83e to b1c8866 Compare September 25, 2025 14:29
@renovate renovate bot changed the title chore(deps): update dependency vite-5 to v7 [security] chore(deps): update dependency vite-5 to v6 [security] Sep 25, 2025
@renovate renovate bot force-pushed the renovate/npm-vite-5-vulnerability branch from b1c8866 to 9d32c57 Compare September 25, 2025 14:51
@renovate renovate bot changed the title chore(deps): update dependency vite-5 to v6 [security] chore(deps): update dependency vite-5 to v7 [security] Sep 25, 2025
@renovate renovate bot force-pushed the renovate/npm-vite-5-vulnerability branch from 9d32c57 to 9d79b45 Compare September 25, 2025 16:51
@renovate renovate bot changed the title chore(deps): update dependency vite-5 to v7 [security] chore(deps): update dependency vite-5 to v6 [security] Sep 25, 2025
@renovate renovate bot force-pushed the renovate/npm-vite-5-vulnerability branch from 9d79b45 to 1b18855 Compare September 25, 2025 16:57
@renovate renovate bot changed the title chore(deps): update dependency vite-5 to v6 [security] chore(deps): update dependency vite-5 to v7 [security] Sep 25, 2025
@renovate renovate bot force-pushed the renovate/npm-vite-5-vulnerability branch from 1b18855 to 1778fc0 Compare September 25, 2025 19:50
@renovate renovate bot changed the title chore(deps): update dependency vite-5 to v7 [security] chore(deps): update dependency vite-5 to v6 [security] Sep 25, 2025
@renovate renovate bot force-pushed the renovate/npm-vite-5-vulnerability branch from 1778fc0 to 06b5037 Compare September 25, 2025 19:57
@renovate renovate bot changed the title chore(deps): update dependency vite-5 to v6 [security] chore(deps): update dependency vite-5 to v7 [security] Sep 25, 2025
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