# CVE-2026-105420: Path Traversal in Wing WFTP Server leading to Remote Code Execution


- **Severity:** Critical 9.4 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:H/UI:N/VC:H/VI:H/VA:H/SC:H/SI:H/SA:H`)
- **Exploited in the wild:** Not known
- **Fix available:** No
- **Published:** 28 Oct 2026
- **Updated:** 28 Oct 2026
- **Also known as:** GHSA-fj2q-v6ch-v3mg

## What is CVE-2026-105420?

CVE-2026-105420 is a critical vulnerability in Wing FTP Server, published on 28 Oct 2026. 

### Official description

Wing FTP Server does not verify user's base folder. An attacker with admin privileges can add user directories via scripts, allowing the added directories to escape the base folder. This allows the attacker to write files on the system and can lead to remote code execution with process owner privileges.Critically, since the installation guide mentions running the command with `sudo`, the files are created as “root.”

This issue was fixed in version 8.2.6.

Weakness: CWE-22 (Improper Limitation of a Pathname to a Restricted Directory)

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


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

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

## Is CVE-2026-105420 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-105420 is a critical vulnerability in Wing FTP Server, published on 28 Oct 2026. 
Exploitation: There is no known exploitation of CVE-2026-105420 in the wild and no public exploit code.

Affected product: Wing FTP Server. 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-105420/ (Markdown: https://insights.sbomify.com/CVE-2026-105420/index.md)
```

## Sources

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

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