CVE-2026-112944: launch-editor: Editor CLI flag misinterpretation causing arbitrary command execution for some editors
Summary launch-editor forwarded file paths directly to editors without sanitization. If a path resembles a CLI flag, editors like Vim may interpret it as a command, potentially causing unintended file overwrites or command execution. Impact Direct launch-editor users Only apps that match all of the following conditions are affected: - The attacker is able to create a file system entry (e.g.
Published Oct 20, 2026
Affected packages
launch-editor
- Ecosystem
- npm
- Affected
- <= 2.14.1
- Fixed in
- 2.14.2
- Check
npm ls launch-editor
vite
- Ecosystem
- npm
- Affected
- >= 8.3.0, <= 8.3.2
- Fixed in
- 8.3.3
- Check
npm ls vite
vite
- Ecosystem
- npm
- Affected
- >= 8.2.0, <= 8.2.3
- Fixed in
- 8.2.4
- Check
npm ls vite
vite
- Ecosystem
- npm
- Affected
- >= 8.0.0, <= 8.1.5
- Fixed in
- 8.1.6
- Check
npm ls vite
vite
- Ecosystem
- npm
- Affected
- >= 7.0.0, <= 7.3.6
- Fixed in
- 7.3.7
- Check
npm ls vite
vite
- Ecosystem
- npm
- Affected
- <= 6.4.3
- Fixed in
- 6.4.4
- Check
npm ls vite
vite-plus
- Ecosystem
- npm
- Affected
- <= 1.0.0
- Fixed in
- 1.1.0
- Check
npm ls vite-plus
Advisory details
From the GitHub Advisory Database (CC BY 4.0).
Summary
launch-editor forwarded file paths directly to editors without sanitization. If a path resembles a CLI flag, editors like Vim may interpret it as a command, potentially causing unintended file overwrites or command execution.
Impact
Direct launch-editor users
Only apps that match all of the following conditions are affected:
- The attacker is able to create a file system entry (e.g. a file or directory) starting with
+or-in the working directory - The user uses or the app specifies any of the following editors:
- Vim (including gVim)
- MacVim
- Emacs (including Emacsclient)
- Notepad++ (only if using a plugin exposing dangerous operations via plugin messages)
- The first argument of
launchEditorcan start with+or-or the user is using WSL
launch-editor-middleware users
Only apps that match the following conditions are affected:
- The attacker is able to create a file system entry (e.g. a file or directory) starting with
+or-in the working directory - The user uses or the app specifies any of the following editors:
- Vim (including gVim)
- MacVim
- Emacs (including Emacsclient)
- Notepad++ (only if using a plugin exposing dangerous operations via plugin messages)
- launch-editor older than v2.2.0 is used, or the user is using WSL
Vite users
Only apps that match the following conditions are affected:
- The attacker is able to create a file system entry (e.g. a file or directory) starting with
+or-in the working directory - The user uses or the app specifies any of the following editors:
- Vim (including gVim)
- MacVim
- Emacs (including Emacsclient)
- Notepad++ (only if using a plugin exposing dangerous operations via plugin messages)
- The user is using WSL
Details
launchEditor(file) function passes the file name as-is to the editor if the file with that file name exists. If the file name starts with - (also + for Vim), the editor treats them as flags rather than positional arguments. For example, Vim treats arguments starting with + as an Ex command. As a result, an existing relative directory such as:
+call writefile(["SAFE_MARKER"],"LAUNCH_EDITOR_MARKER")|qa!is not treated as a filename when passed to Vim. Vim executes the embedded Ex command.
The following editor has a potentially destructive operation exposed to the CLI arguments:
- Vim (including gVim)
- MacVim
- Emacs (including Emacsclient)
- Notepad++ (only if using a plugin exposing dangerous operations via plugin messages)
launch-editor-middleware v2.2.0+ converts the passed file path to an absolute path so those are not affected as long as the user is not using WSL. For WSL, launch-editor converts the paths to relative paths internally, so those are still affected.
Vite 2.0.0+ uses launch-editor-middleware v2.2.0+ so the WSL users are only affected.
Credited to 0xazanul, bluwy.
References
- https://github.com/vitejs/launch-editor/security/advisories/GHSA-r825-w8mm-5pxw
- https://nvd.nist.gov/vuln/detail/CVE-2026-112944
- https://github.com/vitejs/launch-editor/pull/156
- https://github.com/vitejs/launch-editor/commit/f6e6701bb1f16f2dd242b321374f1b6cca6eb6d4
- https://github.com/vitejs/launch-editor/releases/tag/v2.14.2
- https://github.com/advisories/GHSA-r825-w8mm-5pxw
How this page is made: the data panel comes from the GitHub Advisory Database, CISA’s KEV catalog, the NVD and FIRST EPSS, and updates twice a day. No analysis has been written for this entry yet. Methodology
More npm vulnerabilities
All npm entriesCVE-2026-118662
Vite: `server.fs.deny` bypassed with queries
medium6.9Oct 29, 2026CVE-2026-112945
Vite: Cross origin script execution through Vite custom middleware
low2.1Oct 21, 2026CVE-2026-112946
Vite: Files outside `server.fs.allow` could be served when project paths match system paths on non-Windows machine
medium6.3Oct 21, 2026CVE-2026-112947
Vite: First 4 bytes of files outside of `server.fs` setting is exposed by `?vite-wasm-instance`
medium6.3Oct 21, 2026CVE-2026-112948
Vitest: Servers misapply `server.fs.deny`, serving `.env`, private keys, `.git`, and the API token file
medium6.5Oct 21, 2026CVE-2026-112942
launch-editor: `fs.existsSync()` existence check can be bypassed on Windows
high7.5Oct 20, 2026
