VulertSecurity VulertSecurity

Vulnerability Database · npm · Package report

launch-editor: vulnerability history, versions and safety

launch-editor is a package in the npm ecosystem. Vulert records 5 vulnerabilities for it across 23 releases, from Jun 2026 to Oct 2026. Each vulnerability names the versions it affects, the fixed version to move to, and a workaround where no fix has been published.

i
5 vulnerabilities recorded H2 M3
i
0 with no fix published

Every vulnerability has a patched version to move to.

i
5 in the last 12 months

Most recent disclosure 20 Oct 2026.

See the disclosure history →
i
0 malicious-package vulnerabilities

No published version shipped hostile code.

See all launch-editor vulnerabilities

Vulert verdict on launch-editor 2.14.2 i

Updated on 23 Oct 2026

Good news: 2.14.2, the version you would install today, has no known vulnerabilities. Older releases do — the table below lists all 5.

Package health score 75/100
  • Security Some issues to review
  • Maintenance Sustainable
  • Popularity Key ecosystem project
  • Community Quiet

What to do: Stay on 2.14.2 or newer. This can change: a vulnerability disclosed tomorrow can affect 2.14.2 too — Vulert watches the package and alerts you if that happens. Monitor it with Vulert →

  • Current release 2.14.2 — unaffected i
  • Vulnerabilities on record 5 over 1 year · 5 in the last year i
  • Latest disclosure 20 Oct 2026 i
  • Highest CVSS 7.5 i
  • With no published fix 0 i
  • Depended on by 47,000 packages i
  • Stars 719 i
  • Last release this month i
  • Licence MIT i

Version list, release dates, licence and dependants published by the npm registry, refreshed 23 Oct 2026. Licence information is not legal advice.

Concerned about your application's security?

Vulert continues monitoring your dependencies and alerts you when new vulnerabilities are disclosed. No installation and no source-code access required.

01 Versions

Which versions are affected

Every version Vulert tracks for launch-editor, newest first, with the vulnerabilities recorded against each one. A version showing none has no vulnerability in the Vulert database — open it for the full picture on that release.

i
Version Released Vulert vulnerabilities Licence Fix published Details
2.14.2 06 Oct 2026 none MIT — Details →
2.14.1 01 Jun 2026 H1 M2 MIT Yes Details →
2.14.0 29 May 2026 H1 M3 MIT Yes Details →
2.13.2 21 Mar 2026 H1 M3 MIT Yes Details →
2.13.1 25 Feb 2026 H1 M3 MIT Yes Details →
2.13.0 18 Feb 2026 H1 M3 MIT Yes Details →
2.12.0 28 Oct 2025 H1 M3 MIT Yes Details →
2.11.1 07 Aug 2025 H1 M3 MIT Yes Details →
2.11.0 28 Jul 2025 H1 M3 MIT Yes Details →
2.10.0 17 Feb 2025 H1 M3 MIT Yes Details →
2.9.1 05 Sep 2024 H1 M3 MIT Yes Details →
2.9.0 05 Sep 2024 H1 M3 MIT Yes Details →
2.8.2 03 Sep 2024 H2 M3 MIT Yes Details →
2.8.1 05 Aug 2024 H2 M3 MIT Yes Details →
2.8.0 19 Jun 2024 H2 M3 MIT Yes Details →
2.7.0 16 Jun 2024 H2 M3 MIT Yes Details →
2.6.1 07 Oct 2023 H2 M3 MIT Yes Details →
2.6.0 20 Aug 2022 H2 M3 MIT Yes Details →
2.5.0 04 Aug 2022 H2 M3 MIT Yes Details →
2.4.0 25 May 2022 H2 M3 MIT Yes Details →
2.3.0 21 Dec 2021 H2 M3 MIT Yes Details →
2.2.1 31 Jan 2018 H2 M3 MIT Yes Details →
2.0.0 06 Jan 2018 H2 M3 MIT Yes Details →
1.0.0 06 Jan 2018 H2 M3 MIT Yes Details →

All 24 versions Vulert tracks for this package. Severity counts are the vulnerabilities recorded against that exact release.

02 Disclosure history

How often vulnerabilities are recorded

  • 2026 5

Counted by the year Vulert recorded each vulnerability — the same date the table below shows as disclosed. 5 of the 5 were recorded in the last 12 months.

03 Vulnerabilities

Recorded vulnerabilities for launch-editor

The 5 most severe of 5 vulnerabilities recorded for this package

Search all 5 in the database →
Vulnerability Severity Fixed version ↓ Disclosed ↓
CVE-2024-52011: launch-editor Command Injection Vulnerability on Windows 7.5 high 2.9.0 03 Jun 2026
CVE-2026-112942: launch-editor Package Vulnerability - Windows Path Bypass Leading to Command Injection 7.5 high 2.14.2 20 Oct 2026
CVE-2026-112943: launch-editor Package Vulnerability Due to Improper % Escaping on Windows 6.3 medium 2.14.2 20 Oct 2026
CVE-2026-112944: launch-editor Package Arbitrary Command Execution Vulnerability 6.3 medium 2.14.2 20 Oct 2026
CVE-2026-53632: launch-editor Package NTLMv2 Hash Disclosure via UNC Path Handling on Windows 5.5 medium 2.14.1 15 Jun 2026

Vulnerability wrong, a fix missing, or a package we should cover? Report it and we will fix the record. Report Vulnerability Provide Feedback

Updated: 23/Oct/2026 · Vulnerabilities in our DB: 524315

Subscribe to Vulert on Telegram
Daily digest of new CVEs, critical and high severity, affected packages and fixes — plus a weekly roundup.
Join the channel →

Questions

About launch-editor

Is launch-editor safe to use?

Vulert records 5 vulnerabilities for launch-editor in npm: 0 critical, 2 high, 3 medium and 0 low. Every one of them has a published fix, so the practical answer is to run a supported release and keep it patched.

What is launch-editor's Vulert package health score?

Vulert scores launch-editor 75/100, which reads as in good shape. The score weighs the vulnerability record (40), maintenance and release cadence (25), adoption from dependents and stars (20) and community signals such as the OpenSSF scorecard and forks (15).

Is the latest version of launch-editor affected?

No. 2.14.2, the version you would install today, has no vulnerabilities on record against it. Earlier releases do — the version table above lists each release with what affects it.

Which version of launch-editor should I use?

2.14.2 is the version Vulert recommends for the affected releases. The version table above lists every release with the vulnerabilities recorded against it, so you can confirm the range you actually run.

How many vulnerabilities does launch-editor have?

5 vulnerabilities are recorded for launch-editor in the npm ecosystem: 0 critical, 2 high, 3 medium and 0 low. The ledger on this page lists the same counts next to the date of the most recent disclosure.

How often are new launch-editor vulnerabilities disclosed?

5 vulnerabilities were recorded for launch-editor in the last 12 months, and the oldest entry in this database dates to 03 Jun 2026. Recency matters more than a lifetime total: it shows how actively new issues are being disclosed for the package you are considering.

Which versions of launch-editor are affected?

Each vulnerability on this page lists the affected version range and the fixed version to move to. Open the vulnerability for the version you actually run — fixes are specific to a release line, not to the package as a whole.

How do I monitor launch-editor for upcoming vulnerabilities?

Upload the manifest or SBOM for your application at vulert.com/scanner and Vulert keeps checking the launch-editor version you actually run against new disclosures, then alerts you when one affects it. There is no installation and no source-code access required.