Breaking: Java4Shell (CVE-2026-114938) - Less Than 0.12% of JVMs Estimated at Risk of RCE
Read the Report
Learn How MCP Is Bypassing a Decade of Cloud Security Best Practices
Read the Report
Are you exposed? Connect a repo in minutes.
Scan your repos free

launch-editor

npm package

Overview

Newest range
2.14.2
Last CVE
20 Oct 2026
npm 4 version ranges 3 affected
0 Critical
2 High
3 Medium
0 Low

Package versions

Version ranges and their known vulnerabilities
VersionsRangeDirect vulnerabilities
2.14.2 and later versions 0000
2.14.1 up to 2.14.2 0120
2.9.0 up to 2.14.1 0130
before 2.9.0 all earlier versions 0230

No known vulnerabilities in 2.14.2 and later versions

Nothing in our data affects this version.

4 ranges in total. Each row is a range of versions with the same vulnerabilities, newest first. The data names only the versions where something changes (first affected, fixed), so the versions in between are a range.

Vulnerabilities · 5

Known vulnerabilities of this package
CVESeverityPublishedVulnerableFixed in
CVE-2026-112944launch-editor: launch-editor: Arbitrary command execution via improper filename handling MEDIUM 20 Oct 2026 <2.14.2 2.14.2
CVE-2026-112943launch-editor: launch-editor: Arbitrary code execution via improper argument escaping on Windows MEDIUM 20 Oct 2026 <2.14.2 2.14.2
CVE-2026-112942launch-editor: launch-editor: Command injection via improper file path validation HIGH 20 Oct 2026 <2.14.2 2.14.2
CVE-2026-53632launch-editor: launch-editor: Credential compromise via NTLMv2 password hash leak through UNC path access MEDIUM 22 Jun 2026 <2.14.1 2.14.1
CVE-2024-52011launch-editor: vite: launch-editor: Arbitrary command execution via insufficient file argument sanitization HIGH 1 Jun 2026 <2.9.0 2.9.0

Seal Security (npm)

Seal Security ships a patched build of this package. Its fixed versions:

  • CVE-2026-112942: 2.10.0-sp2
  • CVE-2026-112943: 2.10.0-sp2
  • CVE-2026-112944: 2.10.0-sp2

OX Radar and Response Center

Find threats in your stack.

OX Radar can check high-priority threats, like critical package CVEs, against your context.

Each incident is marked Detected or Not Detected with a remediation plan and proof all tracked in the Response Center.