Skip to content

Conversation

renovate[bot]
Copy link
Contributor

@renovate renovate bot commented May 10, 2025

This PR contains the following updates:

Package Change Age Confidence
vite (source) 6.1.3 -> 6.3.6 age confidence

GitHub Vulnerability Alerts

CVE-2025-31486

Summary

The contents of arbitrary files can be returned to the browser.

Impact

Only apps explicitly exposing the Vite dev server to the network (using --host or server.host config option) are affected.

Details

.svg

Requests ending with .svg are loaded at this line.
https://github.com/vitejs/vite/blob/037f801075ec35bb6e52145d659f71a23813c48f/packages/vite/src/node/plugins/asset.ts#L285-L290
By adding ?.svg with ?.wasm?init or with sec-fetch-dest: script header, the restriction was able to bypass.

This bypass is only possible if the file is smaller than build.assetsInlineLimit (default: 4kB) and when using Vite 6.0+.

relative paths

The check was applied before the id normalization. This allowed requests to bypass with relative paths (e.g. ../../).

PoC

npm create vite@latest
cd vite-project/
npm install
npm run dev

send request to read etc/passwd

curl 'http://127.0.0.1:5173/etc/passwd?.svg?.wasm?init'
curl 'http://127.0.0.1:5173/@​fs/x/x/x/vite-project/?/../../../../../etc/passwd?import&?raw'

CVE-2025-32395

Summary

The contents of arbitrary files can be returned to the browser if the dev server is running on Node or Bun.

Impact

Only apps with the following conditions are affected.

  • explicitly exposing the Vite dev server to the network (using --host or server.host config option)
  • running the Vite dev server on runtimes that are not Deno (e.g. Node, Bun)

Details

HTTP 1.1 spec (RFC 9112) does not allow # in request-target. Although an attacker can send such a request. For those requests with an invalid request-line (it includes request-target), the spec recommends to reject them with 400 or 301. The same can be said for HTTP 2 (ref1, ref2, ref3).

On Node and Bun, those requests are not rejected internally and is passed to the user land. For those requests, the value of http.IncomingMessage.url contains #. Vite assumed req.url won't contain # when checking server.fs.deny, allowing those kinds of requests to bypass the check.

On Deno, those requests are not rejected internally and is passed to the user land as well. But for those requests, the value of http.IncomingMessage.url did not contain #.

PoC

npm create vite@latest
cd vite-project/
npm install
npm run dev

send request to read /etc/passwd

curl --request-target /@​fs/Users/doggy/Desktop/vite-project/#/../../../../../etc/passwd http://127.0.0.1:5173

CVE-2025-46565

Summary

The contents of files in the project root that are denied by a file matching pattern can be returned to the browser.

Impact

Only apps explicitly exposing the Vite dev server to the network (using --host or server.host config option) are affected.
Only files that are under project root and are denied by a file matching pattern can be bypassed.

  • Examples of file matching patterns: .env, .env.*, *.{crt,pem}, **/.env
  • Examples of other patterns: **/.git/**, .git/**, .git/**/*

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 for files under root by using a combination of slash and dot (/.).

PoC

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

image
image

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

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.


Release Notes

vitejs/vite (vite)

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.


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.

@renovate renovate bot added the Type: Dependency Dependencies fixes label May 10, 2025
Copy link

coderabbitai bot commented May 10, 2025

Important

Review skipped

Bot user detected.

To trigger a single review, invoke the @coderabbitai review command.

You can disable this status message by setting the reviews.review_status to false in the CodeRabbit configuration file.


Comment @coderabbitai help to get the list of available commands and usage tips.

Copy link

cloudflare-workers-and-pages bot commented May 10, 2025

Deploying vue-i18n-next with  Cloudflare Pages  Cloudflare Pages

Latest commit: 96f4858
Status: ✅  Deploy successful!
Preview URL: https://f16eea15.vue-i18n-next.pages.dev
Branch Preview URL: https://renovate-npm-vite-vulnerabil.vue-i18n-next.pages.dev

View logs

Copy link

github-actions bot commented May 10, 2025

Size Report

Bundles

File Size Gzip Brotli
core.esm-browser.prod.js 38.22 kB 11.67 kB 10.41 kB
core.global.prod.js 31.24 kB 10.82 kB 9.70 kB
core.runtime.esm-browser.prod.js 23.77 kB 7.70 kB 6.90 kB
core.runtime.global.prod.js 18.08 kB 7.03 kB 6.31 kB
message-compiler.esm-browser.prod.js 19.45 kB 5.81 kB 5.18 kB
message-compiler.global.prod.js 17.46 kB 5.59 kB 5.01 kB
petite-vue-i18n-core.esm-browser.prod.js 20.70 kB 6.98 kB 6.27 kB
petite-vue-i18n-core.global.prod.js 15.66 kB 6.08 kB 5.51 kB
petite-vue-i18n.esm-browser.prod.js 37.17 kB 11.41 kB 10.23 kB
petite-vue-i18n.global.prod.js 30.00 kB 10.26 kB 9.24 kB
petite-vue-i18n.runtime.esm-browser.prod.js 22.58 kB 7.35 kB 6.64 kB
petite-vue-i18n.runtime.global.prod.js 16.86 kB 6.42 kB 5.82 kB
vue-i18n.esm-browser.prod.js 50.87 kB 15.22 kB 13.58 kB
vue-i18n.global.prod.js 40.71 kB 13.67 kB 12.29 kB
vue-i18n.runtime.esm-browser.prod.js 36.28 kB 11.17 kB 10.03 kB
vue-i18n.runtime.global.prod.js 27.56 kB 9.88 kB 8.91 kB

Usages

Name Size Gzip Brotli
packages/size-check-core (@intlify/core) 9.22 kB (+0.00 kB) 3.83 kB (+0.00 kB) 3.46 kB
packages/size-check-petite-vue-i18n (petite-vue-i18n) 78.13 kB (+0.00 kB) 30.46 kB (+0.00 kB) 27.47 kB (+0.03 kB)
packages/size-check-vue-i18n (vue-i18n) 83.34 kB (+0.00 kB) 31.94 kB (+0.00 kB) 28.74 kB (+0.03 kB)

Copy link

pkg-pr-new bot commented May 10, 2025

Open in StackBlitz

@intlify/core

npm i https://pkg.pr.new/@intlify/core@2185

@intlify/core-base

npm i https://pkg.pr.new/@intlify/core-base@2185

@intlify/devtools-types

npm i https://pkg.pr.new/@intlify/devtools-types@2185

@intlify/message-compiler

npm i https://pkg.pr.new/@intlify/message-compiler@2185

petite-vue-i18n

npm i https://pkg.pr.new/petite-vue-i18n@2185

@intlify/shared

npm i https://pkg.pr.new/@intlify/shared@2185

vue-i18n

npm i https://pkg.pr.new/vue-i18n@2185

@intlify/vue-i18n-core

npm i https://pkg.pr.new/@intlify/vue-i18n-core@2185

commit: 96f4858

@renovate renovate bot force-pushed the renovate/npm-vite-vulnerability branch from ae83c5f to 427e1d0 Compare May 28, 2025 07:10
@renovate renovate bot force-pushed the renovate/npm-vite-vulnerability branch from 427e1d0 to 23f9eff Compare June 4, 2025 08:21
@renovate renovate bot force-pushed the renovate/npm-vite-vulnerability branch 2 times, most recently from c7fe962 to 6ed1705 Compare June 22, 2025 22:12
@renovate renovate bot force-pushed the renovate/npm-vite-vulnerability branch from 6ed1705 to 305fb30 Compare July 2, 2025 14:59
@renovate renovate bot force-pushed the renovate/npm-vite-vulnerability branch 2 times, most recently from 7b4169b to 5a41236 Compare July 27, 2025 21:05
@renovate renovate bot force-pushed the renovate/npm-vite-vulnerability branch 2 times, most recently from c89d675 to 78d6aab Compare August 13, 2025 14:43
@renovate renovate bot force-pushed the renovate/npm-vite-vulnerability branch from 78d6aab to 75daecf Compare August 19, 2025 19:02
@renovate renovate bot force-pushed the renovate/npm-vite-vulnerability branch from 75daecf to fa919a6 Compare August 31, 2025 10:04
@renovate renovate bot force-pushed the renovate/npm-vite-vulnerability branch from fa919a6 to 96f4858 Compare September 10, 2025 02:42
@renovate renovate bot changed the title chore(deps): update dependency vite to v6.2.7 [security] chore(deps): update dependency vite to v6.3.6 [security] Sep 10, 2025
@renovate renovate bot merged commit 341ecee into master Sep 10, 2025
31 checks passed
@renovate renovate bot deleted the renovate/npm-vite-vulnerability branch September 10, 2025 05:13
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Type: Dependency Dependencies fixes
Projects
None yet
Development

Successfully merging this pull request may close these issues.

0 participants