CVE-2026-119364 ProFTPD through 1.3.9e and 1.3.10rc4 mod_copy Symlink Following Write Bypass
Medium 6.0
Published
Updated
Check this codebase for CVE-2026-119364 and fix it if it is affected.
What it is: CVE-2026-119364 is a medium-severity vulnerability in ProFTPD, published on 30 Oct 2026.
Exploitation: There is no known exploitation of CVE-2026-119364 in the wild and no public exploit code.
Affected product: ProFTPD. 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-119364/ (Markdown: https://insights.sbomify.com/CVE-2026-119364/index.md)
- Exploited in the wild
- Not known
- Fix
- Available
What is CVE-2026-119364?
CVE-2026-119364 is a medium-severity vulnerability in ProFTPD, published on 30 Oct 2026.
Official description
ProFTPD through 1.3.9e and 1.3.10rc1 through 1.3.10rc4 contains a link-following vulnerability in mod_copy that allows authenticated FTP users to bypass Limit WRITE restrictions via symlinks. Attackers can place a symlink in a writable directory and use SITE COPY or SITE CPTO to overwrite files in write-denied locations.
Weakness: CWE-59
Which versions are affected by CVE-2026-119364?
How do I fix CVE-2026-119364?
Upgrade to a fixed version.
Is CVE-2026-119364 being exploited?
There is no known exploitation of CVE-2026-119364 in the wild and no public exploit code.
Sources
Also known as ALPINE-CVE-2026-119364, DEBIAN-CVE-2026-119364, GHSA-97rq-x35j-mmf5, UBUNTU-CVE-2026-119364.