llamaCVEVulnerability Intelligence
/
Advisory · GitHub · npm · launch-editor

GHSA-R825-W8MM-5PXW

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

Parche disponible
Descargar PNG JSON
CVSS
—
medium
Fuente: —
ExplotaciónSin evidenciaNo figura en CISA KEV
Exploits públicos0Ninguno conocido
Parche7 versionesPrimer parche a -14 d de la divulgación
Exposición29 dDesde la divulgación, 20 oct 2026, 2:51 p. m.
Detección27 dDesde la divulgación hasta su ingreso al índice
Timeline

Ciclo de vida de la vulnerabilidad

Hoy
Divulgación
Publicada +1
Explotación
Remediación
Parche 2.14.2 +5
Parche 1.1.0
Monitoreo
Detectada
6 oct 26
7 oct 26
20 oct 26
17 nov 26
19 nov 26
6 oct 26
17 oct 26
28 oct 26
8 nov 26
19 nov 26
FechaFaseEventoDetalle
Remediación Parche 2.14.2 launch-editor · -14 d desde divulgación
Remediación Parche 6.4.4 vite · -14 d desde divulgación
Remediación Parche 7.3.7 vite · -14 d desde divulgación
Remediación Parche 8.1.6 vite · -14 d desde divulgación
Remediación Parche 8.2.4 vite · -14 d desde divulgación
Remediación Parche 8.3.3 vite · -14 d desde divulgación
Remediación Parche 1.1.0 vite-plus · -13 d desde divulgación
Divulgación Publicada GHSA-R825-W8MM-5PXW divulgada
Divulgación Modificada Última actualización del registro
Monitoreo Detectada Ingresó al índice
Resumen
Descripción del advisory
Texto original · GitHub · en inglés
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.

Versiones

Rangos afectados

Afectada Corregida Última
vite-plus< 1.1.0
launch-editor< 2.14.2
vite< 6.4.4
vite≥ 7.0.0 < 7.3.7
vite≥ 8.0.0 < 8.1.6
vite≥ 8.2.0 < 8.2.4
vite≥ 8.3.0 < 8.3.3
1.1.0
2.14.2
6.4.4
7.0.0
7.3.7
8.0.0
8.1.6
8.2.0
8.2.4
8.3.0
8.3.3
8.3.8
Remediación

Estado del parche por paquete

Paquete / productoEstadoCorregida enDesde divulgaciónÚltima versión
npmlaunch-editor
Corregida 2.14.2 -14 d 2.14.2 no afectada
npmvite
Corregida 6.4.4, 7.3.7, 8.1.6, 8.2.4, 8.3.3 -14 d · -14 d · -14 d · -14 d · -14 d 8.3.8 no afectada
npmvite-plus
Corregida 1.1.0 -13 d 1.6.0 no afectada
Versiones corregidas1.1.02.14.26.4.47.3.78.1.68.2.48.3.3
Explotación

Arsenal público

Sin exploits, módulos ni PoC públicos conocidos a la fecha de verificación.

Referencias
Advisoryhttps://nvd.nist.gov/vuln/detail/CVE-2026-112944
Otrahttps://github.com/vitejs/launch-editor/security/advisories/GHSA-r825-w8mm-5pxw
Otrahttps://github.com/vitejs/launch-editor/pull/156
Otrahttps://github.com/vitejs/launch-editor/commit/f6e6701bb1f16f2dd242b321374f1b6cca6eb6d4
Otrahttps://github.com/vitejs/launch-editor
Otrahttps://github.com/vitejs/launch-editor/releases/tag/v2.14.2

Las referencias externas se muestran para copiar: cve.llama.ec no lo redirige a otros sitios.