SolarWinds Serv-U End of Life (EOL) Dates & Support Timeline

SolarWinds Serv-U lifecycle status — the real story

SolarWinds Serv-U is a file transfer server (Serv-U MFT Server and Serv-U FTP Server) that exists to exchange files with outside parties, so it is commonly reachable from the internet. SolarWinds dates each Serv-U release individually on its Serv-U release history page, with three dates per release: the end-of-life announcement, End-of-Engineering (EoE) and End-of-Life (EoL). At EoE, "Service releases, bug fixes, workarounds, and service packs" for that release "will no longer be actively supported by SolarWinds"; at EoL, "SolarWinds will no longer provide technical support" for it. Serv-U 15.5 reached its EoL on October 8, 2026, and 15.5.1 follows on November 18, 2026. The current release line is 2026.3.

Four Serv-U vulnerabilities are in CISA's Known Exploited Vulnerabilities catalog (2026.10.08): CVE-2021-35211 (remote code execution, added November 3, 2021, flagged as used in ransomware campaigns), CVE-2021-35247 (improper input validation, added January 21, 2022), CVE-2024-28995 (path traversal, added July 17, 2024) and CVE-2026-28318 (unauthenticated denial of service, added June 5, 2026). SolarWinds shipped the CVE-2026-28318 fix as Serv-U 15.5.4 Hotfix 1 on June 4, 2026 and says "You must be on Serv-U 15.5.4 to download and install this hotfix. Other Serv-U versions are not compatible with the hotfix."

Field mapping: support is the End-of-Engineering date (no more service releases, bug fixes or patches) and eol is the End-of-Life date (no technical support), both exactly as SolarWinds prints them. SolarWinds' End of Life Policy defines EoE as the date SolarWinds "will cease engineering related to Self-Hosted Software", and EoL as the date "all technical support shall cease". Two rows on the vendor page cover ranges ("15.3.2 and earlier", "15.1.6 and earlier"); the cycle label keeps that wording. Release dates come from the Serv-U release notes on documentation.solarwinds.com.

SolarWinds Serv-U release and support pattern

Across the 7 release lines with a published release date, SolarWinds Serv-U has shipped a new line roughly every 5 months (median interval). A line typically stays supported for about 2 years from its release to its end-of-life date (measured on the 3 lines with both dates published).

Of the 12 release lines tracked, 7 are past end of life and 5 are still within support. The newest line, 2026.3, was released July 21, 2026. The next scheduled end of life is 15.5.1 on November 18, 2026 — 39 days from this build.

Computed from the tracked release data at every build — the figures above are the dates in the table, restated, not an editorial estimate.

SolarWinds Serv-U security intelligence

CISA KEV history: SolarWinds Serv-U is named in CISA's Known Exploited Vulnerabilities catalog 4 times, most recently on 2026-06-05, including use in ransomware campaigns. Derived from CISA's live catalog at every build.

What does SolarWinds Serv-U end of life mean for your organization?

When a version of SolarWinds Serv-U reaches end of life, the maintainers stop issuing security patches. Vulnerabilities discovered after this date are publicly disclosed on the National Vulnerability Database, exploit code appears on GitHub, and your systems remain permanently exposed.

The CVE blind spot: A CVE-based scan does not show the accumulation of unpatched vulnerabilities in EOL software. Some scanners flag unsupported versions of common products, but coverage varies, and none of them give you the date in advance. With a zero-day, nobody knows about the vulnerability. With EOL software, the vulnerability is public — listed, rated, and often weaponized — but no vendor patch is coming. This is one of the most dangerous gaps in enterprise security posture.

Organizations running EOL SolarWinds Serv-U should treat it as a vulnerability class in their risk register, apply compensating controls (network segmentation, enhanced monitoring, access restriction), and prioritize migration to a supported version.

Your options when SolarWinds Serv-U reaches end of life

There are four realistic paths. Which one is right depends far more on how long the system needs to keep running than on the version you are on today.

How to choose, in one question: how many more years does this system need to run? Under a year, extended support (where it exists) is usually cheaper than an emergency migration. One to three years, migrate — support purchased repeatedly costs more than doing the project once, and the project only gets harder as the version ages. Indefinitely, migrate now and plan the next migration before it surprises you.

Worth saying plainly, because vendors selling extended support rarely will: extended support is often the more expensive choice over a multi-year horizon. It is the right answer when a deadline is genuinely unreachable, not as a default. Compare the annual fee against the one-time cost of migrating before committing to either.

Formalizing decisions like this across your estate? Our free EOL policy template is a ready-to-adopt policy with risk tiers, remediation SLAs, and audit mapping — no signup, free to use and share.

Extended Support Options

If you cannot migrate immediately, extended support vendors provide continued security patches for EOL SolarWinds Serv-U versions. This is a bridge, not a permanent solution — plan your migration in parallel.

Related Products