FR
live

WS_FTP Server patches a 10.0-rated authentication flaw that leaks administrator passwords

On 29 October 2026, Progress made public 15 WS_FTP Server fixes, including CVE-2026-84295, a 10.0-rated authentication bypass that hands over administrator credentials without logging in. Servers must move to 2024.0.7 or 2025.0.4, then reset the exposed passwords.

A half-open metal filing cabinet drawer in a dark archive, one amber manila folder pulled partway out.

3 September 2026. Progress ships WS_FTP Server 2024.0.6 and 2025.0.3, and the release notes name no CVE. 1 October 2026. It ships 2024.0.7 and 2025.0.4, still without naming a flaw. 29 October 2026. It publishes 15 CVE records at once, including CVE-2026-84295, a 10.0-rated authentication bypass that exposes administrator credentials without authentication.

What the flaw hands over, and to whom

WS_FTP Server is Progress’s Windows file-transfer server, often the tool a company uses to exchange files with customers, suppliers or payroll providers. That position is exactly what makes CVE-2026-84295 heavy: a transfer server is, by nature, reachable by outside partners.

The flaw is classified as CWE-287 (Improper Authentication) and CWE-522 (Insufficiently Protected Credentials). Progress’s description is unambiguous: the flaw “could allow an unauthenticated remote attacker to access sensitive information, including administrative credentials.” The CVSS 3.1 vector is the worst case for this class of flaw: AV:N/AC:L/PR:N/UI:N/S:C/C:H/I:H/A:H. Network reachable, low complexity, no account, no interaction, and a changed scope (S:C) meaning the server’s compromise can spill into the systems that depend on it.

Put simply: an attacker who can reach the server over the network can read secrets — including administrator passwords — without identifying themselves. This is a “read then pivot” flaw: the stolen credentials are then used to get back in with high privileges.

The pair that makes it worse: CVE-2026-90868

The same day, Progress published CVE-2026-90868, a command injection (CWE-78/CWE-88) scored 9.9 (AV:N/AC:L/PR:L/UI:N/S:C/C:H/I:H/A:H). The difference is the PR:L prerequisite: the attacker needs a low-privilege account on the server.

On its own, that prerequisite limits the reach. But next to CVE-2026-84295, the pair sketches a full chain: the first flaw supplies credentials — including administrator ones — without logging in, and the second turns any account into arbitrary command execution. Rescana puts it cautiously: no source describes the two being used together, but “a server missing both service packs should be treated as fully exposed, and its credentials should be treated as possibly exposed too.”

A silent fix, then a reveal

The timeline deserves a pause, because it contains a governance lesson. The fixes had existed since 3 September (for CVE-2026-84295) and 1 October (for CVE-2026-90868), but the service-pack release notes named no CVE. Teams that applied the updates as routine never learned they were closing critical flaws; teams that deferred them did not know what they were deferring. On 29 October, everything became public at once.

That delayed reveal has a concrete effect: a server still on a version older than 2024.0.6 / 2025.0.3 is now running a 10.0 flaw that is publicly described. That is the most dangerous configuration there is — not an unknown flaw, but a documented one, fixed elsewhere, still open at home.

As of 29 October, neither CISA (the KEV catalog, version 2026.10.28) nor NVD reported active exploitation, and no public exploit was circulating. But history argues against complacency: WS_FTP Server was already targeted by the Cl0p group, which exploited CVE-2023-40044 in 2023 in the wake of the MOVEit campaign. File-transfer servers are a recurring target of these groups precisely because they concentrate partner files.

The scope and the versions

The version situation adds urgency for part of the fleet. Progress lists Windows as the affected platform for both flaws:

CVEAffected versionsFixedShipped
CVE-2026-84295before 2024.0.6; 2025.0 before 2025.0.32024.0.6 (9.0.6) or 2025.0.3 (10.0.3)3 September 2026
CVE-2026-90868before 2024.0.7; 2025.0 before 2025.0.42024.0.7 (9.0.7) or 2025.0.4 (10.0.4)1 October 2026

One target closes both: 2024.0.7 or 2025.0.4 (or later). Older versions are in a dead end: WS_FTP Server 2022 (8.8) has been retired since 4 July 2026, and the 2024 (9.0) line entered Sunset on 23 October 2026, with no further service packs. Only the 2025 (10.0) line remains in active support, until 10 December 2027.

The rest of the 29 October batch completes the picture: thirteen more CVEs, four of them Critical — CVE-2026-90863, 90864 and 90866 (all 9.1, requiring a delegated Host Administrator account) and CVE-2026-90865 (9.0, command injection through FTP notification variables). There are also MFA bypasses, path traversals, and password disclosures in activity logs.

Verdict

If you run WS_FTP Server, move to 2024.0.7 or 2025.0.4 now: the fix closes both the 10.0 flaw and the command injection, and no configuration workaround has been published. The upgrade alone is not enough: CVE-2026-84295 may already have exposed credentials — change administrator passwords, service accounts and any database credentials the server stores, then review the administrator accounts for any you did not create. If your estate is on 2022.x or a 2024 line in Sunset, plan a migration to 2025.0: those versions will receive no further fixes, and staying on them means keeping a documented flaw permanently open. And if you exchange files with partners, ask them the question: your supplier’s server is your attack surface too — a 10.0 flaw on their side is your files in the attacker’s hands. CVE-2026-84295 is the reminder that, on a transfer server, the technical fix never ends with applying the patch: it ends with rotating the secrets.

Références

The cyber brief, every Tuesday

The flaws that matter and the patches to apply, in a ten-minute read.

No spam. One-click unsubscribe.
read next

On the same topic

Apache HTTP Server 2.4.71 patches critical remote code execution in mod_http2

On November 11, 2026 Apache shipped HTTP Server 2.4.71 to fix CVE-2026-119618, a remote code execution flaw in the HTTP/2 module mod_http2, discovered independently by Anthropic and Google Cloud. Upgrade to 2.4.71 or disable mod_http2 — the flaw reaches any server with HTTP/2 enabled, with no prior authentication.

← Back to the feed

Type at least two characters.

↑ ↓ navigate ↵ open esc dismiss