CVE-2026-67607: Time-of-check Time-of-use (TOCTOU) Race Condition in hfiref0x LightFTP
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.
AI Analysis
Technical Summary
CVE-2026-67607 is a TOCTOU race condition vulnerability in LightFTP up to version 2.3.1. It exists in the worker_thread_cleanup() function of ftpserv.c, where unsynchronized access to shared per-connection state occurs without the necessary mutex lock. The vulnerability is a residual issue from an incomplete fix for CVE-2024-11144; the patch in 2.3.1 only narrowed the timing window but did not add the missing lock. Exploitation involves sending a LIST command followed immediately by ABOR, causing detached thread ID reuse and unsynchronized cleanup, which destabilizes or crashes the daemon, resulting in denial of service.
Potential Impact
Successful exploitation allows remote unauthenticated attackers to destabilize or crash the LightFTP daemon, causing denial of service. There is no indication of code execution or data disclosure. The impact is limited to service availability disruption.
Mitigation Recommendations
Patch status is not yet confirmed — check the vendor advisory for current remediation guidance. The existing 2.3.1 patch does not fully fix the issue as it lacks the required mutex lock. Until an official fix is released, users should consider mitigating exposure by restricting access to the FTP service or applying any vendor-recommended workarounds once available.
CVE-2026-67607: Time-of-check Time-of-use (TOCTOU) Race Condition in hfiref0x LightFTP
Description
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.
CVSS v4.0
Score 8.2high
Affected software
hfiref0x
LightFTP
Run on your own infrastructure? Check whether these packages are installed with threat-finder — our free open-source scanner.
AI-Powered Analysis
Machine-generated threat intelligence
Technical Analysis
CVE-2026-67607 is a TOCTOU race condition vulnerability in LightFTP up to version 2.3.1. It exists in the worker_thread_cleanup() function of ftpserv.c, where unsynchronized access to shared per-connection state occurs without the necessary mutex lock. The vulnerability is a residual issue from an incomplete fix for CVE-2024-11144; the patch in 2.3.1 only narrowed the timing window but did not add the missing lock. Exploitation involves sending a LIST command followed immediately by ABOR, causing detached thread ID reuse and unsynchronized cleanup, which destabilizes or crashes the daemon, resulting in denial of service.
Potential Impact
Successful exploitation allows remote unauthenticated attackers to destabilize or crash the LightFTP daemon, causing denial of service. There is no indication of code execution or data disclosure. The impact is limited to service availability disruption.
Mitigation Recommendations
Patch status is not yet confirmed — check the vendor advisory for current remediation guidance. The existing 2.3.1 patch does not fully fix the issue as it lacks the required mutex lock. Until an official fix is released, users should consider mitigating exposure by restricting access to the FTP service or applying any vendor-recommended workarounds once available.
Technical Details
- Data Version
- 5.2
- Assigner Short Name
- VulnCheck
- Date Reserved
- 2026-07-29T21:07:39.202Z
- Cvss Version
- 4.0
- State
- PUBLISHED
Threat ID: 6a6cf74ebf32cb7a34294be2
Added to database: 07/31/2026, 19:28:14 UTC
Last enriched: 08/16/2026, 13:43:05 UTC
Last updated: 09/14/2026, 10:01:32 UTC
Views: 51
Community Reviews
0 reviewsCrowdsource mitigation strategies, share intel context, and vote on the most helpful responses. Sign in to add your voice and help keep defenders ahead.
Want to contribute mitigation steps or threat intel context? Sign in or create an account to join the community discussion.
Actions
Updates to AI analysis require Pro Console access. Upgrade inside Console → Billing.
Need more coverage?
Upgrade to Pro Console for AI refresh and higher limits.
For incident response and remediation, OffSeq services can help resolve threats faster.
Latest Threats
Check if your credentials are on the dark web
Instant breach scanning across billions of leaked records. Free tier available.