Launch Editor
Approved changes feed: RSS · Atom
cpe:2.3:a:vitejs:launch-editor:*:*:*:*:*:*:*:*part: a version: * update: *
| Vendor | Vitejs (b10f11ec-417f-5fda-b8a2-04cf03a82c2a) |
|---|---|
| Product | Launch Editor (88975185-312d-5c83-925c-9808c9422455) |
| Edition | * |
| Language | * |
| Software edition | * |
| Target software | * |
| Target hardware | * |
| Other | * |
Notes
Imported from gcve-enriched-dumps CVE data
PURL mappings
| PURL | Source | Last updated |
|---|---|---|
| No PURL mappings for this CPE yet. | ||
Vulnerability references
| Identifier | cpeApplicability | Submitted | db.gcve.eu details | Rationale |
|---|---|---|---|---|
CVE:CVE-2026-112943 |
vulnerable | 2026-11-03 10:16:28.868085 |
launch-editor: escapeCmdArgs() omits % escaping on Windows
launch-editor allows users to open files with line numbers in editor from Node.js. Prior to 2.14.2, launch-editor did not escape % on Windows when passing an argument to cmd. When an environment variable contained a malicious value, it was possible that that content to be executed. This vulnerability is fixed in 2.14.2.
Published: 2026-10-20T14:53:41.777Z
Updated: 2026-10-20T15:13:40.862Z |
Imported from gcve-enriched-dumps CVE data |
CVE:CVE-2026-112942 |
vulnerable | 2026-11-03 10:16:28.792292 |
launch-editor: `fs.existsSync()` existence check can be bypassed on Windows
launch-editor allows users to open files with line numbers in editor from Node.js. Prior to 2.14.2, launch-editor-middleware processes an attacker-controlled Windows file argument where the file argument ends in a parent-directory component plus a line-and-column suffix: the path is resolved while the suffix is still present, and launch-editor removes the suffix before its existsSync check, leaving the existing parent directory for existsSync and allowing the attacker-controlled file argument to pass filename existence validation without requiring the malicious filename to exist. The bypass can lead to OS command injection when combined with the separately described Windows percent-expansion flaw. This issue is fixed in version 2.14.2.
Published: 2026-10-20T14:48:06.676Z
Updated: 2026-10-21T15:55:05.963Z |
Imported from gcve-enriched-dumps CVE data |
CVE:CVE-2026-112944 |
vulnerable | 2026-11-03 10:16:28.430427 |
launch-editor: Editor CLI flag misinterpretation causing arbitrary command execution for some editors
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.
Published: 2026-10-20T14:57:38.728Z
Updated: 2026-10-20T15:23:12.248Z |
Imported from gcve-enriched-dumps CVE data |
CVE:CVE-2026-53632 |
vulnerable | 2026-07-29 01:00:27.119623 |
NTLMv2 hash disclosure via UNC path handling on Windows
launch-editor allows users to open files with line numbers in editor from Node.js. Prior to 2.14.1, 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. This vulnerability is fixed in 2.14.1.
Published: 2026-06-22T15:54:09.240Z
Updated: 2026-06-22T17:30:11.939Z |
Imported from gcve-enriched-dumps CVE data |
CVE:CVE-2024-52011 |
vulnerable | 2026-06-08 06:52:14.578167 |
launch-editor vulnerable to command injection via the crafted request on Windows
launch-editor allows users to open files with line numbers in editor from Node.js. Prior to version 2.9.0, 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. This issue has been fixed in the `launch-editor` version 2.9.0, corresponding to vite version 5.4.9.
Published: 2026-06-01T17:17:43.792Z
Updated: 2026-09-04T12:04:46.222Z |
Imported from gcve-enriched-dumps CVE data |
Contribute
You can submit an edit proposal for this CPE entry or suggest a related product/vendor addition using the action button above.
Inspect record JSON
Open this panel to browse, search, copy or download the JSON record.