CVSS 4.0
6.3 mediumCVSS:4.0/AV:N/AC:L/AT:P/PR:N/UI:N/VC:L/VI:L/VA:L/SC:N/SI:N/SA:NMedium (6.3) in vitejs. EPSS 0.4% 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:N/VC:L/VI:L/VA:L/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-112943 for an engineer deciding whether to act. Use https://cve.bz/api/public/cves/CVE-2026-112943?via=ask-ai-copy and https://cve.bz/cve/CVE-2026-112943?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-112943 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-698v-4r3x-3vcv | npm | launch-editor | <2.14.2 | 2.14.2 |
| GHSA-698v-4r3x-3vcv | npm | vite | >=8.3.0 <8.3.3 | 8.3.3 |
| GHSA-698v-4r3x-3vcv | npm | vite | >=8.2.0 <8.2.4 | 8.2.4 |
| GHSA-698v-4r3x-3vcv | npm | vite | >=8.0.0 <8.1.6 | 8.1.6 |
| GHSA-698v-4r3x-3vcv | npm | vite | >=7.0.0 <7.3.7 | 7.3.7 |
| GHSA-698v-4r3x-3vcv | npm | vite | <6.4.4 | 6.4.4 |
| GHSA-698v-4r3x-3vcv | npm | vite-plus | <1.1.0 | 1.1.0 |
Red Hat rates this Important.
Red Hat has evaluated this vulnerability as having an Important security impact because successful exploitation could allow an attacker to achieve arbitrary command execution within the application context. The defect specifically arises from argument handling when delegating execution to the Windows command shell. Because standard Red Hat environments and containerized distributions operate on Linux systems, typical deployments do not rely on Windows command interpreters and are not directly exposed to this attack vector.
--- 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 editors on Windows or enforce strict argument allowlists to avoid passing unescaped arguments directly to cmd.exe: upgrade to launch-editor 2.14.2 (or the fixed Grafana/Prometheus builds), which reject arguments containing percent signs, carriage returns, or line feeds by throwing an error instead of passing them to cmd.exe, closing all 4 injection vectors (environment-variable expansion, NTFS alternate data streams, crafted filenames, crafted relative path referencing %CD%). Until patched, this is only a concern on Windows systems running applications that pass user-controlled file paths or arguments to launch-editor — Linux and macOS deployments are unaffected — so restrict and audit who can set environment variables, prohibit placing files containing percent characters, ampersands, or line breaks in working directories, and validate file paths before invoking launch-editor. As a compensating measure, strip carriage returns and line feeds to block command separation and multiline command injection payloads passed into the Windows command shell, deploy Windows Defender Application Control in enforced mode to block unauthorized binaries an injected subcommand might drop, and restrict path characters using allowlist validation to prevent percent signs and line breaks from reaching launch-editor. These controls limit blast radius and contain exploitation, but they do not fix the underlying improper argument escaping defect — apply the upstream patch to fully remediate.
Highest-impact CME: CME-1307 Command Injection Prevention (No Shell Invocation) (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-112943.
The attack patterns MITRE's CAPEC relates to this record's weaknesses, as MITRE names them. Credits.