Skip to main content
Menu
CVEs

CVE

uftpd stack buffer overflow in compose_path() via long FTP path

CVE-2026-59964EUVD-2026-129190Published Updated Summary written by a model

5.9MediumCNA
Exploited
No known exploitation
Fix
Fixed in 2.16
Who is exposed
Not reported

Do first: Upgrade to a fixed version: 2.16.

Summary

A stack-based buffer overflow in uftpd, a UNIX FTP and TFTP server, lets a remote attacker with low-privilege FTP login trigger memory corruption and a reliable service crash using commands such as CWD, RETR, STOR, or LIST. Remote code execution has not been demonstrated.

Original description

uftpd is a UNIX FTP and TFTP server. Prior to 2.16, uftpd's compose_path function in src/common.c can overflow the fixed dir[PATH_MAX] stack buffer when the server runs without chroot and prepends the configured home directory to a near-PATH_MAX attacker-supplied path using memmove. A logged-in FTP client, including an anonymous or guest client where enabled, can trigger the out-of-bounds write through commands such as CWD, RETR, STOR, or LIST, causing memory corruption and a reliable service crash. Remote code execution has not been demonstrated. This issue is fixed in version 2.16.

cve.now Index

9Pcve.now Index 9 of 100 · methodology v3 · provisional
  • Exploitation?/40Unknown. No CISA SSVC exploitation rating yet
  • Exposure3/25Reachable over the network · Unknown: No advisory context yet
  • Reach?/20Unknown. No tracked technology or package matched
  • Severity5.9/10CVSS 5.9
  • No patch0/5No signal

What would change the score

  • Would score about 64 if added to CISA KEV
  • Would score about 59 if CISA's SSVC rates exploitation active
  • Would score about 28 if advisories confirm default setups are exposed

What to do

  • Upgrade to a fixed version: 2.16.

Check your systems with an agent

Paste this into a coding or ops agent. It checks your systems read-only and reports a table per asset.

Check whether my systems are affected by CVE-2026-59964 (uftpd: Stack-based buffer overflow in compose_path() via overlong FTP path), using the cve.now data below.

Rules: work read-only. Do not run exploit code, proof-of-concept scripts or scanners that send attack payloads, and do not change any configuration, package, image or deployment. Report findings only.

What cve.now has for CVE-2026-59964 (entry last updated 2026-11-18):
Affected:
- troglobit uftpd: fixed in 2.16
Fixed versions: 2.16.
Setup: unknown whether the bug needs a non-default feature or setting. Check the advisory.
CISA KEV: CVE-2026-59964 is not listed as of cve.now's last read.
This KEV status is for CVE-2026-59964 only. If you also check another CVE, look up its own KEV status; never assume it from this one.

How to check:
- Installed software: check what is actually running, not what a repo declares. Read the version from each host, container image and Kubernetes node (the binary's version output, the OS package database, image layers), and check whether the conditions above hold there. Distribution packages may carry a backported fix under an older version number; confirm against the distribution's own advisory.

Verify against the linked advisories before concluding, and cite the date you read each one:
- https://github.com/troglobit/uftpd/security/advisories/GHSA-vqhc-mmjf-972h
- https://github.com/troglobit/uftpd/commit/f5552a8c6a5f14691f51bef1f3373747259d7ac8
- https://github.com/troglobit/uftpd/releases/tag/v2.16
Do not conclude an asset is unaffected unless you checked it and the evidence covers both its version and the conditions above. If you could not check something, mark it unknown and say what is missing.

Report a table with one row per asset and these columns: Asset | Version or build | Status (affected, fixed, not applicable, unknown) | Compensating controls | Exposure (internet-facing, internal, none) | Evidence | Next action.

Entry: https://cve.now/CVE-2026-59964
For follow-up questions, use the cve.now MCP server at https://mcp.cve.now/mcp (no authentication), for example execute with name cve.get and arguments {"id": "CVE-2026-59964"}.

Timeline

  1. CVE published
  2. First seen by cve.now

Affected versions

  • troglobit uftpd

    fixed in 2.16

Evidence 5

KindSource
Vendor advisory 1Establishes: Affected and fixed versions.
AdvisoryGitHub · troglobit/uftpd · Advisory GHSA-vqhc-mmjf-972h
CVE record 2Establishes: The identifier and description.
RecordCVE List · CVE-2026-59964
RecordNVD · CVE-2026-59964
Other links 2
RepositoryGitHub · troglobit/uftpd · Commit f5552a8c
RepositoryGitHub · troglobit/uftpd · Release v2.16

Corrections

None so far.

Something wrong on this page? Report an error. Every fix is listed here.

Questions about CVE-2026-59964

Is CVE-2026-59964 being exploited?

It is not in CISA's Known Exploited Vulnerabilities catalog, and CISA's SSVC assessment does not mark exploitation as active. That does not mean it has not been attacked: vendors and researchers can report attacks before CISA lists them. No public exploit code is tracked.Source: cve.now feed data

Which versions are affected by CVE-2026-59964?

uftpd: before 2.16.Source: cve.now feed data

How do I fix CVE-2026-59964?

Upgrade to a fixed version: 2.16.Source: cve.now feed data

More CVEs