Skip to main content
← All vulnerabilities
CVE-2026-112942GHSA-587H-7WMJ-H5PM

launch-editor: `fs.existsSync()` existence check can be bypassed on Windows

Published
Last modified
published
Not listed in CISA KEV
Fix
Fixed in 2.14.2, 8.3.3, 8.2.4, 8.1.6, 7.3.7, and 2 more
None on Exploit-DB, Metasploit or GitHub
  • Exploitation: none
  • Automatable: no
  • Technical impact: total

Summary

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.

Timeline

  1. CVE published
  2. CISA SSVC assessment

    Exploitation: none · Automatable: no · Technical impact: total

  3. Record last updated
  4. First seen by cve.now

Affected versions

  • 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-editornpm

    fixed in 2.14.2

  • vitenpm

    From 8.3.0 · fixed in 8.3.3

  • vitenpm

    From 8.2.0 · fixed in 8.2.4

  • vitenpm

    From 8.0.0 · fixed in 8.1.6

  • vitenpm

    From 7.0.0 · fixed in 7.3.7

  • vitenpm

    fixed in 6.4.4

  • vite-plusnpm

    fixed in 1.1.0

References 3

GitHub · vitejs/launch-editor