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

Exploitation

No confirmed exploitation recorded. Patch Next marks exploitation only from CISA KEV.

CVSS 4.0

6.3 · CVSS:4.0/AV:N/AC:L/AT:P/PR:N/UI:N/VC:L/VI:L/VA:L/SC:N/SI:N/SA:N · score source

EPSS

• CVE-2026-112943: 0.41% estimated exploitation activity in the next 30 days; percentile 35.77 (FIRST EPSS, 2026-11-03). This is a model estimate, not proof of exploitation or customer exposure.

As published by the source; long descriptions are shortened.

Summary launch-editor did not escape % on Windows when passing an argument to cmd. When an environment variable contained a malicious value, it was possible that that content to be executed. Impact Only apps that match all of the following conditions are affected: - The user uses Windows - An attacker can place a file with the malicious filename containing & or % - Either of - An attacker can inject an environment variable with a malicious value - An attacker can add a NTFS alternate data stream to the file placed Details Unlike .sh files, .bat / .cmd files on Windows cannot be called directly using childprocess.spawn and requires passing them as an argument of cmd.exe. To do so, launch-editor escapes the arguments passed to cmd.exe. But launch-editor did not escape % which is used for environment variables. Because launch-editor checks if the argument matches an existing filename, the attack requires the attacker to be able to place a file. - If the attacker can inject an…

Published by the source

20 Oct 2026, 18:30 UTC

Last modified by the source

20 Oct 2026, 18:45 UTC

Source last checked

26 Oct 2026, 13:07 UTC

1. Revision 4 · amended · 26 Oct 2026

   Amended from ghsa record GHSA-698v-4r3x-3vcv

2. Revision 3 · amended · 24 Oct 2026

   Reviewed OSV alias/range/CVSS4 correction; package source scopes and original publication preserved. No customer finding resolved.

3. Revision 2 · amended · 24 Oct 2026

   Amended from osv record GHSA-698v-4r3x-3vcv

4. Revision 1 · created · 23 Oct 2026

   Published from ghsa record GHSA-698v-4r3x-3vcv

Preview the exact text before you copy it. Commands are read-only suggestions; review them before running anything.

# Patch Next advisory brief: CVE-2026-112943

Advisory: launch-editor: escapeCmdArgs() omits % escaping on Windows
IDs: CVE-2026-112943, GHSA-698v-4r3x-3vcv
Record: https://patchnext.com/advisories/cve-2026-112943 (revision 4, source checked 26 Oct 2026, 13:07 UTC)
Inventory: none attached. This brief comes from a public page and does not say whether any deployment is affected.
Severity: Medium (CVSS 6.3)
Exploitation: no confirmed exploitation recorded. Patch Next confirms exploitation only from CISA KEV.
Vendor response: Vendor fix available; fixed versions by package: vite 8.3.3, 8.2.4, 8.1.6, 7.3.7, 6.4.4; vite-plus 1.1.0; launch-editor 2.14.2. A vendor fix does not mean a deployment is fixed.

## Affected components
- npm vite: affected >= 8.3.0, <= 8.3.2; >= 8.2.0, <= 8.2.3; >= 8.0.0, <= 8.1.5; >= 7.0.0, <= 7.3.6; <= 6.4.3; fixed in 7.3.7, 8.2.4, 8.1.6, 8.3.3, 6.4.4
- npm vite-plus: affected <= 1.0.0; fixed in 1.1.0
- npm launch-editor: affected <= 2.14.1; fixed in 2.14.2

## Suggested inspection (read-only)
- `npm ls vite --all`: lists every installed copy and version, including transitive ones. Run in the project root after `npm ci`.
- `npm ls vite-plus --all`: lists every installed copy and version, including transitive ones. Run in the project root after `npm ci`.
- `npm ls launch-editor --all`: lists every installed copy and version, including transitive ones. Run in the project root after `npm ci`.

## Supported action
Upgrade each affected component to a fixed version on its release line. For a transitive dependency, upgrade the parent package or add an override or constraint, then regenerate the lockfile. Redeploy every environment that ran an affected version.

## Required regression checks
- Run the test suite and a production build.
- Exercise the features that depend on vite, vite-plus, launch-editor.
- Repeat the inspection and confirm that only fixed versions remain installed.

## Rollback considerations
- Keep the previous lockfile and deployment artifact. Rolling back reinstates the vulnerable version, so apply any documented mitigation while you fix forward.

## Unresolved questions
- Which deployments run an affected version?
- Exploitation status can change. Check again before lowering the priority.
- Mark the work resolved only after the fixed version is verified in production.

## Sources
- Verified: https://github.com/advisories/GHSA-698v-4r3x-3vcv (GitHub-reviewed advisory GHSA-698v-4r3x-3vcv lists affected ranges: npm launch-editor >=0 =8.3.0 =8.2.0 =8.0.0 =7.0.0 =0 =0 <=1.0.0)
- Verified: https://osv.dev/vulnerability/GHSA-698v-4r3x-3vcv (OSV record GHSA-698v-4r3x-3vcv lists affected ranges: npm launch-editor >=0 =8.3.0 =8.2.0 =8.0.0 =7.0.0 =0 =0 <1.1.0 (fixed))

Commands are suggestions: review each one before running it.