CVE-2026-112942: launch-editor: `fs.existsSync()` existence check can be bypassed on Windows
Summary launch-editor checked fs.existsSync(fileName) before passing a supplied path to an editor command. On Windows, an attacker can bypass this check with a crafted path ending in \\..:line:column. This removes the requirement that the attacker be able to place a file with a malicious filename.
Published Oct 20, 2026
Affected packages
launch-editor
- Ecosystem
- npm
- Affected
- <= 2.14.1
- Fixed in
- 2.14.2
- Check
npm ls launch-editor
vite
- Ecosystem
- npm
- Affected
- >= 8.3.0, <= 8.3.2
- Fixed in
- 8.3.3
- Check
npm ls vite
vite
- Ecosystem
- npm
- Affected
- >= 8.2.0, <= 8.2.3
- Fixed in
- 8.2.4
- Check
npm ls vite
vite
- Ecosystem
- npm
- Affected
- >= 8.0.0, <= 8.1.5
- Fixed in
- 8.1.6
- Check
npm ls vite
vite
- Ecosystem
- npm
- Affected
- >= 7.0.0, <= 7.3.6
- Fixed in
- 7.3.7
- Check
npm ls vite
vite
- Ecosystem
- npm
- Affected
- <= 6.4.3
- Fixed in
- 6.4.4
- Check
npm ls vite
vite-plus
- Ecosystem
- npm
- Affected
- <= 1.0.0
- Fixed in
- 1.1.0
- Check
npm ls vite-plus
Advisory details
From the GitHub Advisory Database (CC BY 4.0).
Summary
launch-editor checked fs.existsSync(fileName) before passing a supplied path to an editor command. On Windows, an attacker can bypass this check with a crafted path ending in \\..:line:column. This removes the requirement that the attacker be able to place a file with a malicious filename.
Combined with the % escaping issue described in GHSA-698v-4r3x-3vcv, this bypass can lead to OS command injection when an attacker controls the file argument.
Impact
Only apps that runs on Windows is affected.
Details
The earlier advisory assumed that fs.existsSync() required an attacker-controlled filename to exist. This advisory covers a bypass of that requirement.
A crafted value ending in \\..:1:1 is interpreted differently by launch-editor-middleware, launch-editor, and Windows:
launch-editor-middlewarecallspath.resolve()while the final path component is..:1:1, so it is not treated as a parent-directory component.launch-editortreats:1:1as a line-and-column suffix and removes it, leaving a path ending in\\...- On Windows,
fs.existsSync()accepts the resulting path as the existing parent directory even though the attacker-controlled preceding component does not exist. - Because the existence check passes, the crafted filename reaches the Windows shell command.
Credited to hutsbotnet, bluwy.
References
- https://github.com/vitejs/launch-editor/security/advisories/GHSA-587h-7wmj-h5pm
- https://nvd.nist.gov/vuln/detail/CVE-2026-112942
- https://github.com/vitejs/launch-editor/commit/f13cd835d4b8e860b1d4d080ad8a490cc2463679
- https://github.com/vitejs/launch-editor/releases/tag/v2.14.2
- https://github.com/advisories/GHSA-587h-7wmj-h5pm
How this page is made: the data panel comes from the GitHub Advisory Database, CISA’s KEV catalog, the NVD and FIRST EPSS, and updates twice a day. No analysis has been written for this entry yet. Methodology
More npm vulnerabilities
All npm entriesCVE-2026-118662
Vite: `server.fs.deny` bypassed with queries
medium6.9Oct 29, 2026CVE-2026-112945
Vite: Cross origin script execution through Vite custom middleware
low2.1Oct 21, 2026CVE-2026-112946
Vite: Files outside `server.fs.allow` could be served when project paths match system paths on non-Windows machine
medium6.3Oct 21, 2026CVE-2026-112947
Vite: First 4 bytes of files outside of `server.fs` setting is exposed by `?vite-wasm-instance`
medium6.3Oct 21, 2026CVE-2026-112948
Vitest: Servers misapply `server.fs.deny`, serving `.env`, private keys, `.git`, and the API token file
medium6.5Oct 21, 2026CVE-2026-112943
launch-editor: escapeCmdArgs() omits % escaping on Windows
medium6.3Oct 20, 2026
