Skip to content
Fencer Intel
high 7.5

CVE-2026-112942 json

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

published 20d ago modified 19d ago also EUVD-2026-105035 , GHSA-587h-7wmj-h5pm

cvss
7.5
version 4.0, CNA
cisa kev
Not listed
not in CISA's catalog
epss
1.3%
EPSS 1.3% chance of exploitation in 30 days, percentile 71%
public exploits
0
none known

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.

Patch / fix

  • npm launch-editor 2.14.2
  • npm vite 6.4.4, 7.3.7, 8.1.6, 8.2.4, 8.3.3
  • npm vite-plus 1.1.0
  • vitejs launch-editor 2.14.2
  • vitejs vite 1.1.0, 2.14.2, 6.4.4, 7.3.7, 8.1.6, 8.2.4, 8.3.3

Is CVE-2026-112942 in your dependencies? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.

Check with Fencer

Vendor advisories

What the vendors themselves say about their products: affected, fixed or not affected, and what to do.

red hat product security vex CVE-2026-112942 updated cvss 8.8

launch-editor: launch-editor: Command injection via improper file path validation

  • Red Hat Hardened Images grafana13.1 13.1.7-0.2.hum1, grafana13.2 13.2.3-0.3.hum1, prometheus3.13 3.13.4-0.1.hum1
    not affected: component not present

Red Hat CSAF VEX © Red Hat, Inc., from https://security.access.redhat.com/data/csaf/v2/vex/; changed: reduced to product statuses and remediations. CC BY 4.0 · csaf

CISA SSVC

Exploitation
none
Automatable
no
Technical impact
total
Assessed
19d ago

Exploit prediction

1.34% chance of exploitation in the next 30 days, higher than 71% of all scored CVEs (FIRST EPSS, 2026-11-09).

CVSS scores

assigned by version score vector
CNA 4.0 7.5 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
CNA 4.0 7.5 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/E:X/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:X

Affected packages

ecosystem package affected fixed in
npm launch-editor
<2.14.2
2.14.2
npm vite
>=8.3.0, <8.3.3
>=8.2.0, <8.2.4
>=8.0.0, <8.1.6
>=7.0.0, <7.3.7
<6.4.4
8.3.3
8.2.4
8.1.6
7.3.7
6.4.4
npm vite-plus
<1.1.0
1.1.0

Affected products

  • vitejs launch-editor
  • vitejs vite
  • vitejs vite-plus

Classification

Weakness
  • CWE-77 Improper Neutralization of Special Elements used in a Command

References

Sources

Fencer Intel keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.

CPEs and fixed versions use Anchore's correction of NVD's data: Added CPE configurations because not yet analyzed by NVD.