GHSA-698v-4r3x-3vcv

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

Medium highest severity reported · also known as CVE-2026-112943

4
catalog tools match this advisory
0
ship the vulnerable code in their release binary (Go tools analyzed with govulncheck)
No
in the CISA KEV catalog
0.4%
EPSS for CVE-2026-112943, percentile 36

Catalog tools matching GHSA-698v-4r3x-3vcv

ToolVersion scannedPackageFixed inReleased binaryDeclared in or found inDispute
infisical
Secret Management
v0.167.4vite@7.3.2
npm
7.3.7not analyzedupgrade-impact/package-lock.jsonDispute
infisical
Secret Management
v0.167.4vite@7.3.6
npm
7.3.7not analyzedbackend/package-lock.jsonDispute
infisical
Secret Management
v0.167.4vite@8.2.2
npm
8.2.4not analyzedfrontend/package-lock.jsonDispute
KubeStellar Console
Kubernetes Security
v0.3.42vite@8.3.0
npm
8.3.3not analyzedweb/package-lock.jsonDispute
prowler
Cloud Security
5.47.0vite@7.3.5
npm
7.3.7not analyzedui/pnpm-lock.yamlDispute
cloudsplaining
Cloud Security
0.9.1launch-editor@2.13.1
npm
2.14.2not analyzedpackage-lock.jsonDispute

Vulnerabilities are known advisories that Grype matches against the dependencies declared in each project's release source (manifests and lockfiles, including development and build dependencies). A match does not mean the tool is exploitable: the vulnerable code may be unused, test-only, or not shipped in the released binary. KEV: listed in the CISA Known Exploited Vulnerabilities catalog. EPSS: FIRST's estimated probability of exploitation in the next 30 days. Both describe the vulnerability in general, not its exploitability through this tool; a match in a workflow file refers to a GitHub Action, not to shipped code. Released binary is only analyzed for Go tools with a Linux release binary; other tools show not analyzed.

Advisory sources

GitHub advisory GHSA-698v-4r3x-3vcv · NVD CVE-2026-112943 · OSV GHSA-698v-4r3x-3vcv

Grype data sources: https://github.com/advisories/GHSA-698v-4r3x-3vcv