CVE-2026-112942
7.5HighPublished 20 Oct 2026 · NVD status: Received · AI triage by gemini-3.8-flash
- Attack vector
- Network
- Complexity
- Low
- Privileges needed
- None
- User interaction
- Active
- Impact
- Full C/I/A compromise
- Weakness
- CWE-77
Impact
Remote attackers can execute arbitrary OS commands on Windows hosts running applications that expose launch-editor-middleware. Exploitation requires user interaction to process a crafted file path query.
Root cause
Improper path resolution order allows specially crafted file paths with line-and-column suffixes to bypass existence checks before being executed on Windows.
Affected systems
launch-editor and launch-editor-middleware versions prior to 2.14.2 on Windows
CVSS v4.0 · CVSS:4.0/AV:N/AC:L/AT:P/PR:N/UI:A/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N/E:X/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:X
Fix & remediation
Upgrade launch-editor to version 2.14.2 or later. If updating is not immediately possible, restrict or disable network access to endpoints hosting launch-editor-middleware.
$ npm install launch-editor@2.14.2AI-suggested. Run it in staging first and check it against the vendor advisory. Why?
NVD description
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.