CVE-2024-52011: launch-editor vulnerable to command injection via the crafted request on Windows

Published Jun 1, 2026
·
Updated

Summary 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.

Impact If the following conditions are met, an attacker can execute arbitrary commands on the computer that is using the launch-editor:

- An attacker can place a file with the malicious filename - An attacker can call the launchEditor method with the file argument controlled - The launch-editor package is running on Windows

For example, some development server using this package satisfy these conditions, as a malicious website might be able to force the downloading of a file and the path of that file is predictable.

Patch This issue has been fixed in the launch-editor version 2.9.0 (commit).

Other sources

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.

— NVD

Affected Software

4 affected componentsFixes available
npm/launch-editor<2.9.0
npm/vite<5.4.9
npm/vite<=5.4.8
5.4.9
npm/launch-editor<=2.8.2
2.9.0

Remediation

Recommended actions to resolve this vulnerability, in priority order.

  1. Upgrade

    Upgrade npm/vite to a version that resolves this vulnerability.

    Fixed in 5.4.9
  2. Upgrade

    Upgrade npm/launch-editor to a version that resolves this vulnerability.

    Fixed in 2.9.0
  3. Upgrade

    Upgrade launch-editor to a version that resolves this vulnerability.

    Fixed in 2.9.0
  4. Upgrade

    Upgrade to a fixed release to a version that resolves this vulnerability.

    Patch vite version 5.4.9

Event History

Jun 1, 2026
CVE Published
via MITRE·05:17 PM
Data Sourced
via MITRE·05:17 PM
DescriptionWeakness
Data Sourced
via NVD·07:16 PM
DescriptionSeverityWeakness
Data Sourced
via Red Hat·10:20 PM
DescriptionSeverityAffected Software
Jun 3, 2026
Advisory Published
via GitHub·06:02 PM
Data Sourced
via GitHub·06:02 PM
DescriptionWeaknessAffected Software

Frequently Asked Questions

1

What is the severity of CVE-2024-52011?

CVE-2024-52011 has a high severity rating of 7.5, indicating a serious vulnerability.

2

How do I fix CVE-2024-52011?

To address CVE-2024-52011, ensure that the `launchEditor` function properly sanitizes the `file` argument to prevent command injection.

3

What type of vulnerability is CVE-2024-52011?

CVE-2024-52011 is classified as a command injection vulnerability.

4

What risks are associated with CVE-2024-52011?

The primary risk of CVE-2024-52011 is that it allows an attacker to execute arbitrary commands on Windows systems.

5

Which software is affected by CVE-2024-52011?

CVE-2024-52011 affects the npm packages `launch-editor` and `vite`.

Contact

SecAlerts Pty Ltd.
132 Wickham Terrace
Fortitude Valley,
QLD 4006, Australia
info@secalerts.co
By using SecAlerts services, you agree to our services end-user license agreement. This website is safeguarded by reCAPTCHA and governed by the Google Privacy Policy and Terms of Service. All names, logos, and brands of products are owned by their respective owners, and any usage of these names, logos, and brands for identification purposes only does not imply endorsement. If you possess any content that requires removal, please get in touch with us.
© 2026 SecAlerts Pty Ltd.
ABN: 70 645 966 203, ACN: 645 966 203