# CVE-2026-100230: Path traversal in Input Leap

> Attackers can achieve code execution via directory traversal in Input Leap when drag-and-drop is enabled on Windows or macOS.

- **Severity:** Medium 5.3 (`CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:U/C:N/I:H/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 25 Sep 2026
- **Updated:** 25 Sep 2026
- **Also known as:** GHSA-m68w-q97c-3w3j

## What is CVE-2026-100230?

CVE-2026-100230 is a medium-severity path traversal vulnerability in input-leap Input Leap, published on 25 Sep 2026. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

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.

Weakness: CWE-180 (Incorrect Behavior Order: Validate Before Canonicalize)

## Which versions are affected by CVE-2026-100230?


## How do I fix CVE-2026-100230?

No fix has been published for CVE-2026-100230 yet. Limit exposure of the affected software until one is available.

## Is CVE-2026-100230 being exploited?

There is no known exploitation of CVE-2026-100230 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-100230 and fix it if it is affected.

What it is: CVE-2026-100230 is a medium-severity path traversal vulnerability in input-leap Input Leap, published on 25 Sep 2026. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2026-100230 in the wild and no public exploit code.

Affected product: input-leap Input Leap. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-100230/ (Markdown: https://insights.sbomify.com/CVE-2026-100230/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-100230
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-100230
- OSV: https://osv.dev/vulnerability/CVE-2026-100230

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-100230/
Summaries are generated and may contain mistakes; the official description above is the record.