Why File Transfer Servers Get Exploited So Often
Why file transfer servers get exploited so often: bulk data, internet exposure and outside users. How to plan for the next MFT zero-day before it lands.
File transfer servers get exploited because they hold large volumes of sensitive data, face the internet by design and accept logins from people outside the organization. One flaw gives an attacker bulk data to steal and a list of partners to extort. CISA's KEV catalog shows the pattern: IBM Aspera Faspex, Progress MOVEit Transfer and Fortra GoAnywhere MFT have all had exploited flaws, several tied to ransomware. Plan for these servers as high-value targets, not utilities.
The latest example is the IBM Aspera Faspex CVE-2026-123218 authorization bypass, added to the KEV catalog on 9 November 2026.
Why do attackers target file transfer servers?
Attackers target file transfer servers because one compromise yields data from many people and partners at once, without moving through the internal network. The data is already collected, labeled and ready to download.
Compare that with a typical intrusion. An attacker who lands on a workstation has to escalate, move laterally, find file shares and stage data before stealing anything. On a file exchange server, the payroll exports, contracts, design files and medical records are already in one place.
A short history in the KEV catalog
The CISA KEV catalog records file transfer products repeatedly:
- Fortra GoAnywhere MFT, CVE-2023-0669. Remote code execution, added 10 February 2023, marked as known ransomware use.
- IBM Aspera Faspex, CVE-2022-47986. YAML deserialization leading to code execution, added 21 February 2023, marked as known ransomware use.
- Progress MOVEit Transfer, CVE-2023-34362. SQL injection, added 2 June 2023, marked as known ransomware use.
- IBM Aspera Faspex, CVE-2026-123218. Authorization bypass to full admin, added 9 November 2026, ransomware use currently unknown.
Faspex appears twice. Attackers who built tooling and target lists for one flaw in a product come back when the next one is published.
Why are these servers hard to defend?
They are hard to defend because their purpose conflicts with the usual controls. A file transfer server must be reachable from the internet, must accept logins from people your identity team does not manage, and must store data long enough for the recipient to collect it.
Other factors make it worse:
- Ownership is unclear. A business unit often buys the service for one partner, and IT inherits it later.
- Patch windows are tight. Partners depend on uptime, so outages get pushed back.
- External accounts pile up. Guest users from finished projects keep working credentials for years.
- Retention is too long. Files that should have been deleted after download stay on the server, so a breach exposes years of data rather than days.
Why does an authorization bypass matter as much as code execution here?
On a file transfer server, an admin account already gives access to every stored file, every user and the configuration. The attacker does not need to run code on the operating system to steal the data, so an authorization flaw like the Faspex bug can do the same business damage as remote code execution.
Our explainer on incorrect authorization (CWE-863) covers how these flaws work.
How to plan for the next file transfer zero-day
Treat the next exploited flaw as a matter of when, and prepare the response before it arrives.
Know what you run. Keep a register of every file transfer service, including SaaS ones, with owner, version, exposure and the partners who rely on it. The register is what lets you answer "are we affected?" in an hour rather than a day.
Pre-approve emergency patching. Agree with business owners now that a KEV listing for a file transfer product triggers same-day patching or a temporary shutdown. Kiteworks customers faced this choice in September when the vendor ordered a precautionary global shutdown.
Limit what can be stolen.
- Set automatic deletion after download or after a fixed number of days.
- Expire external accounts when projects end.
- Remove self-registration unless a partner needs it.
Watch for the outcome, not the exploit. Vendors often publish no technical details, as IBM did with CVE-2026-123218. You can still detect results: new admin accounts, role changes, unusual bulk downloads and logins from unexpected countries. Send these events to your SIEM.
Rehearse the audit. Write the post-patch checklist once and reuse it. Our guide on how to patch Aspera Faspex 5 and audit admin accounts is a template you can adapt to other products.
Should you replace a product with repeated exploited flaws?
Repeated KEV entries are a reason to review the product, not an automatic reason to replace it. Look at how fast the vendor shipped fixes, whether the advisories were clear, and whether the product lets you restrict admin access and shorten retention. A product that patches quickly and supports these controls may be safer than an unknown replacement with no track record.