CVE Tools

CVE-2026-112942

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

No known exploitation. EPSS puts it in the 71st percentile. No fix published yet.

Published Updated Sources: CVE.org, NVD

What to do

No fixed build or workaround is published yet. Limit exposure and watch for a patch.

  • Vitejs Launch-editorAffected: < 2.14.2Upgrade to: not statedStated by: CVE record
  • Vitejs ViteAffected: >= 8.3.0, < 8.3.3Upgrade to: not statedAffected: >= 8.2.0, < 8.2.4Upgrade to: not statedAffected: >= 8.0.0, < 8.1.6Upgrade to: not statedAffected: >= 7.0.0, < 7.3.7Upgrade to: not stated + 1 more branchStated by: CVE record
  • Vitejs Vite-plusAffected: < 1.1.0Upgrade to: not statedStated by: CVE record

Versions as the sources state them. Full version matrix after sign-in

What it is

From the CVE record

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.

In plain language

No plain-language summary for this CVE yet.

Exploitation

Where each signal puts this CVE on the scale from published to confirmed exploited.

EPSS71st
CISA KEV

Not in the catalog. CISA has not confirmed exploitation.

Public exploits

No public exploit or proof of concept found in the sources we track.

EPSS

1.3% chance of exploitation activity in the next 30 days, which ranks it in the 71st percentile of scored CVEs.

Exploit Prediction Scoring System, FIRST.org. A probability, not a confirmation.

Lifecycle

6 events over 1 day, from the signal feeds we watch.

  1. Record updated
  2. Publishedweakness classified, att&ck mapped, record updated, record updated

Affected products

Technical detail

Weaknesses

ATT&CK techniques

Mapped from the weaknesses above (CWE to ATT&CK), not observed in attacks.

Sources

Watch the software you run.

My Stack ranks new CVEs for your products by real-world exploitation, so the next serious one reaches you without reading every advisory.

We'll flag the next CVE, public exploit or patch for Launch-editor, not every advisory.