CVE-2024-52011

HIGHPre-NVD 8.38.3
EchelonGraph scoreMEDIUM confidence

“—” beside the score: it is equal to the CVSS score beside it.

This high-severity CVE scores 8.3 under a secondary CVSS source (NVD's own analysis pending). EPSS exploit probability: 0.5% (43rd percentile of EPSS-scored CVEs). No GitHub Security Advisory CVSS is on record for this CVE.

Triggered by: Headline CVSS from a secondary CVSS source
Sources: EPSS, a secondary CVSS source
Trending — 4 sources updated this week

Also known asEUVD-2024-55605 (ENISA EUVD) · GHSA-c27g-q93r-2cwf (GitHub Security Advisories)Source: ENISA EUVD

8.3EG
EchelonGraph verdictPlan a fixRemediate within your standard update timelines at low or medium mission impact and sooner than that at high (the SSVC decision on this page).
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 0.5%CVSS: 8.3Exploit: None knownExposed services: Not assessed

A fix is available — apply it.

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.

CVSS v3
8.3
EG Score
8.3HIGHmedium confidence
EG Risk
53
EG Risk 53/100

EG Risk is EchelonGraph's 0–100 priority score. It fuses impact severity (EG Severity, the CVSS base score, never the KEV-floored or EPSS-lifted EG Score) with real-world exploitation and automatability, under weights EchelonGraph set by hand, so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner.

How it’s computed (value × EchelonGraph’s weight)
Severity83% × 45%
Impact severity (EG Severity): CVSS 8.3 of 10. Never the KEV-floored or EPSS-lifted EG Score.
Exploitation0.5% × 40%
FIRST EPSS: the 30-day exploitation probability when EchelonGraph scored this CVE.
Automatability100% × 15%
CISA's SSVC Automatable value: yes (Vulnrichment).
SSVC (CISA's decision table, applied by EchelonGraph): Track at low or medium mission impact; Attend at high (mission-essential systems).
Exploitation none (CISA Vulnrichment) · Automatable yes (CISA Vulnrichment) · Technical impact total (CISA Vulnrichment). All three are CISA's SSVC values (Vulnrichment). EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE.
Action: A fix is available. Apply it within your standard update timelines at low or medium mission impact and sooner than that at high.
EPSS PROB
0.5%
EPSS %ILE
43rd
KEV
Not listed

What the EG score is made of (scorer v4.0: the three questions the 0–10 score mixes, published apart · methodology)

The EG score (8.3): severity, escalated by confirmed exploitation. This CVE's 8.3 is its impact severity (EG Severity), not escalated.

EG Severity
8.3 HIGHCVSS-B, impact only: no KEV listing, EPSS or EG-KEV tier raises it.a secondary CVSS source · CVSS v3.0 or v3.1
EG Likelihood
0.5% within 30 daysSource: FIRST EPSS (model v2026.06.15, score date 2026-10-31). FIRST's exploitation probability, not an EchelonGraph model.
Confirmed exploitation
None on record (CISA KEV, EG-KEV Tier 1)Reported apart from the likelihood: an observed fact, not a probability.
EG Priority
SSVC Track at medium mission impactTrack at low or medium mission impact; Attend at high (mission-essential systems).CISA BOD 26-04: 3 days if the affected system is publicly exposed; 60 days if it is not.Each input and its source, and whom BOD 26-04 binds: the SSVC and BOD 26-04 blocks below.

SSVC (CISA's decision table, applied by EchelonGraph)Track at low or medium mission impact; Attend at high (mission-essential systems).

A fix is available. Apply it within your standard update timelines at low or medium mission impact and sooner than that at high.

Exploitation none (CISA Vulnrichment) · Automatable yes (CISA Vulnrichment) · Technical impact total (CISA Vulnrichment). All three are CISA's SSVC values (Vulnrichment). EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE. Mission impact is CISA's Mission & Well-being decision point, and only you can judge it. CISA's table makes it high when Mission Prevalence is Essential — the vulnerable component "directly provides capabilities that constitute at least one MEF for at least one entity" (MEF: mission essential function) — or when Public Well-Being Impact is Irreversible: "multiple fatalities are likely", the cyber-physical system "is likely lost or destroyed", "extreme or serious externalities" are imposed on other parties, or social systems such as elections or the financial grid "are destabilized and potentially collapse". CISA's decision table

BOD 26-04 (CISA's remediation timeline, Table 1)3 days if the affected system is publicly exposed; 60 days if it is not.

The score's inputs: In CISA KEV no (CISA's KEV catalog) · Automatable yes (CISA Vulnrichment) · Technical impact total (CISA Vulnrichment). Whether your system is publicly exposed is yours to answer. BOD 26-04 binds US Federal Civilian Executive Branch agencies; for anyone else it is CISA's published timeline, a reference rather than an obligation. The directive · how EchelonGraph applies it

Published

June 1, 2026

Last Modified

September 4, 2026

Advisory Details (2)

Auto-updated Jun 4, 2026
Patch available. Sources: github_commit, github.
GitHub commit

commit 971291e8a6a9 (vitejs/launch-editor)

Fix landed in vitejs/launch-editor commit 971291e8a6a9 — awaiting tagged release

https://github.com/vitejs/launch-editor/commit/971291e8a6a91226e1616c5c0ec85423d2d50a5e
GitHub advisoryMentions a patch (unverified)

Command injection via the crafted request on Windows · Advisory · vitejs/launch-editor · GitHub

https://github.com/vitejs/launch-editor/security/advisories/GHSA-c27g-q93r-2cwf

Vendor Advisories for CVE-2024-52011(2)

These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.

Patch Availability(3)

Vendor / EcosystemFix (by version range) / PatchReleasedSource
redhatcluster-observability-operator/logging-console-plugin-pf5-rhel9:17828405392026-07-01redhat
npmlaunch-editor @ 2.9.0 (fixes <= 2.8.2)—ghsa
npmvite @ 5.4.9 (fixes <= 5.4.8)—ghsa

Patches are aggregated from vendor advisories (Red Hat, Microsoft, Cisco, GitHub) and package ecosystems (OSV, GHSA). Multiple rows for the same upstream release have been deduplicated.

Affected Packages

(2 across 1 ecosystem)
npm(2)
PackageVulnerable rangeFix by version rangeDependents
launch-editor—
  • every version up to 2.9.0: fixed in 2.9.0
—
vite—
  • every version up to 5.4.9: fixed in 5.4.9
—

Weakness Classification(2)

MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.

Data Freshness Timeline

(refreshed 11× in last 7d / 42× in last 30d)

Each row is a time one of our pipelines fetched, updated or re-scored this CVE. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. An arrow marks a change the record states ("CVSS v3 → 9.1"); EPSS and GHSA rows show the values recorded at that time, not what changed (EPSS values are rounded; hover one for the exact figures). Most recent first.

Showing the most recent 95 of 276 refreshes on record for this CVE.

A repeat, a row identical to one the same pipeline wrote less than 10 seconds earlier, is not a separate refresh and is not counted. 5 repeat rows among the latest 100 are merged into the row they repeat. The 181 oldest rows on record are not shown and were not checked, so the counts can still include repeats.

  1. 2026-11-01 16:31 UTCEPSS rescoreEPSS 0.5% · 43rd percentile
  2. 2026-11-01 08:11 UTCGHSA enrichmentGHSA-c27g-q93r-2cwf · GitHub severity HIGH
  3. 2026-11-01 08:11 UTCEG score recompute
  4. 2026-10-31 16:30 UTCEPSS rescoreEPSS 0.5% · 43rd percentile
  5. 2026-10-30 16:32 UTCEPSS rescoreEPSS 0.5% · 43rd percentile
  6. 2026-10-29 16:31 UTCEPSS rescoreEPSS 0.5% · 43rd percentile
  7. 2026-10-28 16:29 UTCEPSS rescoreEPSS 0.5% · 43rd percentile
  8. 2026-10-27 20:05 UTCEG score recompute
  9. 2026-10-27 20:05 UTCVendor advisory
  10. 2026-10-27 16:30 UTCEPSS rescoreEPSS 0.5% · 43rd percentile
  11. 2026-10-26 16:29 UTCEPSS rescoreEPSS 0.5% · 43rd percentile
  12. 2026-10-25 16:57 UTCEG score recompute
  13. 2026-10-25 16:30 UTCEPSS rescoreEPSS 0.5% · 43rd percentile
  14. 2026-10-24 16:30 UTCEPSS rescoreEPSS 0.5% · 43rd percentile
  15. 2026-10-23 16:30 UTCEPSS rescoreEPSS 0.5% · 42nd percentile
  16. 2026-10-22 16:31 UTCEPSS rescoreEPSS 0.5% · 42nd percentile
  17. 2026-10-21 16:30 UTCEPSS rescoreEPSS 0.5% · 42nd percentile
  18. 2026-10-20 16:30 UTCEPSS rescoreEPSS 0.5% · 42nd percentile
  19. 2026-10-19 16:30 UTCEPSS rescoreEPSS 0.5% · 42nd percentile
  20. 2026-10-19 16:21 UTCEG score recompute
  21. 2026-10-19 16:21 UTCVendor advisory
  22. 2026-10-18 16:30 UTCEPSS rescoreEPSS 0.5% · 42nd percentile
  23. 2026-10-18 06:53 UTCEG score recompute
  24. 2026-10-17 16:31 UTCEPSS rescoreEPSS 0.5% · 42nd percentile
  25. 2026-10-16 16:37 UTCEPSS rescoreEPSS 0.5% · 42nd percentile
Show 70 more
  1. 2026-10-15 16:30 UTCEPSS rescoreEPSS 0.5% · 42nd percentile
  2. 2026-10-14 16:30 UTCEPSS rescoreEPSS 0.5% · 42nd percentile
  3. 2026-10-13 16:31 UTCEPSS rescoreEPSS 0.5% · 42nd percentile
  4. 2026-10-12 17:40 UTCEG score recompute
  5. 2026-10-12 16:31 UTCEPSS rescoreEPSS 0.5% · 42nd percentile
  6. 2026-10-11 21:06 UTCEG score recompute
  7. 2026-10-11 15:58 UTCEG score recompute
  8. 2026-10-11 13:46 UTCEPSS rescoreEPSS 0.5% · 42nd percentile
  9. 2026-10-10 19:58 UTCEPSS rescoreEPSS 0.5% · 42nd percentile
  10. 2026-10-09 20:05 UTCEPSS rescoreEPSS 0.5% · 42nd percentile
  11. 2026-10-08 17:08 UTCEPSS rescoreEPSS 0.5% · 41st percentile
  12. 2026-10-07 23:46 UTCEPSS rescoreEPSS 0.5% · 41st percentile
  13. 2026-10-06 15:16 UTCEPSS rescoreEPSS 0.5% · 41st percentile
  14. 2026-10-05 17:41 UTCEPSS rescoreEPSS 0.5% · 41st percentile
  15. 2026-10-04 23:20 UTCEPSS rescoreEPSS 0.5% · 41st percentile
  16. 2026-10-03 14:24 UTCEPSS rescoreEPSS 0.5% · 41st percentile
  17. 2026-10-03 13:39 UTCOSV refresh
  18. 2026-10-02 16:19 UTCEG score recompute
  19. 2026-10-01 19:48 UTCEPSS rescoreEPSS 0.5% · 41st percentile
  20. 2026-09-30 15:02 UTCEPSS rescoreEPSS 0.5% · 41st percentile
  21. 2026-09-29 15:18 UTCEPSS rescoreEPSS 0.5% · 41st percentile
  22. 2026-09-28 13:50 UTCEPSS rescoreEPSS 0.5% · 41st percentile
  23. 2026-09-27 13:44 UTCEPSS rescoreEPSS 0.5% · 41st percentile
  24. 2026-09-26 15:57 UTCEPSS rescoreEPSS 0.5% · 41st percentile
  25. 2026-09-24 14:01 UTCEPSS rescoreEPSS 0.5% · 41st percentile
  26. 2026-09-23 13:46 UTCEPSS rescoreEPSS 0.5% · 42nd percentile
  27. 2026-09-22 14:47 UTCEPSS rescoreEPSS 0.5% · 42nd percentile
  28. 2026-09-20 20:14 UTCEPSS rescoreEPSS 0.5% · 42nd percentile
  29. 2026-09-19 15:40 UTCEPSS rescoreEPSS 0.5% · 42nd percentile
  30. 2026-09-18 19:26 UTCEPSS rescoreEPSS 0.5% · 42nd percentile
  31. 2026-09-17 19:27 UTCEPSS rescoreEPSS 0.5% · 42nd percentile
  32. 2026-09-16 14:06 UTCEPSS rescoreEPSS 0.5% · 42nd percentile
  33. 2026-09-16 05:12 UTCEPSS rescoreEPSS 0.5% · 42nd percentile
  34. 2026-09-15 03:08 UTCEPSS rescoreEPSS 0.5% · 42nd percentile
  35. 2026-09-14 06:06 UTCEG score recompute
  36. 2026-09-14 06:06 UTCVendor advisory
  37. 2026-09-13 16:45 UTCEPSS rescoreEPSS 0.5% · 42nd percentile
  38. 2026-09-12 14:59 UTCEPSS rescoreEPSS 0.5% · 42nd percentile
  39. 2026-09-11 14:51 UTCEPSS rescoreEPSS 0.5% · 42nd percentile
  40. 2026-09-11 09:35 UTCEPSS rescoreEPSS 0.5% · 42nd percentile
  41. 2026-09-10 09:33 UTCEPSS rescoreEPSS 0.5% · 42nd percentile
  42. 2026-09-08 21:58 UTCEPSS rescoreEPSS 0.5% · 41st percentile
  43. 2026-09-07 16:00 UTCEPSS rescoreEPSS 0.5% · 41st percentile
  44. 2026-09-06 13:46 UTCEPSS rescoreEPSS 0.5% · 41st percentile
  45. 2026-09-04 13:59 UTCEPSS rescoreEPSS 0.5% · 41st percentile
  46. 2026-09-04 13:29 UTCEG score recompute
  47. 2026-09-04 13:29 UTCVendor advisory
  48. 2026-09-04 12:21 UTCEG score recompute
  49. 2026-09-04 12:21 UTCVendor advisory
  50. 2026-09-04 05:05 UTCEPSS rescoreEPSS 0.5% · 41st percentile
  51. 2026-09-02 14:10 UTCEPSS rescoreEPSS 0.5% · 41st percentile
  52. 2026-09-01 13:52 UTCEPSS rescoreEPSS 0.5% · 41st percentile
  53. 2026-09-01 04:37 UTCEPSS rescoreEPSS 0.5% · 41st percentile
  54. 2026-08-31 13:31 UTCEG score recompute
  55. 2026-08-31 13:31 UTCVendor advisory
  56. 2026-08-31 12:30 UTCEG score recompute
  57. 2026-08-31 12:30 UTCVendor advisory
  58. 2026-08-30 19:16 UTCEPSS rescoreEPSS 0.5% · 41st percentile
  59. 2026-08-30 01:20 UTCEPSS rescoreEPSS 0.5% · 41st percentile
  60. 2026-08-28 21:39 UTCEPSS rescoreEPSS 0.5% · 41st percentile
  61. 2026-08-27 14:23 UTCEPSS rescoreEPSS 0.5% · 41st percentile
  62. 2026-08-26 14:44 UTCEPSS rescoreEPSS 0.5% · 41st percentile
  63. 2026-08-25 13:47 UTCEPSS rescoreEPSS 0.5% · 41st percentile
  64. 2026-08-25 03:51 UTCEG score recompute
  65. 2026-08-25 03:51 UTCVendor advisory
  66. 2026-08-24 14:15 UTCEPSS rescoreEPSS 0.5% · 41st percentile
  67. 2026-08-23 13:50 UTCEG score recompute
  68. 2026-08-23 13:50 UTCVendor advisory
  69. 2026-08-23 00:18 UTCEPSS rescoreEPSS 0.5% · 41st percentile
  70. 2026-08-21 23:47 UTCEPSS rescoreEPSS 0.5% · 41st percentile

Related CVEs(same product + same vendor + same CWE)

Frequently asked(5)

What is CVE-2024-52011?
CVE-2024-52011 is a high-severity vulnerability; its CVE record was published on June 1, 2026. 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.…
When was the CVE record for CVE-2024-52011 published?
The CVE record for CVE-2024-52011 was published on June 1, 2026. That is the record's publication date; the vulnerability itself may have been made public earlier. EchelonGraph's copy of the record carries a last-modified date of September 4, 2026; the record at its source may have been updated since.
Is CVE-2024-52011 actively exploited?
CVE-2024-52011 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.5% probability of exploitation in the next 30 days (43rd percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2024-52011?
CVE-2024-52011 has a CVSS base score of 8.3 (a secondary CVSS source that NVD displays; NVD's own analysis pending).
How do I remediate CVE-2024-52011?
A fix for CVE-2024-52011 is available: update to the fixed version the vendor names in its advisory. The vendor advisories EchelonGraph has for CVE-2024-52011 are linked in the Vendor Advisories panel on this page.

Dependency Blast Radius

See which npm, PyPI, Go, and Maven packages are affected by CVE-2024-52011

Explore →

Is Your Infrastructure Affected by CVE-2024-52011?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.

Book a Demo →Browse All CVEs