launch-editor vulnerabilities

launch editor from node.js

Registry
npm
Latest
2.14.2
License
MIT
Source
github.com/vitejs/launch-editor (opens the source repository in a new tab)

5 known advisories

The latest version, 2.14.2, is not affected by any of them. Projects on older versions may be.

Update to the latest version:npm install launch-editor@2.14.2

Security advisories for launch-editor

  • MediumGHSA-r825-w8mm-5pxw20 Oct 2026

    launch-editor: Editor CLI flag misinterpretation causing arbitrary command execution for some editors

    Affected
    <2.14.2
    Fixed in
    2.14.2
  • HighGHSA-587h-7wmj-h5pm20 Oct 2026

    launch-editor: `fs.existsSync()` existence check can be bypassed on Windows

    Affected
    <2.14.2
    Fixed in
    2.14.2
  • MediumGHSA-698v-4r3x-3vcv20 Oct 2026

    launch-editor: escapeCmdArgs() omits % escaping on Windows

    Affected
    <2.14.2
    Fixed in
    2.14.2
  • MediumGHSA-v6wh-96g9-6wx315 Jun 2026

    launch-editor: NTLMv2 hash disclosure via UNC path handling on Windows

    Affected
    <2.14.1
    Fixed in
    2.14.1
  • HighGHSA-c27g-q93r-2cwf3 Jun 2026

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

    Affected
    <2.9.0
    Fixed in
    2.9.0

Which of your client projects still run an old launch-editor?

NPMscan reads the package-lock.json, yarn.lock and pnpm-lock.yaml in every GitHub repo you pick and checks each installed version against these advisories, including the packages your packages pull in. Each finding comes with the command that fixes it.

Scan a project free, no signupOr connect GitHub to scan every repo

Other npm packages

Advisory data from OSV.dev (opens OSV.dev in a new tab), refreshed daily. Package details from the npm registry.