BlackTreeCVE Intelligence
← Back to the CVE catalogue
Full vulnerability report · 2026
CVE-2024-52011High confidence

launch-editor vulnerable to command injection via the crafted request on Windows

vitejs · launch-editor

Official source article: GitHub GHSA-C27G-Q93R-2CWF ↗. Check the applicable product and release in the original source.

7.5HighCVSS 4.0
Recommended action
Within 7 days

High technical severity; prioritise exposed affected systems while verifying vendor guidance.

Patch available
R
Operational reassessment

Published severity in operational context

Open reassessment dashboard →
Published severityHighOperational priority:High, unchanged from published severity.unchanged

Evidence used

  • No CISA KEV confirmation is currently recorded.
  • EPSS is 0.51% for the current model date.

Compensating controls

  • Validate the affected product branch and deploy the verified fixed release.
  • Restrict the affected network interface to trusted sources where business-safe.
  • Monitor vendor guidance and exploitation sources for a material change.

Verification

  1. Confirm that the asset runs vitejs launch-editor and falls inside the recorded affected range.
  2. Verify the installed build against the product-specific fixed version after deployment.
  3. Validate exposure, authentication requirements and compensating controls in the actual environment.
  4. Reopen this reassessment when CVSS, KEV, EPSS, exploit evidence or remediation changes.
Mitigation target: Within 30 daysRemediation target: Within 180 days

This automated reassessment organises public evidence. It does not know asset exposure, business impact or control effectiveness and does not replace CVSS or a human risk decision.

Open-source package ranges4 source-attributed ranges

These OSV and GitHub advisory ranges apply only to the named package and ecosystem. A listed fixed version is not a universal product patch or proof that an update is installed.

Ecosystem and packageAffected rangeFirst fixed versionEvidence
npmlaunch-editor<= 2.8.22.9.0GitHub advisory ↗upstream repository advisory · 3 Jun 2026
npmlaunch-editorSEMVER: introduced 0; fixed 2.9.02.9.0OSV record ↗aggregator derived · 10 Sep 2026
npmvite<= 5.4.85.4.9GitHub advisory ↗upstream repository advisory · 3 Jun 2026
npmviteSEMVER: introduced 0; fixed 5.4.95.4.9OSV record ↗aggregator derived · 10 Sep 2026
Direct vendor intelligence

Authoritative vendor CSAF and VEX advisories

Structured product status and remediation from the issuing vendor. Product-state explanations are always visible; large lists can be searched or downloaded.

1 current
CVE-2024-52011 · CSAF 2.0 · revision 3 · finalRed Hat Product Securitylaunch-editor: vite: launch-editor: Arbitrary command execution via insufficient file argument sanitization
8 fixed

The vendor explicitly identifies these products or versions as containing the fix.

  • registry.redhat.io/cluster-observability-operator/logging-console-plugin-pf4-rhel9@sha256:1a883d0526f205beab9dfc51c5ac32b6a494dd950465b319076bf3a72e05e798_s390x as a component of Cluster Observability Operator 1.5.3
  • registry.redhat.io/cluster-observability-operator/logging-console-plugin-pf4-rhel9@sha256:2ef62503cd347fba4ae4e9fe659a39fd7ceeb6be9b29ac8c1a1071f378ad7fbc_ppc64le as a component of Cluster Observability Operator 1.5.3
  • registry.redhat.io/cluster-observability-operator/logging-console-plugin-pf4-rhel9@sha256:841c0c2af089daa79d66d73da42e9b7f1880db3ee27a1160e8e2f230f125c9f4_amd64 as a component of Cluster Observability Operator 1.5.3
  • registry.redhat.io/cluster-observability-operator/logging-console-plugin-pf4-rhel9@sha256:91568609093559b57722d4125b472a815fabb79888a56ac5e444d34a90c5f944_arm64 as a component of Cluster Observability Operator 1.5.3
  • registry.redhat.io/cluster-observability-operator/logging-console-plugin-pf5-rhel9@sha256:03182e8c0d9a28dd8dab831b3740bb588fd8d03f6783d24c492e53e52df5613d_arm64 as a component of Cluster Observability Operator 1.5.3
  • registry.redhat.io/cluster-observability-operator/logging-console-plugin-pf5-rhel9@sha256:2d882541f78495cb6ab25932d03947e038d5e477d878210e506dffcd787d201b_s390x as a component of Cluster Observability Operator 1.5.3
  • registry.redhat.io/cluster-observability-operator/logging-console-plugin-pf5-rhel9@sha256:ccce0a754cefa59c426bea1b1c8c345487a1cd35d147f50d8c2c881401b9ea7c_ppc64le as a component of Cluster Observability Operator 1.5.3
  • registry.redhat.io/cluster-observability-operator/logging-console-plugin-pf5-rhel9@sha256:cdd84d0f5e4fbe28071182219185e2dc5a1f478c48a14eb2a34ef9dc8d75dc96_amd64 as a component of Cluster Observability Operator 1.5.3
Summary
A flaw was found in launch-editor, a tool that allows users to open files with line numbers in an editor from Node.js. Due to insufficient sanitization of the `file` argument in the `launchEditor` function, an attacker can execute arbitrary commands on Windows systems by supplying a filename that contains special characters. This can lead to a complete compromise of the affected system.
Remediation
Before applying this update, make sure all previously released errata relevant to your system have been applied. For details on how to apply this update, refer to: https://access.redhat.com/articles/11258
Optional official sources

National CERT insights
?CERT means Computer Emergency Response Team; CSIRT is the closely related term Computer Security Incident Response Team.

Choose official national sources for this report. Each advisory shows its original language. Your selection is remembered on this device and included in shared links.

Official European source

ENISA European Vulnerability Database

Official EUVD identifiers, advisory evidence and known-exploited context. Missing fields are not treated as evidence of low risk.

1 current
ENISA EUVD identifier

EUVD-2024-55605

No EUVD known-exploited evidence

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.

EUVD state
Present in the current official mapping
Known exploitation
Not present in the current ENISA EUVD known-exploited dataset. This is not proof of no exploitation.
ENISA score
7.5 · CVSS 4.0
Advisory evidence
No linked advisory details stored yet
Recommended actionWithin 7 days

High technical severity; prioritise exposed affected systems while verifying vendor guidance.

Patch available
01

What, why and how

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.

What

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.

Why

Untrusted input reaches a command interpreter without sufficient validation or separation from command syntax.

How

An attacker operating through a network path may attempt exploitation when the stated preconditions are met. If successful, the issue may execute code or commands in the affected security context.

What

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.

Why

Untrusted input reaches a command interpreter without sufficient validation or separation from command syntax.

How

An attacker operating through a network path may attempt exploitation when the stated preconditions are met. If successful, the issue may execute code or commands in the affected security context.

02

Exploit reality and attack path

CVSS severity, EPSS forecast probability, public exploit material and CISA-confirmed exploitation are separate signals.

Observed exploitation
?Confirmed exploitation and public exploit material are separate signals. Attacks can occur without public proof-of-concept or exploit code.
No confirmed evidence

No CISA KEV match was present at the last successful refresh. This means no confirmation from that source, not proof of no exploitation.

Public PoC / exploit material
?Confirmed exploitation and public exploit material are separate signals. Attacks can occur without public proof-of-concept or exploit code.
None recorded

No exploit-tagged reference or CISA SSVC proof-of-concept state is currently recorded. Research may still exist outside the structured feeds.

Likely attack path
a network path → Improper Neutralization of Special Elements used in a Command ('Command Injection') → execute code or commands in the affected security context
Attack surface
Network
Privileges required
None: unauthenticated exploitation is possible
User interaction
Active interaction required
Attack complexity
Low: no specialised conditions are recorded
Security boundary
Not a CVSS 4.0 base metric
Weakness
?CWE means Common Weakness Enumeration: a standard category for the underlying weakness.
CWE-77 ↗

CWE-77: Improper Neutralization of Special Elements used in a Command ('Command Injection'). The product constructs all or part of a command using externally-influenced input from an upstream component, but it does not neutralize or incorrectly neutralizes special elements that could modify the intended command when it is sent to a downstream component.

CVSS vector
?CVSS means Common Vulnerability Scoring System. The vector records the metric values used to calculate technical severity.
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

Common Vulnerability Scoring System 4.0: the compact vector below is decoded into plain language.

AVNetworkAttack vector: The vulnerable component can be reached over a network.ACLowAttack complexity: No specialised conditions are required beyond attacker-controlled input.ATPresentAttack requirements: A particular deployment or execution condition must be present.PRNonePrivileges required: The attacker does not need an account or existing privileges.UIActiveUser interaction: A user must take a deliberate action for exploitation to succeed.VCHighVulnerable-system confidentiality: A successful attack can cause a major loss.VIHighVulnerable-system integrity: A successful attack can cause a major loss.VAHighVulnerable-system availability: A successful attack can cause a major loss.SCNoneSubsequent-system confidentiality: No direct loss is represented by this metric.SINoneSubsequent-system integrity: No direct loss is represented by this metric.SANoneSubsequent-system availability: No direct loss is represented by this metric.
Post-exploitation / living off the land
After compromise, an attacker may use built-in shells, scripting engines, scheduled tasks and native network utilities for discovery, persistence or movement. This is a plausible LoTL path, not evidence that it has occurred for every attack.
NetworkUnauthenticatedRemote code executionCWE-77
A

Official authority intelligence

Only matched European and national findings are included. Language selectors and unavailable sources are omitted.

ENISA EUVD · EUVD-2024-55605Official EUVD mapping

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.

Official EUVD record ↗
Cyber Security Agency of Singapore · English · CSA-SB-20260603Security Bulletin 3 Jun 2026

The Cyber Security Agency of Singapore included this CVE in its official Security Bulletin 3 Jun 2026, published on 3 June 2026. Open the linked bulletin for the product, severity and reference information published in that issue.

Official advisory ↗
03

Patch and workaround

Operational remediation based on structured source evidence.

Status
?Patch availability is based on structured fixed-version fields and authoritative update references. If no fix is verified, check the vendor advisory before making a change.
Patch available
Affected
Fixed
Action
Before applying this update, make sure all previously released errata relevant to your system have been applied. For details on how to apply this update, refer to: https://access.redhat.com/articles/11258
Workaround
No verified workaround is recorded. If business-safe, reduce exposure to the affected interface and allow only trusted sources until authoritative guidance is available.
04

Evidence and provenance

Published 1 Jun 2026 · Last source change 4 Sept 2026, 12:04 UTC · CWE-77 · Improper Neutralization of Special Elements used in a Command ('Command Injection')

CVE recordCVE.org · 5.2
CVSS sourceCNA
EPSS source
?The date BlackTree first stored a score for this CVE from the daily FIRST EPSS feed.
FIRST · tracked since 2026-08-14
European sourceENISA EUVD · EUVD-2024-55605
Product sourceCNA
Remediation sourceVendor CSAF · Red Hat Product Security
CWE sourceCNA
NVD statusNVD not scheduled

Core structured fields are present and their contributing authorities are shown above.

Material change intelligence

What changed after publication

View recent updates ↗
  1. Affected versionsThe structured affected or fixed version information changed.
    Before
    Fixed: registry.redhat.io/cluster-observability-operator/logging-console-plugin-pf4-rhel9@sha256:1a883d0526f205beab9dfc51c5ac32b6a494dd950465b319076bf3a72e05e798_s390x as a component of Cluster Observability Operator 1.5.0; registry.redhat.io/cluster-observability-operator/logging-console-plugin-pf4-rhel9@sha256:2ef62503cd347fba4ae4e9fe659a39fd7ceeb6be9b29ac8c1a1071f378ad7fbc_ppc64le as a component of Cluster Observability Operator 1.5.0; registry.redhat.io/cluster-observability-operator/logging-console-plugin-pf4-rhel9@sha256:841c0c2af089daa79d66d73da42e9b7f1880db3ee27a1160e8e2f230f125c9f4_amd64 as a component of Cluster Observability Operator 1.5.0; registry.redhat.io/cluster-observability-operator/logging-console-plugin-pf4-rhel9@sha256:91568609093559b57722d4125b472a815fabb79888a56ac5e444d34a90c5f944_arm64 as a component of Cluster Observability Operator 1.5.0; registry.redhat.io/cluster-observability-operator/logging-console-plugin-pf5-rhel9@sha256:03182e8c0d9a28dd8dab831b3740bb588fd8d03f6783d24c492e53e52df5613d_arm64 as a component of Cluster Observability Operator 1.5.0; registry.redhat.io/cluster-observability-operator/logging-console-plugin-pf5-rhel9@sha256:2d882541f78495cb6ab25932d03947e038d5e477d878210e506dffcd787d201b_s390x as a component of Cluster Observability Operator 1.5.0; registry.redhat.io/cluster-observability-operator/logging-console-plugin-pf5-rhel9@sha256:ccce0a754cefa59c426bea1b1c8c345487a1cd35d147f50d8c2c881401b9ea7c_ppc64le as a component of Cluster Observability Operator 1.5.0; registry.redhat.io/cluster-observability-operator/logging-console-plugin-pf5-rhel9@sha256:cdd84d0f5e4fbe28071182219185e2dc5a1f478c48a14eb2a34ef9dc8d75dc96_amd64 as a component of Cluster Observability Operator 1.5.0
    After
    Fixed: registry.redhat.io/cluster-observability-operator/logging-console-plugin-pf4-rhel9@sha256:1a883d0526f205beab9dfc51c5ac32b6a494dd950465b319076bf3a72e05e798_s390x as a component of Cluster Observability Operator 1.5.3; registry.redhat.io/cluster-observability-operator/logging-console-plugin-pf4-rhel9@sha256:2ef62503cd347fba4ae4e9fe659a39fd7ceeb6be9b29ac8c1a1071f378ad7fbc_ppc64le as a component of Cluster Observability Operator 1.5.3; registry.redhat.io/cluster-observability-operator/logging-console-plugin-pf4-rhel9@sha256:841c0c2af089daa79d66d73da42e9b7f1880db3ee27a1160e8e2f230f125c9f4_amd64 as a component of Cluster Observability Operator 1.5.3; registry.redhat.io/cluster-observability-operator/logging-console-plugin-pf4-rhel9@sha256:91568609093559b57722d4125b472a815fabb79888a56ac5e444d34a90c5f944_arm64 as a component of Cluster Observability Operator 1.5.3; registry.redhat.io/cluster-observability-operator/logging-console-plugin-pf5-rhel9@sha256:03182e8c0d9a28dd8dab831b3740bb588fd8d03f6783d24c492e53e52df5613d_arm64 as a component of Cluster Observability Operator 1.5.3; registry.redhat.io/cluster-observability-operator/logging-console-plugin-pf5-rhel9@sha256:2d882541f78495cb6ab25932d03947e038d5e477d878210e506dffcd787d201b_s390x as a component of Cluster Observability Operator 1.5.3; registry.redhat.io/cluster-observability-operator/logging-console-plugin-pf5-rhel9@sha256:ccce0a754cefa59c426bea1b1c8c345487a1cd35d147f50d8c2c881401b9ea7c_ppc64le as a component of Cluster Observability Operator 1.5.3; registry.redhat.io/cluster-observability-operator/logging-console-plugin-pf5-rhel9@sha256:cdd84d0f5e4fbe28071182219185e2dc5a1f478c48a14eb2a34ef9dc8d75dc96_amd64 as a component of Cluster Observability Operator 1.5.3
    Red Hat Product Security ↗
  2. Affected versionsThe structured affected or fixed version information changed.
    Before
    Fixed: registry.redhat.io/cluster-observability-operator/logging-console-plugin-pf4-rhel9@sha256:1a883d0526f205beab9dfc51c5ac32b6a494dd950465b319076bf3a72e05e798_s390x as a component of Cluster Observability Operator 1.5.2; registry.redhat.io/cluster-observability-operator/logging-console-plugin-pf4-rhel9@sha256:2ef62503cd347fba4ae4e9fe659a39fd7ceeb6be9b29ac8c1a1071f378ad7fbc_ppc64le as a component of Cluster Observability Operator 1.5.2; registry.redhat.io/cluster-observability-operator/logging-console-plugin-pf4-rhel9@sha256:841c0c2af089daa79d66d73da42e9b7f1880db3ee27a1160e8e2f230f125c9f4_amd64 as a component of Cluster Observability Operator 1.5.2; registry.redhat.io/cluster-observability-operator/logging-console-plugin-pf4-rhel9@sha256:91568609093559b57722d4125b472a815fabb79888a56ac5e444d34a90c5f944_arm64 as a component of Cluster Observability Operator 1.5.2; registry.redhat.io/cluster-observability-operator/logging-console-plugin-pf5-rhel9@sha256:03182e8c0d9a28dd8dab831b3740bb588fd8d03f6783d24c492e53e52df5613d_arm64 as a component of Cluster Observability Operator 1.5.2; registry.redhat.io/cluster-observability-operator/logging-console-plugin-pf5-rhel9@sha256:2d882541f78495cb6ab25932d03947e038d5e477d878210e506dffcd787d201b_s390x as a component of Cluster Observability Operator 1.5.2; registry.redhat.io/cluster-observability-operator/logging-console-plugin-pf5-rhel9@sha256:ccce0a754cefa59c426bea1b1c8c345487a1cd35d147f50d8c2c881401b9ea7c_ppc64le as a component of Cluster Observability Operator 1.5.2; registry.redhat.io/cluster-observability-operator/logging-console-plugin-pf5-rhel9@sha256:cdd84d0f5e4fbe28071182219185e2dc5a1f478c48a14eb2a34ef9dc8d75dc96_amd64 as a component of Cluster Observability Operator 1.5.2
    After
    Fixed: registry.redhat.io/cluster-observability-operator/logging-console-plugin-pf4-rhel9@sha256:1a883d0526f205beab9dfc51c5ac32b6a494dd950465b319076bf3a72e05e798_s390x as a component of Cluster Observability Operator 1.5.0; registry.redhat.io/cluster-observability-operator/logging-console-plugin-pf4-rhel9@sha256:2ef62503cd347fba4ae4e9fe659a39fd7ceeb6be9b29ac8c1a1071f378ad7fbc_ppc64le as a component of Cluster Observability Operator 1.5.0; registry.redhat.io/cluster-observability-operator/logging-console-plugin-pf4-rhel9@sha256:841c0c2af089daa79d66d73da42e9b7f1880db3ee27a1160e8e2f230f125c9f4_amd64 as a component of Cluster Observability Operator 1.5.0; registry.redhat.io/cluster-observability-operator/logging-console-plugin-pf4-rhel9@sha256:91568609093559b57722d4125b472a815fabb79888a56ac5e444d34a90c5f944_arm64 as a component of Cluster Observability Operator 1.5.0; registry.redhat.io/cluster-observability-operator/logging-console-plugin-pf5-rhel9@sha256:03182e8c0d9a28dd8dab831b3740bb588fd8d03f6783d24c492e53e52df5613d_arm64 as a component of Cluster Observability Operator 1.5.0; registry.redhat.io/cluster-observability-operator/logging-console-plugin-pf5-rhel9@sha256:2d882541f78495cb6ab25932d03947e038d5e477d878210e506dffcd787d201b_s390x as a component of Cluster Observability Operator 1.5.0; registry.redhat.io/cluster-observability-operator/logging-console-plugin-pf5-rhel9@sha256:ccce0a754cefa59c426bea1b1c8c345487a1cd35d147f50d8c2c881401b9ea7c_ppc64le as a component of Cluster Observability Operator 1.5.0; registry.redhat.io/cluster-observability-operator/logging-console-plugin-pf5-rhel9@sha256:cdd84d0f5e4fbe28071182219185e2dc5a1f478c48a14eb2a34ef9dc8d75dc96_amd64 as a component of Cluster Observability Operator 1.5.0
    Red Hat Product Security ↗
  3. Vendor guidanceAuthoritative vendor guidance changed: added remediation: github.com/GHSA-c27g-q93r-2cwf.
    Before
    no authoritative guidance recorded
    After
    remediation: github.com/GHSA-c27g-q93r-2cwf
    CNA ↗
  4. Affected versionsThe structured affected or fixed version information changed.
    Before
    < 2.9.0; < 5.4.9 · Fixed: No fixed version is explicitly recorded in the structured CVE data.
    After
    launch-editor: < 2.9.0; vite: < 5.4.9 · Fixed: RHSA-2026:34342: Cluster Observability Operator 1.5.0
    CNA ↗
  5. Remediation statusRemediation status changed from Awaiting fix to Patch available.
    Before
    Awaiting fix
    After
    Patch available
    CNA ↗
Material fields only · duplicate refreshes suppressed · history retained for the configured operational retention period
CVE published
Fixed release or patch reference recorded
ENISA EUVD · EUVD-2024-55605↗Vendor CSAF · Red Hat Product Security↗CVE authority or vendor reference · GitHub GHSA-C27G-Q93R-2CWF↗Official CVE record (CNA and ADP data)↗NVD record↗
Technical terms and abbreviations used in this report
CVE
Common Vulnerabilities and Exposures: the public identifier for one disclosed vulnerability.
CVSS
Common Vulnerability Scoring System: a technical severity framework; it is not patching priority by itself.
EPSS
Exploit Prediction Scoring System: FIRST's estimate of the probability that exploitation activity will be observed in the next 30 days; it is a forecast, not confirmation.
CWE
Common Weakness Enumeration: the standard category describing the underlying software or hardware weakness.
CNA
CVE Numbering Authority: an organisation authorised to assign and publish CVE records.
CISA ADP
Cybersecurity and Infrastructure Security Agency Authorized Data Publisher: structured enrichment added to a CVE record.
NVD
National Vulnerability Database: NIST's enrichment service for CVE records.
CERT / CSIRT
A computer security incident response team that publishes warnings or coordinates incident response.
PoC
Proof of concept: public material that demonstrates or helps reproduce exploitation.
CSAF
Common Security Advisory Framework: a machine-readable format for security advisories.
LoTL
Living off the land: abuse of legitimate tools or system functions during an attack.
Free version - for non-commercial use only.CVE-2024-52011 · cve.blacktree.nl