Medium severity · published Oct 20, 2026
CVE-2026-112944
launch-editor: Editor CLI flag misinterpretation causing arbitrary command execution for some editors
6.3
CVSS
0.7%
EPSS
No
On KEV
Description
launch-editor allows users to open files with line numbers in editor from Node.js. Prior to 2.14.2, when an attacker can create a filesystem entry beginning with plus or minus in the working directory, an affected editor is selected, and the path can remain relative or is converted to a relative WSL path, launchEditor forwards the path without forcing it to be interpreted as a positional filename. Editor option parsing then treats the attacker-controlled filename as a command-line flag, which can cause unintended file overwrite or arbitrary command execution by the selected editor. The affected editors are Vim and gVim, MacVim, Emacs and Emacsclient, and Notepad++ when a plugin exposes dangerous operations; WSL path conversion keeps Vite and newer middleware callers exposed. This issue is fixed in version 2.14.2.
Exploitation
Is it being used?
Exploit prediction (EPSS)0.7% · higher than 53% of CVEs
Exploited in the wildNo evidence yet
CISA KEVNot listed
Ransomware campaign useNot known
Affected products
Which versions
LA
launch-editor · vitejs
< 2.14.2 · source: vendor
VI
vite · vitejs
>= 8.3.0, < 8.3.3; >= 8.2.0, < 8.2.4; >= 8.0.0, < 8.1.6; >= 7.0.0, < 7.3.7; < 6.4.4 · source: vendor
VI
vite-plus · vitejs
< 1.1.0 · source: vendor
Affected product
LA
launch-editor
vitejs
More from launch-editor
8.3
CVE-2024-52011
launch-editor vulnerable to command injection via the crafted request on Windows
7.5
CVE-2026-112942
launch-editor: `fs.existsSync()` existence check can be bypassed on Windows
6.3
CVE-2026-112943
launch-editor: escapeCmdArgs() omits % escaping on Windows
5.5
CVE-2026-53632
NTLMv2 hash disclosure via UNC path handling on Windows