Skip to main content

Input Leap EUVDEUVD-2026-87130

| CVE-2026-100230 MEDIUM
Incorrect Behavior Order: Validate Before Canonicalize (CWE-180)
2026-09-25 mitre GHSA-m68w-q97c-3w3j
5.3
CVSS 3.1 · Vendor: mitre
View

Attack ChainAIDerived

Hypothetical attack flow derived from CVE metadata – not a confirmed exploit chain

  1. Access
    Reach Input Leap peer with drag-drop enabled
  2. Delivery
    Send crafted DDRG message
  3. Exploit
    Abuse / vs \ path traversal
  4. Execution
    Write file to startup directory
  5. Impact
    Code executes at next login

Vulnerability Assessment

Weakness
CWE
OWASP Top 10:2025
A05:2025 - Injection
ASVS 5.0
V1 - Encoding and Sanitization Leading special element handling
Exploitation Conditions

Requires the non-default --enable-drag-drop command-line option to be active on an Input Leap peer running Windows or macOS (Linux/default configs are not stated as affected). The attacker must be able to deliver a DDRG drag-and-drop protocol message to the victim - i.e. act as a connected/authorized peer or otherwise inject on the connection (PR:L). Successful code execution further requires the traversal-written file to land in a startup directory and the victim to subsequently log in or reboot for the payload to run. Limiting factors: non-default feature must be explicitly enabled, only Windows/macOS targets, delayed execution dependent on next login, and no confirmed unauthenticated path in the default deployment.

Impact

This is a high-CVSS-ceiling-but-low-real-risk issue in practice. The provided CVSS 3.1 vector (AV:N/AC:H/PR:L/UI:N/S:U/C:N/I:H/A:N, base 5.3) already tempers severity via AC:H and the constrained impact, and I concur the practical priority is modest. Key gating signals: exploitation requires the NON-DEFAULT --enable-drag-drop option to be enabled on a Windows or macOS peer, so the vast majority of Input Leap deployments are not exposed. No EPSS score, no CISA KEV listing, and no public POC are present in the supplied data, so this is 'no public exploit identified at time of analysis' - no evidence of active exploitation or automatable weaponization. That said, the outcome is genuine directory-traversal-to-code-execution (write into a startup directory → code runs at next login), which is more serious than the C:N/I:H/A:N vector suggests; a defensible reassessment treats the resultant code execution as full user-context compromise (C:H/I:H/A:H) rather than integrity-only. The reference to CVE-2021-42072 (Barrier client authentication bypass) is relevant context: if the connection is unauthenticated in a given deployment, the PR:L assumption weakens and network reachability matters more. Net: real but conditional - a targeted rather than mass-exploitation concern.

Exploit ScenarioDerived

An attacker who can present as a connected Input Leap peer (or intercept/inject on the connection) to a victim running the non-default --enable-drag-drop option on Windows or macOS sends a crafted DDRG drag-and-drop message. By abusing the mishandled '/' versus '\' path separator, the payload traverses directories and writes an attacker-controlled file into a user startup directory, which executes automatically at the victim's next login. No public exploit code is identified at time of analysis.

This Month Plan within 30 days. Why: MEDIUM severity (CVSS 4.0-6.9).
No patch listed yet 0.7% exploitation probability (EPSS)

Get an e-mail when this CVE is exploited, patched or re-scored. Free account.

Alert me

AnalysisAIv1 – Sep 25, 2026

Directory traversal in Input Leap through 3.0.3 allows a connected peer to send a crafted DDRG drag-and-drop protocol message that escapes the intended drop directory on Windows and macOS, writing attacker-controlled files anywhere the Input Leap process has write access - including startup directories, which yields code execution the next time the victim logs in or reboots. The flaw only manifests when the non-default --enable-drag-drop option is explicitly enabled and only against Windows or macOS targets; delivery requires the attacker to act as an authorized/connected peer (PR:L per the assessed vector, which the vendor vector agrees on). No public exploit code or confirmed active exploitation was identified at time of analysis, and while the vendor score is 5.3 (C:N/I:H/A:N), our independent assessment raises the impact ceiling to C:H/I:H/A:H - this is a high-ceiling but low-risk-in-practice issue because of the non-default prerequisite, the platform restriction, and the delayed, login-dependent execution path.

RemediationAI

No vendor-released fixed version is identified in the available data, so the primary action is to eliminate the vulnerable configuration: remove the non-default --enable-drag-drop option from the Input Leap client and server command lines (or from the service/launch configuration) on all Windows and macOS peers, then restart the peer - this completely removes the DDRG message handling path and is the highest-confidence mitigation, at the cost of losing drag-and-drop file transfer between machines. Administrators should monitor https://github.com/input-leap/input-leap/releases and the project advisories for a patched release and upgrade as soon as one is published. As compensating controls, restrict which hosts can connect to the Input Leap peer: require TLS and password authentication via SecureSocket and limit accepted peers to known, trusted machines, which raises the PR:L prerequisite to a trusted-user requirement but does not help if any authorized peer is itself compromised. Run the Input Leap process under a least-privileged account whose writable locations exclude per-user startup directories, accepting that this is hard to guarantee on Windows/macOS since user profile startup folders are typically writable by that user. Finally, block the configured Input Leap listening port from untrusted network segments and avoid exposing the peer directly to the internet; the trade-off is reduced flexibility for remote or multi-network use. Related advisories for the Deskflow fork and the historical Barrier issue CVE-2021-42072 are worth reviewing for additional hardening guidance.

Affected VersionsENISA

Input Leap 0 ≤3.0.3

Affected Packages

euvd input_leap no fix

Source: OSV (Open Source Vulnerabilities)

Affects your stack

Affects 1 package in euvd

Checking this CVE against your own stacks and servers is part of the Basic plan and up.

Technical ContextAI · show details

The root cause class is CWE-180 (Incorrect Behavior Order: Validate Before Canonicalize). Input Leap is the community fork of Barrier/Synergy, a KVM-style remote input sharing tool where a client and server exchange input events, clipboard data, and optional drag-and-drop file transfers over an authenticated socket (see SecureSocket.cpp). When the non-default --enable-drag-drop option is active, the peer parses DDRG drag-and-drop messages in src/lib/inputleap/DragInformation.cpp and resolves the drop target in src/lib/inputleap/DropHelper.cpp. On Windows and macOS the backslash and forward slash are both treated as path separators, but the traversal validation is applied before the path is canonicalized, so a filename constructed with the alternate separator convention bypasses the '..' checks and is then resolved by the OS as a genuine parent-directory reference. Because the same handler writes the received file to the resolved location, the attacker can drop content into a per-user startup directory (for example the Windows Startup folder or a macOS LoginItems/LaunchAgents-adjacent path) and obtain code execution at next login. The affected product is identified by CPE cpe:2.3:a:input-leap:input_leap:*:*:*:*:*:*:*:* (a wildcard range; the description bounds affected releases at 3.0.3). This bug is closely related to the Barrier drag-and-drop traversal CVE-2021-42072 cited in the references, and to advisories published for the related Deskflow project, indicating a shared lineage of drag-and-drop path-handling defects across these forks. The references to ArgParser.cpp and Server.cpp document how the --enable-drag-drop flag and server-side message handling are configured. Real-world risk is bounded by the assessed constraints: AV:N/AC:H/PR:L/UI:N/S:U with C:H/I:H/A:H, i.e. network-reachable but requiring an authenticated/authorized peer relationship and a non-default feature toggle, and the exploit requires the victim to log in or reboot before payload execution.

Know when Input Leap gets its next vulnerability

  • Watch products and get an email when something new is published
  • Check this CVE against your own stack and servers
  • Exploit and PoC references, threat intelligence from 22 sources

No credit card · 7-day full trial

Severity by source

Vendor (mitre) PRIMARY 5.3 MEDIUM
AV:N/AC:H/PR:L/UI:N/S:U/C:N/I:H/A:N
vuln.today AI 7.5 HIGH

Non-default option plus specific path/message crafting gives AC:H; a connected peer implies PR:L; resultant startup-dir code execution runs in the user context, so C/I/A:H rather than integrity-only.

3.1 AV:N/AC:H/PR:L/UI:N/S:U/C:H/I:H/A:H
4.0 AV:N/AC:H/AT:N/PR:L/UI:N/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N
Red Hat 5.3 MEDIUM

Primary rating from Vendor (mitre).

CVSS VectorVendor: mitre

Attack Vector
Network
Attack Complexity
High
Privileges Required
Low
User Interaction
None
Scope
Unchanged
Confidentiality
None
Integrity
High
Availability
None

DescriptionCVE.org

Input Leap (aka input-leap) through 3.0.3, when the non-default --enable-drag-drop option is used on Windows or macOS, mishandles the / versus \ distinction and allows directory traversal, with resultant code execution if a file is written to a startup directory. This occurs via a DDRG message.

Threat Intelligence Overview

EPSS Score
0.7%
Top 51% exploitable
Prevalence
Low
niche open-source KVM keyboard/mouse-sharing tool, small power-user footprint
Data Quality
7 sources
Confidence: High
EUVD NVD CVE.org EPSS Vulnrichment Vendor GitHub

How this decision was reached

The engine reads each signal below and applies a fixed list of rules from top to bottom. The first rule that matches sets the recommended action – like a statement, every line is shown.

SignalValue
Severity MEDIUM
CISA KEV No
Public POC No
EPSS 0.7%
Patch available No
Active threat No
Deciding rule
MEDIUM severity (CVSS 4.0-6.9)
What every action level means
Emergency Immediate action required. Criteria: CRITICAL + in CISA KEV (actively exploited) without patch, OR CRITICAL + EPSS > 30% without patch, OR CRITICAL + active threat signals without patch.
Act Now Prioritize within 24-48h. Criteria: in KEV with patch available, OR CRITICAL + public POC, OR HIGH + EPSS > 10%, OR CRITICAL + active threat, OR any CRITICAL severity.
This Week Schedule remediation this week. Criteria: HIGH severity (CVSS 7.0-8.9). Patch within normal change window.
This Month Plan within 30 days. Criteria: MEDIUM severity (CVSS 4.0-6.9), lower exploitation probability. Include in regular patch cycle.
Monitor Track and reassess. Criteria: LOW severity (CVSS 0.1-3.9), minimal exploitation risk. No immediate action needed.

SSVC AssessmentENISA

SSVC Decision· derived
Scheduled
Exploitation
None
System Exposure· derived
Open
Automatable
No
Human Impact· derived
Medium
Technical Impact
Partial

Priority Score

27
Low Medium High Critical
KEV: 0
EPSS: +1
CVSS: +26
PoC: 0
Weaponized: 0
Threat intel: 0
Gov advisory: 0

Attack Technique

Path traversal exploits occur when applications use user-controlled input to construct file system paths without proper validation.

Remote Code Execution represents the critical moment when an attacker successfully runs arbitrary code on a target system without physical access.

Vendor StatusVendor

This site uses cookies essential for authentication and security. No tracking or analytics cookies are used. Privacy Policy