MediumCVE-2026-112944

    Vite Launch-editor: Argument Injection (CVE-2026-112944)

    Published Last modified Sources: OSV, CVE.org, Hersteller

    What is affected, what to do

    Update Vite Launch-editor to version 2.14.2, Vitejs to version 6.4.4, Vite-plus to version 1.1.0.

    Affected
    • Vite Launch-editor lt *..2.14.2
    • Vitejs gte 7.0.0, < 7.3.7..*
    • Vitejs lt *..6.4.4
    • Vite-plus lt *..1.1.0
    Fixed in
    • Vite Launch-editor 2.14.2
    • Vitejs 6.4.4
    • Vite-plus 1.1.0

    Not sure whether and how you are affected? Ask a question about this vulnerability

    Metrics

    6.3

    Priority

    XIEM Effective CVSS: highest available CVSS rating from NVD and vendor data.

    Source: Vendor (CNA), CVSS v4

    6.3

    CVSS v4

    Severity Medium on the scale from 0 to 10.

    Source: OSV, CVE.org, Hersteller

    0.7 %

    EPSS score

    Low — model estimates < 1% exploitation likelihood.

    Source: FIRST EPSS, percentile 53.3

    Show all metrics
    Severity
    Medium
    Priority (0–325)

    The priority score is a consolidated metric that condenses several individual signals into a single, action-guiding ranking: technical severity (CVSS), exploitation likelihood (EPSS), known-exploited status (KEV) and the context of the affected asset. The aim is to answer the only truly important question in vulnerability management: what first?

    Read in glossary
    84.26 Methodology
    Exploit maturity

    An exploit is code or a technique that specifically uses a concrete vulnerability to force unintended behaviour — such as executing code or escalating privileges. It is the tool that turns a theoretical flaw into a practical attack.

    Read in glossary
    no public PoC known
    XIEM Effective CVSS

    XIEM® is the tiered managed-security operating model from NEOSEC and a registered trademark of NEOSEC GmbH. It extends classic SIEM — the central collection, normalisation and correlation of security-relevant events — with endpoint forensics, network visibility and deception technology, and consolidates them into three building tiers: Sentry, Orchestrate and Command.

    Read in glossary
    6.3 Methodology
    CVSS v4

    CVSS is the globally established, open standard for assessing the technical severity of a vulnerability on a scale from 0 to 10. It describes how easily a flaw can be exploited and what damage it can cause — but not how likely its actual exploitation is. CVSS and the complementary EPSS deliberately answer different questions.

    Read in glossary
    6.3
    EPSS score

    The EPSS score is the absolute model output for an individual vulnerability: the estimated probability of real-world exploitation within the next 30 days, expressed as a value between 0 and 1 (i.e. 0 % to 100 %). A score of 0.42 means „the model estimates a 42 % chance of real-world exploitation within 30 days“.

    Read in glossary
    0.7 %
    Low — model estimates < 1% exploitation likelihood.
    EPSS percentile

    The EPSS percentile is the relative position of a vulnerability within all EPSS-scored CVEs, expressed as a value between 0 and 1. A percentile of 0.90 means „this CVE has a higher EPSS score than 90 % of all other scored CVEs“. Unlike the EPSS score, it is not a probability — but a positioning within a ranking.

    Read in glossary
    53.3
    High — this CVE ranks above the median of all CVEs scored today (rank ≥ 36%).
    KEV status

    The KEV catalogue is a list maintained by the US authority CISA of vulnerabilities for which active exploitation in the wild has been confirmed. It answers not the question „how severe?“ but „is it already being attacked?“ — thereby sharply prioritising patching.

    Read in glossary
    —
    Published
    CISA assessment (SSVC)
    Exploitation: none known · not automatable · Technical impact: partial
    Source: CISA Vulnrichment, as of 20 October 2026
    CWE

    CWE is a catalogue of typical weakness types in software and hardware — such as flawed input validation, unsafe memory handling or poor authentication. Where a CVE names a concrete vulnerability in a concrete product, a CWE describes the underlying class of defect.

    Read in glossary
    CWE-88

    Detection rules

    No NEOSEC detection rule is available for this vulnerability yet.

    Classification under NIS2 and CRA

    Rule-based classification from exploitation status and severity. It does not replace a case-by-case assessment.

    NIS2

    NIS2 is EU Directive (EU) 2022/2555 to raise the level of cybersecurity across the Union. It substantially broadens obligations compared with the first NIS directive: more sectors, mandatory risk management, staged reporting duties and personal accountability of senior management.

    Read in glossary
    Handle the vulnerability in regular vulnerability handling under Art. 21(2)(e) NIS2.
    CRA

    The CRA is EU Regulation (EU) 2024/2847 setting horizontal cybersecurity requirements for „products with digital elements“ — from industrial controllers and software to connected consumer devices. For the first time manufacturers must ensure security across the entire product lifecycle, handle vulnerabilities and provide security updates.

    Read in glossary
    From 11.12.2027, Annex I Part II CRA requires manufacturers of affected products with digital elements to handle vulnerabilities without delay and provide security updates.
    ISO/IEC 27001

    ISO/IEC 27001 is the internationally leading standard for an information security management system (ISMS). It describes a risk-based, process-oriented framework to systematically plan, implement, review and improve information security.

    Read in glossary
    Control A.8.8, management of technical vulnerabilities: assess relevance to your systems, plan remediation and keep evidence.

    Description

    Summary

    launch-editor forwarded file paths directly to editors without sanitization. If a path resembles a CLI flag, editors like Vim may interpret it as a command, potentially causing unintended file overwrites or command execution.

    Impact

    Direct launch-editor users

    Only apps that match all of the following conditions are affected:

    • The attacker is able to create a file system entry (e.g. a file or directory) starting with + or - in the working directory
    • The user uses or the app specifies any of the following editors:
      • Vim (including gVim)
      • MacVim
      • Emacs (including Emacsclient)
      • Notepad++ (only if using a plugin exposing dangerous operations via plugin messages)
    • The first argument of launchEditor can start with + or - or the user is using WSL

    launch-editor-middleware users

    Only apps that match the following conditions are affected:

    • The attacker is able to create a file system entry (e.g. a file or directory) starting with + or - in the working directory
    • The user uses or the app specifies any of the following editors:
      • Vim (including gVim)
      • MacVim
      • Emacs (including Emacsclient)
      • Notepad++ (only if using a plugin exposing dangerous operations via plugin messages)
    • launch-editor older than v2.2.0 is used, or the user is using WSL

    Vite users

    Only apps that match the following conditions are affected:

    • The attacker is able to create a file system entry (e.g. a file or directory) starting with + or - in the working directory
    • The user uses or the app specifies any of the following editors:
      • Vim (including gVim)
      • MacVim
      • Emacs (including Emacsclient)
      • Notepad++ (only if using a plugin exposing dangerous operations via plugin messages)
    • The user is using WSL

    Details

    launchEditor(file) function passes the file name as-is to the editor if the file with that file name exists. If the file name starts with - (also + for Vim), the editor treats them as flags rather than positional arguments. For example, Vim treats arguments starting with + as an Ex command. As a result, an existing relative directory such as:

    +call writefile(["SAFE_MARKER"],"LAUNCH_EDITOR_MARKER")|qa!

    is not treated as a filename when passed to Vim. Vim executes the embedded Ex command.

    The following editor has a potentially destructive operation exposed to the CLI arguments:

    • Vim (including gVim)
    • MacVim
    • Emacs (including Emacsclient)
    • Notepad++ (only if using a plugin exposing dangerous operations via plugin messages)

    launch-editor-middleware v2.2.0+ converts the passed file path to an absolute path so those are not affected as long as the user is not using WSL. For WSL, launch-editor converts the paths to relative paths internally, so those are still affected.

    Vite 2.0.0+ uses launch-editor-middleware v2.2.0+ so the WSL users are only affected.

    Source: OSV (Open Source Vulnerabilities), NVD (NIST), GitHub Security Advisories, cvelistv5

    Affected products

    The following versions are affected. Older releases of the same product line are also vulnerable unless stated otherwise.

    Affected products
    Affected versionsFixed in
    vitejslaunch-editor
    • < 2.14.2
    • 2.14.2
    vitejsvite
    • < 6.4.4
    • ≥ 7.0.0, < 7.3.7
    • 6.4.4
    • —
    vitejsvite-plus
    • < 1.1.0
    • 1.1.0
    npmlaunch-editor
    • <= 2.14.1
    • —
    • 2.14.2
    • 2.14.2
    npmvite
    • >= 7.0.0, <= 7.3.6
    • 7.0.0
    • <= 6.4.3
    • >= 8.3.0, <= 8.3.2
    • >= 8.2.0, <= 8.2.3
    • —
    • 8.2.0
    • 8.0.0
    • 8.3.0
    • >= 8.0.0, <= 8.1.5
    • 7.3.7
    • 7.3.7
    • 6.4.4
    • 8.3.3
    • 8.2.4
    • 6.4.4
    • 8.2.4
    • 8.1.6
    • 8.3.3
    • 8.1.6
    npmvite-plus
    • <= 1.0.0
    • —
    • 1.1.0
    • 1.1.0

    Vendors and products

    Weakness classes (CWE)

    • CWE-88Improper Neutralization of Argument Delimiters in a Command ('Argument Injection')

      Base

      The product constructs a string for a command to be executed by a separate component in another control sphere, but it does not properly delimit the intended arguments, options, or switches within that command string.

      Entry at MITRE CWE-88

    References & sources

    • github.comvitejs/launch-editor/commit/f6e6701bb1f16f2dd242b321374f1b6cca6…x_refsource_MISC, web
    • github.comvitejs/launch-editor/pull/156x_refsource_MISC, web
    • github.comvitejs/launch-editor/releases/tag/v2.14.2x_refsource_MISC, web
    • github.comvitejs/launch-editor/security/advisories/GHSA-r825-w8mm-5pxwx_refsource_CONFIRM, web
    • NVD (NIST)vuln/detail/CVE-2026-112944advisory
    • github.comvitejs/launch-editorpackage

    Changes to this CVE

    Who changed this CVE and when: NVD (analysis, affected products, CVSS), the CVE publisher (CNA) and additional providers such as CISA (ADP).

    1. Record modifiedCISA ADP

      CISA assessment (SSVC): exploitation: none known, automatable: no

      Show the original change
      Individual changes of this event as published by NVD
      TypeActionBeforeAfter
      SSVC assessmentadded
      —
      {"id":"CVE-2026-112944","role":"CISA Coordinator","options":[{"exploitation":"none"},{"automatable":"no"},{"technicalImpact":"partial"}],"version":"2.0.3","timestamp":"2026-10-20T15:22:50.878612Z"}

      Source identifier: 134c704f-9b21-4f2e-91b3-4a467353bcc0

    2. ReceivedGitHub

      CVSS V4.0: AV:N/AC:L/AT:P/PR:N/UI:N/VC:L/VI:L/VA:L/SC:N/SI:N/SA:N

      Weakness type: CWE-88

      Description added or changed

      Show 8 original changes
      Individual changes of this event as published by NVD
      TypeActionBeforeAfter
      Descriptionadded
      —
      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.
      CVSSadded
      —
      AV:N/AC:L/AT:P/PR:N/UI:N/VC:L/VI:L/VA:L/SC:N/SI:N/SA:N/E:X/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:X
      Weakness type (CWE)added
      —
      CWE-88
      Affected versions (publisher)added
      —
      New affected value received. <a href="https://github.com/CVEProject/cvelistV5/blob/main/cves/2026/112xxx/CVE-2026-112944.json">CVE-2026-112944</a>
      Referenceadded
      —
      https://github.com/vitejs/launch-editor/commit/f6e6701bb1f16f2dd242b321374f1b6cca6eb6d4
      Referenceadded
      —
      https://github.com/vitejs/launch-editor/pull/156
      Referenceadded
      —
      https://github.com/vitejs/launch-editor/releases/tag/v2.14.2
      Referenceadded
      —
      https://github.com/vitejs/launch-editor/security/advisories/GHSA-r825-w8mm-5pxw

      Source identifier: security-advisories@github.com

    Embed badge

    Show the severity and KEV status of this vulnerability on your site – with a link back here. The image is updated hourly.

    Badge preview for CVE-2026-112944
    <a href="https://intel.neosec.eu/en/cve/CVE-2026-112944"><img src="https://intel.neosec.eu/badge/cve/CVE-2026-112944.svg?lang=en" alt="CVE-2026-112944 – NEOSEC Intel" height="20"></a>