CVE-2026-112944

MEDIUMPre-NVD 6.36.3
EchelonGraph scoreMEDIUM confidence

“—” beside the score: it is equal to the CVSS score beside it.

This medium-severity CVE scores 6.3 under a secondary CVSS source (NVD's own analysis pending). EPSS exploit probability: 0.7% (53rd percentile of EPSS-scored CVEs). No GitHub Security Advisory CVSS is on record for this CVE.

Triggered by: Headline CVSS from a secondary CVSS source
Sources: EPSS, a secondary CVSS source
Trending — 4 sources updated this week

Also known asEUVD-2026-105045 (ENISA EUVD) · GHSA-r825-w8mm-5pxw (GitHub Security Advisories)Source: ENISA EUVD

6.3EG
EchelonGraph verdictMonitorRemediate within your standard update timelines (the SSVC decision on this page).
  • Lower severity and no public exploit yet
CISA-KEV: Not listedEPSS PROB: 0.7%CVSS: 6.3Exploit: None knownExposed services: Not assessed

A fix is available — apply it.

launch-editor allows users to open files with line numbers in editor from Node.js. Prior to 2.14.2, when an attacker can create a filesystem entry beginning with plus or minus in the working directory, an affected editor is selected, and the path can remain relative or is converted to a relative WSL path, launchEditor forwards the path without forcing it to be interpreted as a positional filename. Editor option parsing then treats the attacker-controlled filename as a command-line flag, which can cause unintended file overwrite or arbitrary command execution by the selected editor. The affected editors are Vim and gVim, MacVim, Emacs and Emacsclient, and Notepad++ when a plugin exposes dangerous operations; WSL path conversion keeps Vite and newer middleware callers exposed. This issue is fixed in version 2.14.2.

CVSS v3
6.3
EG Score
6.3MEDIUMmedium confidence
EG Risk
29
EG Risk 29/100

EG Risk is EchelonGraph's 0–100 priority score. It fuses impact severity (EG Severity, the CVSS base score, never the KEV-floored or EPSS-lifted EG Score) with real-world exploitation and automatability, under weights EchelonGraph set by hand, so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner.

How it’s computed (value × EchelonGraph’s weight)
Severity63% × 45%
Impact severity (EG Severity): CVSS 6.3 of 10. Never the KEV-floored or EPSS-lifted EG Score.
Exploitation0.7% × 40%
FIRST EPSS: the 30-day exploitation probability when EchelonGraph scored this CVE.
Automatability0% × 15%
CISA's SSVC Automatable value: no (Vulnrichment).
SSVC (CISA's decision table, applied by EchelonGraph): Track at every mission impact level.
Exploitation none (CISA Vulnrichment) · Automatable no (CISA Vulnrichment) · Technical impact partial (CISA Vulnrichment). All three are CISA's SSVC values (Vulnrichment). EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE.
Action: A fix is available. Apply it within your standard update timelines.
EPSS PROB
0.7%
EPSS %ILE
53rd
KEV
Not listed

What the EG score is made of (scorer v4.0: the three questions the 0–10 score mixes, published apart · methodology)

The EG score (6.3): severity, escalated by confirmed exploitation. This CVE's 6.3 is its impact severity (EG Severity), not escalated.

EG Severity
6.3 MEDIUMCVSS-B, impact only: no KEV listing, EPSS or EG-KEV tier raises it.a secondary CVSS source · CVSS v3.0 or v3.1
EG Likelihood
0.7% within 30 daysSource: FIRST EPSS (model v2026.06.15, score date 2026-10-31). FIRST's exploitation probability, not an EchelonGraph model.
Confirmed exploitation
None on record (CISA KEV, EG-KEV Tier 1)Reported apart from the likelihood: an observed fact, not a probability.
EG Priority
SSVC Track at medium mission impactTrack at every mission impact level.CISA BOD 26-04: 60 days if the affected system is publicly exposed; Fix on system upgrade if it is not.Each input and its source, and whom BOD 26-04 binds: the SSVC and BOD 26-04 blocks below.

SSVC (CISA's decision table, applied by EchelonGraph)Track at every mission impact level.

A fix is available. Apply it within your standard update timelines.

Exploitation none (CISA Vulnrichment) · Automatable no (CISA Vulnrichment) · Technical impact partial (CISA Vulnrichment). All three are CISA's SSVC values (Vulnrichment). EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE. Mission impact is CISA's Mission & Well-being decision point, and only you can judge it. CISA's table makes it high when Mission Prevalence is Essential — the vulnerable component "directly provides capabilities that constitute at least one MEF for at least one entity" (MEF: mission essential function) — or when Public Well-Being Impact is Irreversible: "multiple fatalities are likely", the cyber-physical system "is likely lost or destroyed", "extreme or serious externalities" are imposed on other parties, or social systems such as elections or the financial grid "are destabilized and potentially collapse". CISA's decision table

BOD 26-04 (CISA's remediation timeline, Table 1)60 days if the affected system is publicly exposed; Fix on system upgrade if it is not.

The score's inputs: In CISA KEV no (CISA's KEV catalog) · Automatable no (CISA Vulnrichment) · Technical impact partial (CISA Vulnrichment). Whether your system is publicly exposed is yours to answer. BOD 26-04 binds US Federal Civilian Executive Branch agencies; for anyone else it is CISA's published timeline, a reference rather than an obligation. The directive · how EchelonGraph applies it

Published

October 20, 2026

Last Modified

October 20, 2026

Advisory Details (3)

Auto-updated Oct 20, 2026
Patch available. Sources: github, github_pr, github_commit.
GitHub commit

commit f6e6701bb1f1 (vitejs/launch-editor)

Fix landed in vitejs/launch-editor commit f6e6701bb1f1 — awaiting tagged release

https://github.com/vitejs/launch-editor/commit/f6e6701bb1f16f2dd242b321374f1b6cca6eb6d4
GitHub pull request

fix: ensure filenames passed to editors are not considered as flags

Fix merged in vitejs/launch-editor PR #156 on 2026-10-06 — awaiting tagged release

https://github.com/vitejs/launch-editor/pull/156
GitHub advisoryMentions a patch (unverified)

Editor CLI flag misinterpretation causing arbitrary command execution for some editors · Advisory · vitejs/launch-editor · GitHub

https://github.com/vitejs/launch-editor/security/advisories/GHSA-r825-w8mm-5pxw

Vendor Advisories for CVE-2026-112944(1)

These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.

Patch Availability(7)

Vendor / EcosystemFix (by version range) / PatchReleasedSource
npmlaunch-editor @ 2.14.2 (fixes <= 2.14.1)—ghsa
npmvite @ 8.3.3 (fixes >= 8.3.0, <= 8.3.2)—ghsa
npmvite @ 8.2.4 (fixes >= 8.2.0, <= 8.2.3)—ghsa
npmvite @ 8.1.6 (fixes >= 8.0.0, <= 8.1.5)—ghsa
npmvite @ 7.3.7 (fixes >= 7.0.0, <= 7.3.6)—ghsa
npmvite @ 6.4.4 (fixes <= 6.4.3)—ghsa
npmvite-plus @ 1.1.0 (fixes <= 1.0.0)—ghsa

Patches are aggregated from vendor advisories (Red Hat, Microsoft, Cisco, GitHub) and package ecosystems (OSV, GHSA). Multiple rows for the same upstream release have been deduplicated.

Affected Packages

(3 across 1 ecosystem)
npm(3)
PackageVulnerable rangeFix by version rangeDependents
launch-editor—
  • every version up to 2.14.2: fixed in 2.14.2
—
vite—
  • 8.3.0 up to 8.3.3: fixed in 8.3.3
  • 8.2.0 up to 8.2.4: fixed in 8.2.4
  • 8.0.0 up to 8.1.6: fixed in 8.1.6
  • 7.0.0 up to 7.3.7: fixed in 7.3.7
  • every version up to 6.4.4: fixed in 6.4.4
—
vite-plus—
  • every version up to 1.1.0: fixed in 1.1.0
—

Weakness Classification(1)

MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.

Data Freshness Timeline

(refreshed 11× in last 7d / 21× in last 30d)

Each row is a time one of our pipelines fetched, updated or re-scored this CVE. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. An arrow marks a change the record states ("CVSS v3 → 9.1"); EPSS and GHSA rows show the values recorded at that time, not what changed (EPSS values are rounded; hover one for the exact figures). Most recent first.

  1. 2026-11-01 16:33 UTCEPSS rescoreEPSS 0.7% · 53rd percentile
  2. 2026-11-01 07:59 UTCGHSA enrichmentGHSA-r825-w8mm-5pxw · GitHub severity MODERATE
  3. 2026-11-01 07:59 UTCEG score recompute
  4. 2026-10-31 16:32 UTCEPSS rescoreEPSS 0.7% · 53rd percentile
  5. 2026-10-30 16:33 UTCEPSS rescoreEPSS 0.7% · 53rd percentile
  6. 2026-10-29 16:32 UTCEPSS rescoreEPSS 0.7% · 53rd percentile
  7. 2026-10-29 15:13 UTCEG score recompute
  8. 2026-10-28 17:25 UTCOSV refresh
  9. 2026-10-28 16:31 UTCEPSS rescoreEPSS 0.7% · 53rd percentile
  10. 2026-10-27 16:31 UTCEPSS rescoreEPSS 0.7% · 53rd percentile
  11. 2026-10-26 16:30 UTCEPSS rescoreEPSS 0.7% · 53rd percentile
  12. 2026-10-25 16:32 UTCEPSS rescoreEPSS 0.7% · 53rd percentile
  13. 2026-10-25 14:51 UTCEG score recompute
  14. 2026-10-24 16:32 UTCEPSS rescoreEPSS 0.7% · 52nd percentile
  15. 2026-10-23 16:31 UTCEPSS rescoreEPSS 0.7% · 52nd percentile
  16. 2026-10-22 16:33 UTCEPSS rescoreEPSS 0.7% · 52nd percentile
  17. 2026-10-21 16:32 UTCEPSS rescoreEPSS 0.7% · 52nd percentile
  18. 2026-10-20 16:29 UTCEG score recompute
  19. 2026-10-20 15:27 UTCEG score recompute
  20. 2026-10-20 15:04 UTCEG score recomputeFirst assessed: 6.3 MEDIUM
  21. 2026-10-20 15:01 UTCMITRE cvelistV5first tracked

Related CVEs(same product + same CWE)

Frequently asked(5)

What is CVE-2026-112944?
CVE-2026-112944 is a medium-severity vulnerability; its CVE record was published on October 20, 2026. launch-editor allows users to open files with line numbers in editor from Node.js. Prior to 2.14.2, when an attacker can create a filesystem entry beginning with plus or minus in the working directory, an affected editor is selected, and the path can remain relative or is converted to a relative…
When was the CVE record for CVE-2026-112944 published?
The CVE record for CVE-2026-112944 was published on October 20, 2026. That is the record's publication date; the vulnerability itself may have been made public earlier. EchelonGraph's copy of the record carries a last-modified date of October 20, 2026; the record at its source may have been updated since.
Is CVE-2026-112944 actively exploited?
CVE-2026-112944 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.7% probability of exploitation in the next 30 days (53rd percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2026-112944?
CVE-2026-112944 has a CVSS base score of 6.3 (a secondary CVSS source that NVD displays; NVD's own analysis pending).
How do I remediate CVE-2026-112944?
A fix for CVE-2026-112944 is available: update to the fixed version the vendor names in its advisory. The vendor advisories EchelonGraph has for CVE-2026-112944 are linked in the Vendor Advisories panel on this page.

Dependency Blast Radius

See which npm, PyPI, Go, and Maven packages are affected by CVE-2026-112944

Explore →

Is Your Infrastructure Affected by CVE-2026-112944?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.

Book a Demo →Browse All CVEs