CVE-2026-67607
MediumCVSS 5.9Exploitation Probability (EPSS)
Low risk22th percentile - higher than 22% of all known CVEs
Summary
LightFTP 2.3.1 contains an incomplete fix for CVE-2024-11144, leaving a race condition in the worker_thread_cleanup() function. A remote unauthenticated attacker can send a LIST command followed by ABOR, causing daemon instability or crash (denial of service).
Risk Assessment
An attacker can remotely crash the FTP server, leading to service disruption and potential loss of file availability.
Recommendation
Apply the vendor's patch or consider using a different FTP server. Temporarily restrict FTP server access to trusted hosts only.
Other vulnerabilities in LightFTP
See all- CVE-2017-1000218Critical
LightFTP version 1.1 is vulnerable to a buffer overflow in the 'writelogentry' function resulting in denial of service or remote code execution.
- CVE-2026-70637Medium
LightFTP through 2.4 contains multiple data race vulnerabilities in ftpserv.c that allow anonymous attackers to cause undefined behavior by issuing LIST followed by ABOR commands without authentication. The control thread closes data_socket and file_fd descriptors while worker threads concurrently operate on the same fields in worker_thread_cleanup, allowing stale file descriptors to be reassigned by the OS and subsequently used by worker threads on unrelated resources, resulting in potential denial of service.
Original NVD description (English source)
LightFTP 2.3.1 contains a residual race condition vulnerability (an incomplete fix for CVE-2024-11144) in the worker_thread_cleanup() function of ftpserv.c that allows remote unauthenticated attackers to destabilize or crash the daemon by triggering unsynchronized access to shared per-connection state without holding the required mutex lock. Attackers can send a data-transfer command such as LIST followed immediately by ABOR to exploit the missing synchronization on shared context and detached thread id reuse, resulting in daemon destabilization or crash which can lead to a denial of service. The 2.3.1 patch only narrowed the timing window (an extra re-check and reordered cleanup), it never added the missing lock, so the underlying race remains.