launch-editor
Affected
- introduced
0, fixed2.14.2(semver)
Fixed versions
2.14.2
Fix
- Fixed version
2.14.2npm install [email protected]
Advisory
Also known as: CVE-2026-112943
launch-editor: escapeCmdArgs() omits % escaping on Windows
Summary
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.
Impact
Only apps that match all of the following conditions are affected:
& or %Details
Unlike .sh files, .bat / .cmd files on Windows cannot be called directly using `child_process.spawn` and requires passing them as an argument of cmd.exe. To do so, launch-editor escapes the arguments passed to cmd.exe. But launch-editor did not escape % which is used for environment variables.
Because launch-editor checks if the argument matches an existing filename, the attack requires the attacker to be able to place a file.
&calc.exe to %ENV%) and call launchEditor with something%ENV%.~-38%calc.exe), they can call launchEditor with something %CMDCMDLINE:~-38%calc.exe.%CD% and the subcommand (e.g. &calc.exe ), they can call launchEditor with ./%CD%Medium Basis: The source's own band: MODERATE
0, fixed 2.14.2 (semver)2.14.2
2.14.2npm install [email protected]8.3.0, fixed 8.3.3 (semver)8.3.3
8.3.3npm install [email protected]8.2.0, fixed 8.2.4 (semver)8.2.4
8.2.4npm install [email protected]8.0.0, fixed 8.1.6 (semver)8.1.6
8.1.6npm install [email protected]7.0.0, fixed 7.3.7 (semver)7.3.7
7.3.7npm install [email protected]0, fixed 6.4.4 (semver)6.4.4
6.4.4npm install [email protected]0, fixed 1.1.0 (semver)1.1.0
1.1.0npm install [email protected]Fix commands are the export's own generic commands. Ojuju never runs them. Check them against your setup first.
Check your own computer: guard packages check
Source: GitHub Advisory Database (reviewed advisories) · CC BY 4.0