What’s Vulnerable › Vulnerabilities
CVE-2026-112942: launch-editor: `fs.existsSync()` existence check can be bypassed on Windows
- Severity: high (CVSS 7.5 v4.0)
- Exploited in the wild: not listed in CISA KEV
- EPSS: 1.3% probability of exploitation in the next 30 days
- Public exploit or detection template: none known
- Published: 2026-10-20 · updated 2026-10-21
- Weakness: CWE-77
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.
Affected products
- Npm Launch-Editor: before 2.14.2 — fixed in 2.14.2
- Npm Vite: from 8.3.0 before 8.3.3; from 8.2.0 before 8.2.4; from 8.0.0 before 8.1.6; from 7.0.0 before 7.3.7; before 6.4.4 — fixed in 8.3.3, 8.2.4, 8.1.6, 7.3.7, 6.4.4
- Npm Vite-Plus: before 1.1.0 — fixed in 1.1.0
- vitejs launch-editor: before 2.14.2
- vitejs vite: from 8.3.0, < 8.3.3; from 8.2.0, < 8.2.4; from 8.0.0, < 8.1.6; from 7.0.0, < 7.3.7; before 6.4.4
- vitejs vite-plus: before 1.1.0
How to fix
Upgrade to a fixed version: Npm Launch-Editor 2.14.2; Npm Vite 8.3.3, 8.2.4, 8.1.6, 7.3.7; Npm Vite-Plus 1.1.0. Check the vendor advisory for mitigations.
References
- https://github.com/vitejs/launch-editor/commit/f13cd835d4b8e860b1d4d080ad8a490cc2463679
- https://github.com/vitejs/launch-editor/releases/tag/v2.14.2
- https://github.com/vitejs/launch-editor/security/advisories/GHSA-587h-7wmj-h5pm
Get alerted when CVE-2026-112942 or the next vulnerability affects your stack