Progress WS_FTP Server: multiple vulnerabilities fixed in November 2026 service pack
France's CERT-FR reports several vulnerabilities in Progress WS_FTP Server, some of which can cause remote denial of service or compromise the confidentiality and integrity of data. Any organisation running WS_FTP Server earlier than 2025.0.5 (10.0.5) is affected.
What to do now
- Product
- Progress WS_FTP Server
- Affected versions
- WS_FTP Server versions earlier than 2025.0.5 (10.0.5)
- Fixed in
- 2025.0.5 (10.0.5), via the November 2026 service pack
- CVE
- CVE-2026-115338
On 19 November 2026, CERT-FR published advisory CERTFR-2026-AVI-1570. It covers multiple security flaws in Progress WS_FTP Server, Progress's file transfer server. The advisory is based on a Progress security bulletin dated 9 November 2026, which accompanies the November 2026 service pack.
CERT-FR says an attacker could exploit some of these flaws to cause a remote denial of service. Others could be used to compromise the confidentiality or integrity of data. The advisory does not say which vulnerability leads to which impact. It also does not state whether an attacker needs to authenticate first.
WS_FTP Server versions earlier than 2025.0.5 (10.0.5) are vulnerable. Five CVE identifiers are listed: CVE-2026-115338, CVE-2026-115339, CVE-2026-115340, CVE-2026-115341 and CVE-2026-35189.
CERT-FR points administrators to the Progress bulletin for the fixes. The advisory does not report any active exploitation of these flaws, and it does not describe a temporary workaround.
File transfer servers are frequently reachable from the internet and often handle sensitive data. Flaws like these can therefore directly affect exchanges with partners and customers. Teams running WS_FTP Server should schedule the update promptly.
What to do now
- Inventory your Progress WS_FTP Server instances and record the version running on each one.
- Apply the November 2026 service pack referenced in the Progress bulletin so that every instance runs at least version 2025.0.5 (10.0.5).
- Until the fix is deployed, and as general good practice, restrict network access to the server to the addresses that actually need it.
- After updating, review server logs for unusual logins, abnormal transfers or unexplained service crashes.