launch-editor vulnerable to command injection via the crafted request on Windows
Published 3 Jun 2026 · Updated 10 Sept 2026
Affected packages
- Affected
- <2.9.0
- Fixed in
- 2.9.0
npm install launch-editor@2.9.0- Affected
- <5.4.9
- Fixed in
- 5.4.9
npm install vite@5.4.9Details
Summary
Due to the insufficient sanitization of the file argument in the launchEditor, an attacker can execute arbitrary commands on Windows by supplying a filename that contains special characters.
Impact
If the following conditions are met, an attacker can execute arbitrary commands on the computer that is using the launch-editor:
- An attacker can place a file with the malicious filename
- An attacker can call the
launchEditormethod with thefileargument controlled - The
launch-editorpackage is running on Windows
For example, some development server using this package satisfy these conditions, as a malicious website might be able to force the downloading of a file and the path of that file is predictable.
Patch
This issue has been fixed in the launch-editor version 2.9.0 (commit).
Is GHSA-c27g-q93r-2cwf in any of your client repos?
Checking one package by hand is fine. Checking it across forty client projects is not. NPMscan reads the lockfiles in every GitHub repo you pick, finds each project with an affected launch-editor, and gives you the command that fixes it.
References
- Linkgithub.com/vitejs/launch-editor/security/advisories/GHSA-c27g-q93r-2cwf
- Linkgithub.com/yyx990803/launch-editor/security/advisories/GHSA-c27g-q93r-2cwf
- Advisorynvd.nist.gov/vuln/detail/CVE-2024-52011
- Linkgithub.com/vitejs/launch-editor/commit/971291e8a6a91226e1616c5c0ec85423d2d50a5e
- Packagegithub.com/vitejs/launch-editor
Advisory data from OSV.dev (opens OSV.dev in a new tab), refreshed daily.