Patch & vulnerability status
Tim Kosse
FileZilla Server 1.12.6
Latest tracked version 1.12.6. Release status, tracked CVEs, and automated cross-platform patching for FileZilla Server.
| Platform | Latest version | CVEs tracked | Last checked |
|---|---|---|---|
| Windows | 1.12.6 | 3 | 2026-08-10 |
Known vulnerabilities (CVEs) in FileZilla Server
Lavawall tracks 3 published CVEs affecting FileZilla Server, and deploys the versions that fix them automatically across your fleet.
| CVE | Published | Severity | Details | Vector |
|---|---|---|---|---|
| CVE-2015-10003 | 2022-07-17 07:15:07 | MEDIUM (4) | A vulnerability, which was classified as problematic, was found in FileZilla Server up to 0.9.50. This affects an unknown part of the component PORT Handler. The manipulation leads to unintended intermediary. It is possible to initiate the attack remotely. Upgrading to version 0.9.51 is able to address this issue. It is recommended to upgrade the affected component. | NETWORK |
| CVE-2014-0224 | 2014-06-05 21:55:08 | HIGH (7) | OpenSSL before 0.9.8za, 1.0.0 before 1.0.0m, and 1.0.1 before 1.0.1h does not properly restrict processing of ChangeCipherSpec messages, which allows man-in-the-middle attackers to trigger use of a zero-length master key in certain OpenSSL-to-OpenSSL communications, and consequently hijack sessions or obtain sensitive information, via a crafted TLS handshake, aka the "CCS Injection" vulnerability. | NETWORK |
| CVE-2014-0160 | 2014-04-07 22:55:04 | HIGH (8) | The (1) TLS and (2) DTLS implementations in OpenSSL 1.0.1 before 1.0.1g do not properly handle Heartbeat Extension packets, which allows remote attackers to obtain sensitive information from process memory via crafted packets that trigger a buffer over-read, as demonstrated by reading private keys, related to d1_both.c and t1_lib.c, aka the Heartbleed bug. | NETWORK |
Why keeping FileZilla Server patched matters
Unpatched third-party applications are one of the most common ways attackers get in: 57% of breached MSP clients and 32% of ransomware cases trace back to a missing patch. Every FileZilla Server release that fixes a security bug is public, so attackers see it too, and an out-of-date install becomes a documented way in. Tracking the installed version on every machine and closing the gap quickly is what turns a disclosed CVE into a non-event.
How Lavawall® patches FileZilla Server
Lavawall® watches FileZilla Server releases and CVEs continuously, ranks each update by risk, and deploys it across your whole fleet, Windows, macOS, and Linux, from a single agent, independently of your RMM. You get one place to see which machines are behind on FileZilla Server, one policy to bring them current, and timestamped evidence for audits.
Frequently asked questions
Lavawall tracks FileZilla Server at version 1.12.6 (last checked 2026-08-10). New releases are monitored continuously and can be deployed automatically across your fleet.
Lavawall tracks 3 CVEs for FileZilla Server and remediates them automatically as part of patching.
Deploy the Lavawall® agent and FileZilla Server updates are applied automatically across Windows, macOS, and Linux, risk-ranked and reported, independently of your RMM.
Lavawall® monitors releases and CVEs for FileZilla Server through public information and proprietary statistical analysis, and can patch it automatically across your fleet.