# CVE-2016-15060: PCMan FTP Server PORT buffer overflow

> Remote attackers can exploit a buffer overflow in the PORT command handler to execute arbitrary code or crash the PCMan FTP Server.

- **Severity:** Medium 6.9 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:L/VI:L/VA:L/SC:L/SI:L/SA:L/E:P`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 14 Oct 2026
- **Updated:** 20 Oct 2026
- **Also known as:** GHSA-268h-569f-j3p4

## What is CVE-2016-15060?

CVE-2016-15060 is a medium-severity memory corruption vulnerability in PCMan FTP Server, published on 14 Oct 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

A vulnerability was found in PCMan FTP Server up to 2.0.7. This affects an unknown function of the component PORT Command Handler. The manipulation results in buffer overflow. The attack can be launched remotely. The exploit has been made public and could be used.

Weakness: CWE-120 (Buffer Copy without Checking Size of Input), CWE-119 (Improper Restriction of Operations within the Bounds of a Memory Buffer)

## Which versions are affected by CVE-2016-15060?


## How do I fix CVE-2016-15060?

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

## Is CVE-2016-15060 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2016-15060 exists.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2016-15060 and fix it if it is affected.

What it is: CVE-2016-15060 is a medium-severity memory corruption vulnerability in PCMan FTP Server, published on 14 Oct 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2016-15060 exists.

Affected product: PCMan 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-2016-15060/ (Markdown: https://insights.sbomify.com/CVE-2016-15060/index.md)
```

## Sources

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

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