CVE-2024-52011

HIGHPre-NVD 8.38.3—
EchelonGraph scoreMEDIUM confidence

This high-severity CVE scores 8.3 under a secondary CVSS source (NVD's own analysis pending). EPSS exploit probability: 0.5%, top 59% of all CVEs by exploit prediction. GitHub Security Advisory data not yet ingested — confidence will rise once GHSA publishes (typical lag: hours to days for open-source ecosystem CVEs; never for infrastructure-only CVEs).

Triggered by: NVD CVSS baseline
Sources: epss, secondary
Trending — 3 sources updated this week
8.3EG
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 1%CVSS: 8.3Exploit: None knownExposed: 0

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.3(medium)
EG Risk
53(Track)
EG Risk 53/100SSVC: Track

EG Risk is EchelonGraph's 0–100 priority score: it fuses intrinsic severity with real-world exploitation and automatability so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner. Distinct from the 0–10 EG Score (severity).

How it’s computed
Severity83% × 45%
Exploitation1% × 40%
Automatability100% × 15%
Action: Routine — remediate on your standard cadence.
EPSS PROB
1%
EPSS %ILE
41%
KEV
Not listed

Published

June 1, 2026

Last Modified

July 21, 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 Patch Available

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(1)

Vendor / EcosystemFixed in / PatchReleasedSource
redhatcluster-observability-operator/logging-console-plugin-pf5-rhel9:17828405392026-07-01redhat

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 rangeFixed inDependents
launch-editor—2.9.0—
vite—5.4.9—

Weakness Classification(2)

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

Data Freshness Timeline

(refreshed 15× in last 7d / 55× in last 30d)

Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. 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. Most recent first.

  1. 2026-07-27 11:42 UTCVendor advisory
  2. 2026-07-26 23:16 UTCEG score recompute
  3. 2026-07-26 23:16 UTCVendor advisory
  4. 2026-07-26 14:53 UTCEPSS rescore
  5. 2026-07-26 14:53 UTCEPSS rescore
  6. 2026-07-25 14:17 UTCEPSS rescore
  7. 2026-07-25 14:16 UTCEPSS rescore
  8. 2026-07-24 14:16 UTCEPSS rescore
  9. 2026-07-23 14:17 UTCEPSS rescore
  10. 2026-07-23 14:17 UTCEPSS rescore
  11. 2026-07-23 02:43 UTCEG score recompute
  12. 2026-07-22 14:07 UTCEPSS rescore
  13. 2026-07-22 14:07 UTCEPSS rescore
  14. 2026-07-21 15:23 UTCEPSS rescore
  15. 2026-07-20 17:06 UTCEPSS rescore
  16. 2026-07-19 14:30 UTCEPSS rescore
  17. 2026-07-19 14:30 UTCEPSS rescore
  18. 2026-07-19 02:28 UTCEPSS rescore
  19. 2026-07-19 02:28 UTCEPSS rescore
  20. 2026-07-18 10:03 UTCEPSS rescore
  21. 2026-07-18 10:03 UTCEPSS rescore
  22. 2026-07-16 17:02 UTCEPSS rescore
  23. 2026-07-16 01:29 UTCVendor advisory
  24. 2026-07-15 16:57 UTCEPSS rescore
  25. 2026-07-15 16:56 UTCEPSS rescore
Show 71 more
  1. 2026-07-15 01:59 UTCEPSS rescore
  2. 2026-07-15 01:59 UTCEPSS rescore
  3. 2026-07-14 17:25 UTCVendor advisory
  4. 2026-07-14 05:29 UTCVendor advisory
  5. 2026-07-13 22:29 UTCEPSS rescore
  6. 2026-07-13 06:12 UTCEPSS rescore
  7. 2026-07-12 05:45 UTCEPSS rescore
  8. 2026-07-12 05:45 UTCEPSS rescore
  9. 2026-07-12 01:24 UTCVendor advisory
  10. 2026-07-11 13:28 UTCVendor advisory
  11. 2026-07-11 08:26 UTCEPSS rescore
  12. 2026-07-09 19:09 UTCEPSS rescore
  13. 2026-07-09 19:09 UTCEPSS rescore
  14. 2026-07-08 16:54 UTCVendor advisory
  15. 2026-07-08 15:14 UTCEPSS rescore
  16. 2026-07-07 13:45 UTCEPSS rescore
  17. 2026-07-06 16:26 UTCEPSS rescore
  18. 2026-07-06 02:22 UTCEPSS rescore
  19. 2026-07-05 02:29 UTCEPSS rescore
  20. 2026-07-04 06:30 UTCEPSS rescore
  21. 2026-07-02 14:00 UTCVendor advisory
  22. 2026-07-02 02:02 UTCVendor advisory
  23. 2026-07-01 15:05 UTCEPSS rescore
  24. 2026-06-30 23:21 UTCEPSS rescore
  25. 2026-06-30 23:19 UTCEG score recompute▲ 0.80
  26. 2026-06-30 04:33 UTCNVD updateCVSS v3 → 8.3
  27. 2026-06-29 14:05 UTCEPSS rescore
  28. 2026-06-28 14:07 UTCEPSS rescore
  29. 2026-06-28 04:55 UTCEPSS rescore
  30. 2026-06-28 04:55 UTCEPSS rescore
  31. 2026-06-27 03:07 UTCEPSS rescore
  32. 2026-06-27 03:07 UTCEPSS rescore
  33. 2026-06-25 13:49 UTCEPSS rescore
  34. 2026-06-24 14:04 UTCEPSS rescore
  35. 2026-06-24 14:04 UTCEPSS rescore
  36. 2026-06-23 21:32 UTCEPSS rescore
  37. 2026-06-23 21:32 UTCEPSS rescore
  38. 2026-06-22 14:25 UTCEPSS rescore
  39. 2026-06-22 14:25 UTCEPSS rescore
  40. 2026-06-21 14:56 UTCEPSS rescore
  41. 2026-06-21 01:59 UTCEPSS rescore
  42. 2026-06-21 01:58 UTCEPSS rescore
  43. 2026-06-19 19:25 UTCEPSS rescore
  44. 2026-06-18 17:52 UTCEPSS rescore
  45. 2026-06-18 17:52 UTCEPSS rescore
  46. 2026-06-17 17:52 UTCEPSS rescore
  47. 2026-06-17 17:52 UTCEPSS rescore
  48. 2026-06-16 17:52 UTCEPSS rescore
  49. 2026-06-16 17:52 UTCEPSS rescore
  50. 2026-06-15 17:47 UTCEPSS rescore
  51. 2026-06-14 23:17 UTCEPSS rescore
  52. 2026-06-13 22:59 UTCEPSS rescore
  53. 2026-06-13 22:59 UTCEPSS rescore
  54. 2026-06-13 22:59 UTCEPSS rescore
  55. 2026-06-12 23:11 UTCEPSS rescore
  56. 2026-06-12 23:11 UTCEPSS rescore
  57. 2026-06-11 13:59 UTCEPSS rescore
  58. 2026-06-10 22:18 UTCEPSS rescore
  59. 2026-06-10 13:21 UTCEPSS rescore
  60. 2026-06-08 14:16 UTCEPSS rescore
  61. 2026-06-08 14:16 UTCEPSS rescore
  62. 2026-06-07 15:24 UTCEPSS rescore
  63. 2026-06-07 15:24 UTCEPSS rescore
  64. 2026-06-05 22:46 UTCEPSS rescore
  65. 2026-06-05 22:46 UTCEPSS rescore
  66. 2026-06-05 06:09 UTCEPSS rescore
  67. 2026-06-05 06:09 UTCEPSS rescore
  68. 2026-06-04 13:11 UTCEPSS rescore
  69. 2026-06-04 13:11 UTCEPSS rescore
  70. 2026-06-02 20:12 UTCEPSS rescore
  71. 2026-06-01 20:45 UTCEG score recompute

Related CVEs(same vendor + same CWE)

Frequently asked(5)

What is CVE-2024-52011?
CVE-2024-52011 is a high vulnerability 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 CVE-2024-52011 disclosed?
CVE-2024-52011 was first published in the National Vulnerability Database on June 1, 2026, with the most recent update on July 21, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2024-52011 actively exploited?
CVE-2024-52011 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 1% probability of exploitation in the next 30 days, which ranks it in the top 59.2% of all scored CVEs.
What is the CVSS score of CVE-2024-52011?
CVE-2024-52011 has a CVSS v3 base score of 8.3 (NVD).
How do I remediate CVE-2024-52011?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2024-52011, EchelonGraph cross-links them in the Vendor Advisories panel below — those typically contain the canonical remediation steps, fixed version numbers, and any vendor-specific mitigations.

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.

Start Free Scan →Browse All CVEs