CVE-2026-112944
launch-editor allows users to open files with line numbers in …
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.
What to do now
- Check your exposureFind out whether the affected software runs anywhere in your environment, including systems of suppliers.
- UpdateInstall the version in which the vendor fixed the vulnerability. The references lead to the advisory.
- Limit access until thenIf you cannot update at once, take the system off the internet or restrict who can reach it.
References
- github.com/vitejs/launch-editor/commit/f6e6701bb1f16f2dd242b321374f1b6cca6eb6d4
- github.com/vitejs/launch-editor/pull/156
- github.com/vitejs/launch-editor/releases/tag/v2.14.2
- github.com/vitejs/launch-editor/security/advisories/GHSA-r825-w8mm-5pxw
- nvd.nist.gov/vuln/detail/CVE-2026-112944
- github.com/advisories/GHSA-r825-w8mm-5pxw
- nvd.nist.gov/vuln/detail/CVE-2026-112944
- cve.org/CVERecord?id=CVE-2026-112944
Data: CVE list and the NVD. This product uses data from the NVD API but is not endorsed or certified by the NVD.