All reports
Medium

launch-editor: Editor CLI flag misinterpretation causing arbitrary command execution for some editors

Affected versions

Affected versions
<= 2.14.1
Fixed version
2.14.2
Affected versions
<= 1.0.0
Fixed version
1.1.0
Affected versions
>= 8.3.0, <= 8.3.2
Fixed version
8.3.3
Affected versions
>= 8.2.0, <= 8.2.3
Fixed version
8.2.4
Affected versions
>= 7.0.0, <= 7.3.6
Fixed version
7.3.7
Affected versions
>= 8.0.0, <= 8.1.5
Fixed version
8.1.6
Affected versions
<= 6.4.3
Fixed version
6.4.4

Exploitation

CVE-2026-112944

Probability of exploitation in the next 30 days: 0.71%

FIRST EPSS · 2026-11-19

Description

Summary

launch-editor forwarded file paths directly to editors without sanitization. If a path resembles a CLI flag, editors like Vim may interpret it as a command, potentially causing unintended file overwrites or command execution.

Impact
Direct launch-editor users

Only apps that match all of the following conditions are affected:

  • The attacker is able to create a file system entry (e.g. a file or directory) starting with + or - in the working directory

  • The user uses or the app specifies any of the following editors:

    • Vim (including gVim)

    • MacVim

    • Emacs (including Emacsclient)

    • Notepad++ (only if using a plugin exposing dangerous operations via plugin messages)

  • The first argument of launchEditor can start with + or - or the user is using WSL

launch-editor-middleware users

Only apps that match the following conditions are affected:

  • The attacker is able to create a file system entry (e.g. a file or directory) starting with + or - in the working directory

  • The user uses or the app specifies any of the following editors:

    • Vim (including gVim)

    • MacVim

    • Emacs (including Emacsclient)

    • Notepad++ (only if using a plugin exposing dangerous operations via plugin messages)

  • launch-editor older than v2.2.0 is used, or the user is using WSL

Vite users

Only apps that match the following conditions are affected:

  • The attacker is able to create a file system entry (e.g. a file or directory) starting with + or - in the working directory

  • The user uses or the app specifies any of the following editors:

    • Vim (including gVim)

    • MacVim

    • Emacs (including Emacsclient)

    • Notepad++ (only if using a plugin exposing dangerous operations via plugin messages)

  • The user is using WSL

Details

launchEditor(file) function passes the file name as-is to the editor if the file with that file name exists. If the file name starts with - (also + for Vim), the editor treats them as flags rather than positional arguments. For example, Vim treats arguments starting with + as an Ex command. As a result, an existing relative directory such as:

+call writefile(["SAFE_MARKER"],"LAUNCH_EDITOR_MARKER")|qa!

is not treated as a filename when passed to Vim. Vim executes the embedded Ex command.

The following editor has a potentially destructive operation exposed to the CLI arguments:

  • Vim (including gVim)

  • MacVim

  • Emacs (including Emacsclient)

  • Notepad++ (only if using a plugin exposing dangerous operations via plugin messages)

launch-editor-middleware v2.2.0+ converts the passed file path to an absolute path so those are not affected as long as the user is not using WSL. For WSL, launch-editor converts the paths to relative paths internally, so those are still affected.

Vite 2.0.0+ uses launch-editor-middleware v2.2.0+ so the WSL users are only affected.

Links

Credits

  • 0xazanul
  • bluwy