---
title: "launch-editor security advisories"
description: "5 known security advisories for launch-editor, with the versions they affect and the version that fixes each."
url: https://inlinr.com/packages/launch-editor/security
lang: en
---

[Packages](https://inlinr.com/packages)

# launch-editor

2.14.2 · 6 Oct 2026 MIT 30.3M / week [Repository](https://github.com/vitejs/launch-editor) [Homepage](https://github.com/vitejs/launch-editor#readme) [npm](https://www.npmjs.com/package/launch-editor) [Atom feed](https://inlinr.com/packages/feed/launch-editor)

Your version 

## Security advisories

From OSV, open ones first. Each release line gets its own fix: an older major is fixed by a patch on that major, not by moving to the newest one.

| Line | Newest | Where it stands                                                           |
| ---- | ------ | ------------------------------------------------------------------------- |
|      | 2.14.2 | Safe from 2.14.2                                                          |
|      | 1.0.0  | 5 open advisories, worst high  · last release Jan 2018, no longer updated |

- High  
[launch-editor: \`fs.existsSync()\` existence check can be bypassed on Windows](https://inlinr.com/advisories/GHSA-587h-7wmj-h5pm)GHSA-587h-7wmj-h5pm · 20 Oct 2026  
fixed in 2.14.2
- High  
[launch-editor vulnerable to command injection via the crafted request on Windows](https://inlinr.com/advisories/GHSA-c27g-q93r-2cwf)GHSA-c27g-q93r-2cwf · 3 Jun 2026  
fixed in 2.9.0
- Moderate  
[launch-editor: Editor CLI flag misinterpretation causing arbitrary command execution for some editors](https://inlinr.com/advisories/GHSA-r825-w8mm-5pxw)GHSA-r825-w8mm-5pxw · 20 Oct 2026  
fixed in 2.14.2
- Moderate  
[launch-editor: escapeCmdArgs() omits % escaping on Windows](https://inlinr.com/advisories/GHSA-698v-4r3x-3vcv)GHSA-698v-4r3x-3vcv · 20 Oct 2026  
fixed in 2.14.2
- Moderate  
[launch-editor: NTLMv2 hash disclosure via UNC path handling on Windows](https://inlinr.com/advisories/GHSA-v6wh-96g9-6wx3)GHSA-v6wh-96g9-6wx3 · 15 Jun 2026  
fixed in 2.14.1

### Quality and security signals

What [npm](https://www.npmjs.com/package/launch-editor) and [deps.dev](https://deps.dev/npm/launch-editor) say about the latest release. Signals, not a verdict.

- Licence  
[MIT](https://spdx.org/licenses/MIT.html)
- Provenance  
[Present](https://www.npmjs.com/package/launch-editor/v/2.14.2#provenance), built from [github.com/vitejs/launch-editor](https://github.com/vitejs/launch-editor)  
Says where the release was built and from which commit. It does not say the code is safe.
- Published by  
GitHub Actions
- Maintainers on npm  
[yyx990803](https://www.npmjs.com/~yyx990803), [soda](https://www.npmjs.com/~soda), [sapphi-red](https://www.npmjs.com/~sapphi-red)
- Size  
[36 kB unpacked , 16 files](https://www.npmjs.com/package/launch-editor/v/2.14.2?activeTab=code)
- GitHub stars  
724 on [vitejs/launch-editor](https://github.com/vitejs/launch-editor)
- Last release  
[2.14.2](https://www.npmjs.com/package/launch-editor/v/2.14.2), 6 October 2026
- OpenSSF Scorecard  
No Scorecard for this repository

Reading releases, release notes and advisories…

Registry facts last checked 15 Nov 2026\. Releases and advisories last read 20 Nov 2026.

A whole project to check? Paste its package.json in the [dependency check](https://inlinr.com/tools/dependency-check): every deprecated, outdated or vulnerable dependency, with what to upgrade to. Free, no account.
