Skip to main content
Vulnerability Database/CVE-2026-112944

CVE-2026-112944: launch-editor Node.js RCE Vulnerability

CVE-2026-112944 is a command injection flaw in launch-editor that enables arbitrary code execution through malicious filesystem entries. This post explains the technical details, affected editors, and mitigation steps.

Published:

Disclaimer: This content was generated using AI. While we strive for accuracy, please verify critical information with official sources.

Sources: National Vulnerability Database, CISA KEV, Exploit-DB

CVE-2026-112944 Overview

CVE-2026-112944 is an argument injection vulnerability [CWE-88] in the launch-editor package maintained by the Vite project. The flaw affects versions prior to 2.14.2 and occurs when launchEditor forwards attacker-controlled filenames to downstream editors without marking them as positional arguments. When a filesystem entry begins with a plus or minus character, editors such as Vim, gVim, MacVim, Emacs, Emacsclient, and Notepad++ (with certain plugins) parse the filename as a command-line flag. The downstream impact can include unintended file overwrites or arbitrary command execution within the editor process.

Critical Impact

An attacker who can plant a file whose name starts with + or - in the working directory can trigger editor flag parsing, leading to file overwrite or command execution on the developer workstation.

Affected Products

  • launch-editor versions prior to 2.14.2
  • Vite and newer middleware callers that invoke launchEditor with WSL path conversion
  • Downstream editors: Vim, gVim, MacVim, Emacs, Emacsclient, and Notepad++ with plugins exposing dangerous operations

Discovery Timeline

  • 2026-10-20 - CVE-2026-112944 published to the National Vulnerability Database
  • 2026-10-20 - Last updated in NVD database

Technical Details for CVE-2026-112944

Vulnerability Analysis

The launch-editor package provides a Node.js utility that opens files in a developer's configured editor, often triggered by framework overlays such as the Vite error overlay. When the user clicks a stack frame, the server resolves the source path and invokes the editor via child_process with the filename and optional line and column numbers.

The vulnerability stems from how getArgumentsForFile constructs the argument list. The filename is appended to the command without a -- separator and without normalization to an absolute path. Many Unix editors treat tokens starting with - or + as options. For Vim, +{command} executes the supplied Ex command on startup, which can be abused to run shell commands via :! or to overwrite files via :w.

The advisory specifically calls out Vite and newer middleware callers that rely on Windows Subsystem for Linux (WSL) path conversion. Even when the caller supplies an absolute path, the WSL conversion step keeps the resulting path relative, exposing it to the same argument-parsing confusion.

Root Cause

The root cause is unsafe argument construction [CWE-88: Argument Injection]. The fileName parameter was passed directly to the editor binary without resolution to an absolute path and without using the POSIX -- end-of-options sentinel. Any filesystem entry starting with + or - was interpreted as a flag by the invoked editor.

Attack Vector

Exploitation requires an attacker to create a file whose name begins with + or - inside the project's working directory. This is plausible via dependency installation hooks, git repositories with crafted filenames, archive extraction, or any workflow that materializes untrusted content into a developer's project tree. When the developer later clicks an error overlay link or invokes launchEditor on the malicious file, the attacker-chosen flag is executed by the editor.

javascript
// Patch excerpt from packages/launch-editor/get-args.js
// normalize a file and optional line/column numbers into command line
// args for specific editors
module.exports = function getArgumentsForFile(editor, fileName, lineNumber, columnNumber = 1) {
+  fileName = path.resolve(fileName)
+
   if (
     process.platform === 'linux' &&
     fileName.startsWith('/mnt/') &&

Source: GitHub Commit f6e6701. The fix resolves the filename to an absolute path before any editor-specific handling, preventing a leading + or - from being interpreted as a command-line flag.

Stop Remote Code Execution Before It Runs

Singularity™ Endpoint detects and blocks exploit attempts at machine speed, including zero-days and novel attack techniques.

Stop Exploit Attempts

Detection Methods for CVE-2026-112944

Indicators of Compromise

  • Filesystem entries in project directories whose names begin with + or -, especially under source trees served by dev servers such as Vite
  • Unexpected child processes spawned by vim, gvim, mvim, emacs, emacsclient, or notepad++ originating from a Node.js parent process
  • Writes to unexpected files on disk coincident with developer use of error-overlay "open in editor" features

Detection Strategies

  • Perform software composition analysis across Node.js projects to flag any direct or transitive dependency on launch-editor below version 2.14.2
  • Audit package-lock.json and pnpm-lock.yaml for launch-editor resolutions, including those pulled in via vite and @vue/cli
  • Scan repositories and workspace directories for file names matching the regex ^[+-] and quarantine anomalies

Monitoring Recommendations

  • Monitor developer endpoints for editor processes launched with argument strings containing shell escapes such as +:! or +!
  • Alert on node or vite processes spawning editors with arguments that resolve to relative paths beginning with + or -
  • Log and review file-creation events in developer project directories where filenames start with disallowed prefixes

How to Mitigate CVE-2026-112944

Immediate Actions Required

  • Upgrade launch-editor to version 2.14.2 or later across all projects and build pipelines
  • Rebuild and redeploy any internal tools or dev-server middleware that bundle launch-editor as a transitive dependency
  • Review and remove any files in active working directories whose names begin with + or -

Patch Information

The fix is published in launch-editor v2.14.2 via Pull Request #156. Full technical context is available in GHSA-r825-w8mm-5pxw. The patch calls path.resolve(fileName) before downstream editor-specific handling.

Workarounds

  • Pin an unaffected editor configuration that does not interpret leading + or - as command flags until the upgrade is deployed
  • Restrict the dev server to trusted project directories and avoid opening untrusted repositories where filenames cannot be audited
  • Prevent creation of files whose names begin with + or - via pre-commit hooks or filesystem policies in CI runners
bash
# Upgrade launch-editor to the patched version
npm install launch-editor@^2.14.2

# Confirm no transitive copy remains below 2.14.2
npm ls launch-editor

# Audit the working tree for suspicious filenames
find . -type f \( -name '+*' -o -name '-*' \) -not -path './node_modules/*'

Disclaimer: This content was generated using AI. While we strive for accuracy, please verify critical information with official sources.

Sources: National Vulnerability Database, CISA KEV, Exploit-DB

Experience the Most Advanced Cybersecurity Platform

See how the world’s most intelligent, autonomous cybersecurity platform can protect your organization today and into the future.