CVE-2024-52011: launch-editor vulnerable to command injection via the crafted request on Windows
launch-editor allows users to open files with line numbers in editor from Node.js. Prior to version 2.9.0, due to the insufficient sanitization of the `file` argument in the `launchEditor`, an attacker can execute arbitrary commands on Windows by supplying a filename that contains special characters. This issue has been fixed in the `launch-editor` version 2.9.0, corresponding to vite version 5.4.9.
Security readout for executives and security teams
Plain-English summary
This flaw lets a crafted filename reach Windows command execution through affected launch-editor tooling. It matters most where Vite or launch-editor is reachable with attacker-controlled requests. The issue is rated high, but the source bundle does not show known active exploitation or CISA KEV listing.
Executive priority
Treat as a high-priority developer tooling update for Windows environments. Prioritize exposed development servers, shared workstations, and build systems first. Internet-facing or broadly reachable Vite tooling should be addressed urgently.
Technical view
launch-editor before 2.9.0 insufficiently sanitized the file argument passed to launchEditor. On Windows, special characters in the filename could lead to arbitrary command execution. The CVE maps to CWE-77 and CWE-88, CVSS 8.3, and is fixed in launch-editor 2.9.0 and Vite 5.4.9.
Likely exposure
Windows systems using launch-editor below 2.9.0 or Vite below 5.4.9 are the relevant exposure. Risk is highest where requests or filenames can be influenced by untrusted users. Non-Windows impact is not established in the supplied sources.
Exploitation context
The CVSS vector indicates network attackability, low complexity, no privileges, and required user interaction. The bundle says exploitation uses a crafted request and malicious filename characters on Windows. KEV is false, and no supplied source confirms active exploitation.
Researcher notes
The strongest evidence is the GitHub advisory, fix commit, CVE record, and Red Hat entries. The supplied data supports command injection on Windows through file argument sanitization failure, but does not prove exploitation in the wild or broader platform impact.
Mitigation direction
Upgrade launch-editor to 2.9.0 or later.
Upgrade Vite to 5.4.9 or later where bundled dependency applies.
Review dependency lockfiles for transitive launch-editor copies.
Do not expose affected dev tooling to untrusted networks.
Check Red Hat advisory RHSA-2026:34342 if using Red Hat packages.
Validation and detection
Search manifests and lockfiles for launch-editor versions below 2.9.0.
Search manifests and lockfiles for Vite versions below 5.4.9.
Identify Windows hosts running affected Node.js developer tooling.
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
Potential ATT&CK relevance
Conservative CVE-to-ATT&CK context
These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.
ATT&CK lookup starting points
Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.
cwe · medium confidence lookup
CWE-77: Command execution behavior lookup
Command injection weaknesses can lead defenders to review execution techniques and command interpreter telemetry. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.
Command injection weaknesses can lead defenders to review execution techniques and command interpreter telemetry. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.
The CVE wording references code or command execution, so execution technique review may help defensive triage. This is a Glexia inferred lookup path, not an official MITRE, ATT&CK, or CVE Program mapping.
These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.
2CVSS vectors
5Timeline events
2ADP providers
7Source links
SSVC decision data
CISA-ADPCISA Coordinator
Timestamp
Version
2.0.3
Exploitation: noneAutomatable: yesTechnical Impact: total
CVSS vector scores
2 official scores
We collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.
CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.
CWE-77 · source CWE mapping
Improper Neutralization of Special Elements used in a Command ('Command Injection')
Improper Neutralization of Special Elements used in a Command ('Command Injection') represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.
Improper Neutralization of Argument Delimiters in a Command ('Argument Injection')
Improper Neutralization of Argument Delimiters in a Command ('Argument Injection') represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.