CVSS 4.0
7.5 highCVSS:4.0/AV:N/AC:L/AT:P/PR:N/UI:A/VC:H/VI:H/VA:H/SC:N/SI:N/SA:NHigh (7.5) in vitejs. EPSS 1.7% estimated probability of exploitation activity in the next 30 days. Fixed in launch-editor 2.14.2.
CVSS:4.0/AV:N/AC:L/AT:P/PR:N/UI:A/VC:H/VI:H/VA:H/SC:N/SI:N/SA:Nlaunch-editor (npm): fixed in 2.14.2vite (npm): fixed in 8.3.3, 8.2.4, 8.1.6, 7.3.7, 6.4.4vite-plus (npm): fixed in 1.1.0Explain CVE-2026-112942 for an engineer deciding whether to act. Use https://cve.bz/api/public/cves/CVE-2026-112942?via=ask-ai-copy and https://cve.bz/cve/CVE-2026-112942?via=ask-ai-copy as the source of truth: what is affected and which versions fix it, whether it is in CISA KEV, public exploits, and its EPSS (an internet-wide 30-day estimate of exploitation activity, not a forecast for my systems). If they give no fixed versions, use the CVE record https://cveawg.mitre.org/api/cve/CVE-2026-112942 or the vendor advisory, not third-party mirrors. Tell me how to check whether I am affected and how to verify a fix. Cite the sources and say where they are uncertain.Opens a third-party assistant; its answer is its own, not cve.bz's. The prompt holds only this CVE's id and public links.
From the CNA's record in the CVE List.
| Product | Affected |
|---|---|
| vitejs launch-editor | < 2.14.2 |
| vitejs vite | >= 8.3.0, < 8.3.3 |
| vitejs vite | >= 8.2.0, < 8.2.4 |
| vitejs vite | >= 8.0.0, < 8.1.6 |
| vitejs vite | >= 7.0.0, < 7.3.7 |
| vitejs vite | < 6.4.4 |
| vitejs vite-plus | < 1.1.0 |
| Advisory | Ecosystem | Package | Affected | Fixed in |
|---|---|---|---|---|
| GHSA-587h-7wmj-h5pm | npm | launch-editor | <2.14.2 | 2.14.2 |
| GHSA-587h-7wmj-h5pm | npm | vite | >=8.3.0 <8.3.3 | 8.3.3 |
| GHSA-587h-7wmj-h5pm | npm | vite | >=8.2.0 <8.2.4 | 8.2.4 |
| GHSA-587h-7wmj-h5pm | npm | vite | >=8.0.0 <8.1.6 | 8.1.6 |
| GHSA-587h-7wmj-h5pm | npm | vite | >=7.0.0 <7.3.7 | 7.3.7 |
| GHSA-587h-7wmj-h5pm | npm | vite | <6.4.4 | 6.4.4 |
| GHSA-587h-7wmj-h5pm | npm | vite-plus | <1.1.0 | 1.1.0 |
Red Hat rates this Important.
Red Hat has evaluated this vulnerability as having an Important impact due to the severe potential blast radius of arbitrary command execution if an untrusted file path is evaluated by the service. However, this attack vector relies on Windows-specific path resolution and shell argument expansion behaviors to bypass file existence checks. Because Red Hat enterprise platforms and container images operate on Linux environments, the platform-specific mechanisms required to achieve exploitation are not present in standard deployments.
--- CME Mitigation Guidance (2026-10-20) ---
Disclaimer: The following mitigation solutions are provided as a courtesy, pending the application of an official patch. This content was generated utilizing AI tools in conjunction with data from https://cmetaxonomy.org. Customers are advised to independently evaluate and test these temporary mitigations within their own infrastructure.
The highest-value action is to eliminate shell invocation when launching editor processes on Windows hosts to prevent percent-variable expansion: upgrade to launch-editor 2.14.2 (or the fixed Grafana/Prometheus builds), which resolve file paths with path.resolve() immediately after stripping line and column position suffixes and check UNC paths on the resolved file name, closing all 3 injection vectors (crafted file path with position suffixes, parent-directory traversal bypass, Windows percent-variable expansion). Until patched, this is only a concern on Windows hosts running launch-editor or launch-editor-middleware endpoints — non-Windows platforms are unaffected — so restrict network access to endpoints exposing launch-editor-middleware and audit file path inputs to block parent-directory sequences and percent characters. As a compensating measure, enforce strict allowlist validation to restrict path characters and reject unexpected percent signs and coordinate suffix formats, deploy a web application firewall to detect and block incoming HTTP requests with traversal patterns or command injection characters, deploy Windows Defender Application Control in enforced mode to block unauthorized binaries an injected subcommand might drop, and configure endpoint detection and response agents to monitor and alert on anomalous child process creation spawned from Node.js. These controls limit blast radius and contain exploitation, but they do not fix the underlying improper path validation defect — apply the upstream patch to fully remediate.
Highest-impact CME: CME-1301 Path Traversal Prevention (Canonicalization) (high)
| Product | Package | State | Advisory |
|---|---|---|---|
| Red Hat Hardened Images | grafana13.1 | Not affected | |
| Red Hat Hardened Images | grafana13.2 | Not affected | |
| Red Hat Hardened Images | prometheus3.13 | Not affected |
Contains Red Hat Security Data © Red Hat, Inc., licensed under CC BY 4.0. Source: https://access.redhat.com/security/data. Modified: reformatted. Red Hat's page for CVE-2026-112942.
The attack patterns MITRE's CAPEC relates to this record's weaknesses, as MITRE names them. Credits.