Kaseya VSA End of Life (EOL) Dates & Support Timeline
Complete end-of-life dates, support windows, and security status for all Kaseya VSA versions. Data sourced from endoflife.date and official vendor documentation. Updated at every deploy.
Kaseya VSA 9 (9.5.x) is supported until August 31, 2027, its end-of-support date. It is also the next Kaseya VSA version to reach end of life. The full Kaseya VSA lifecycle, with every version's release and end-of-support date, is in the table below.
Running an EOL version? Get matched with support options — free ↓| Version | Latest Release | Release Date | EOL Date | Days | Status |
|---|---|---|---|---|---|
| 9 (9.5.x) | 9.5.27 | — | Aug 31, 2027 | 325 days remaining | Active |
Live EOL badge for your README — updates automatically at every build.
[](https://endoflife.ai/kaseya-vsa)
Kaseya VSA lifecycle status — the real story
Kaseya VSA is a remote monitoring and management (RMM) server that managed service providers use to control their customers' endpoints. It is sold as SaaS and as an on-premises server. On August 17, 2026 Kaseya published a VSA 9 End of Life Notice. It gives August 31, 2027 as the end-of-life date and says "VSA 9 will be fully decommissioned and cease operation". It also says "only sustaining updates are being deployed until EOL date of August 31, 2027". Kaseya is moving customers to Datto RMM, "our primary recommended platform, with VSA 10 available as an alternate path where required". The notice does not give separate dates for SaaS and on-premises.
Until then, VSA 9 ships as 9.5.x feature releases. Each one goes to SaaS first and reaches on-premises customers later: 9.5.27 started its SaaS rollout on August 8, 2026 and reached General Availability for on-premises customers on August 27, 2026. Kaseya's stated policy is "to provide support for the current GA release, one prior Feature Release, and any interim Maintenance Releases", so an on-premises server more than one feature release behind is already outside support today, well before the 2027 date.
VSA is a high-value target because one compromised server reaches every endpoint it manages. CISA's Known Exploited Vulnerabilities catalog (2026.10.08) lists three Kaseya VSA entries, all flagged as used in ransomware campaigns: CVE-2021-30116 (an information disclosure flaw, added November 3, 2021), CVE-2018-20753 (remote code execution, added April 13, 2022) and CVE-2017-18362 (SQL injection, added May 24, 2022, in the ConnectWise ManagedITSync integration for VSA). Kaseya's own on-premises hardening guide tells administrators to block "all inbound traffic except for port 5721 (the agent port)", which means the server still accepts inbound agent connections even when hardened. Field mapping: eol is the date in Kaseya's notice. No release date or separate end of active support is published for VSA 9.
Kaseya VSA security intelligence
CISA KEV history: Kaseya VSA is named in CISA's Known Exploited Vulnerabilities catalog 3 times, most recently on 2022-05-24, including use in ransomware campaigns. Derived from CISA's live catalog at every build.
What does Kaseya VSA end of life mean for your organization?
When a version of Kaseya VSA 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 Kaseya VSA 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 Kaseya VSA 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.
| Option | Best when | Watch out for |
|---|---|---|
| Move to a supported version | The system will outlive the current version's support window and you can schedule the work | Budget for compatibility testing, not just the upgrade itself — that is where the real cost sits |
| Replace the component | The project is unmaintained, or a better-supported alternative exists | The replacement has its own lifecycle and its own end-of-life date — you are changing vendors, not escaping the problem |
| Buy extended support | Migration is genuinely underway but cannot finish before the deadline, or the workload is frozen by certification or a third-party application | A bridge, not a destination — every year purchased is a year the migration still has to happen |
| Document accepted risk | The system is isolated, short-lived, or scheduled for retirement | Only defensible with real compensating controls and a written decision — auditors treat undocumented end-of-life software as a finding |
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 Kaseya VSA versions. This is a bridge, not a permanent solution — plan your migration in parallel.
When Kaseya VSA versions reach end of life, security patches stop — the CVEs keep coming. Extended support past the official date exists for many products in this position — whether it exists for Kaseya VSA is exactly what we check. Tell us where to reach you and we'll reply with matched options and pricing guidance — or an honest "no vendor covers this."