Kaseya VSA 9 End of Life: August 31, 2027
Kaseya VSA 9 reaches end of life on August 31, 2027: Kaseya's VSA 9 End of Life Notice says VSA 9 will be "fully decommissioned and cease operation" on that date. The notice gives one date for VSA 9. It prints no separate date for on-premises servers and none for SaaS, and it says all customers must have completed migration to Datto RMM or VSA 10 before that date. Kaseya published the notice on August 17, 2026. Until end of life, the notice says, VSA 9 has no further innovation roadmap and gets only sustaining updates.
Key Dates at a Glance
- Kaseya VSA 9: end of life 2027-08-31
- VSA 9 End of Life Notice: published 2026-08-17
- VSA 9.5.27a: General Availability for on-premises customers 2026-10-29
- CVE-2021-30116: added to CISA KEV 2021-11-03
- CVE-2018-20753: added to CISA KEV 2022-04-13
- CVE-2017-18362: added to CISA KEV 2022-05-24
What Kaseya's notice says about each product
| Product | In Kaseya's words | End of life |
|---|---|---|
| VSA 9 (9.5.x releases) | A legacy platform that Kaseya is retiring; only sustaining updates until end of life | August 31, 2027 |
| Datto RMM | Primary recommended platform; primary migration target for VSA 9 customers | No date in the notice |
| VSA 10 | Alternate path, where required for the customer's environment | No date in the notice |
The notice is about VSA 9 only. It publishes no release date for VSA 9 and no separate end date for active development; our Kaseya VSA page leaves both empty for that reason.
Does the date apply to on-premises VSA 9?
Kaseya's notice does not separate the two ways VSA 9 is delivered. It names VSA 9 as a whole, gives one end-of-life date, and says all customers must have completed migration before it. We publish that date, August 31, 2027, as the end-of-life date of VSA 9 for on-premises and SaaS.
The notice leaves three on-premises questions open:
- It does not say how a server that a customer hosts itself is switched off on that date.
- It does not give an earlier or later end of support for on-premises servers. The release notes do set a minimum supported version, covered in the next section.
- It does not say whether either migration path can be run on-premises. Kaseya's own product page describes Datto RMM as a cloud-based solution.
The notice sends each customer to the account manager to confirm the recommended path and to agree milestones. Take these three questions with you.
What Kaseya supports until then
VSA 9 ships as 9.5.x releases. Each release's notes in Kaseya's VSA release notes carry a release schedule and a section on the support policy for prior releases.
- The policy. Kaseya supports the current GA release, one prior Feature Release, and any interim Maintenance Releases.
- SaaS first, on-premises after. A release schedule lists the SaaS deployment dates and then a General Availability date for on-premises customers. Kaseya's release notes for 9.5.27a list General Availability for on-premises customers: October 29, 2026.
- The minimum supported version. The same notes say that after that GA date the minimum supported version is the 9.5.26 Feature Release.
- Security updates. The same notes say the release includes important security updates and recommend that on-premises customers upgrade as soon as possible after the GA date. SaaS customers need no action, because updates are applied for them.
The notice does not say how many more releases VSA 9 will get. The minimum supported version moves with each release, so read the newest release notes before you rely on the one named here.
Why a neglected VSA server is a risk
A VSA server manages every endpoint that reports to it. CISA's Known Exploited Vulnerabilities catalog lists 3 Kaseya VSA entries, all 3 flagged as known to be used in ransomware campaigns.
| CVE | What CISA lists | Added to the catalog |
|---|---|---|
| CVE-2021-30116 | Kaseya VSA information disclosure vulnerability | November 3, 2021 |
| CVE-2018-20753 | Kaseya VSA remote code execution vulnerability | April 13, 2022 |
| CVE-2017-18362 | Kaseya VSA SQL injection vulnerability, in the ConnectWise ManagedITSync integration for VSA | May 24, 2022 |
Kaseya's VSA On-Premises Hardening and Best Practice Guide recommends limiting access to the VSA application to local IP addresses by blocking all inbound traffic except port 5721, the agent port. A hardened server still accepts agent connections on that port. That is the reason to stay on a supported release until the migration is finished.
What a VSA 9 owner should plan
- Check the release you run. An on-premises server below the minimum supported version in the newest release notes is outside Kaseya's support policy now. Upgrade it first.
- Ask your account manager which path applies. Kaseya names Datto RMM as the primary migration target and VSA 10 as the alternate path, and says the account manager confirms the recommended path for each environment.
- If you need to stay on-premises, ask that question directly. The notice does not say that either path can be self-hosted. Get the answer in writing before you plan around it.
- Agree the milestones. The notice asks customers to agree key milestones, responsibilities and next steps. Work back from August 31, 2027: Kaseya says migration must be complete before that date.
- Keep the server restricted until it is switched off. Follow the network recommendations in Kaseya's hardening guide and apply each release after its on-premises GA date.
The EOL Checker looks up one product and version. Our Kaseya VSA page carries the live status and EOL Risk Score.
Frequently Asked Questions
When does Kaseya VSA 9 reach end of life?
August 31, 2027. Kaseya's VSA 9 End of Life Notice says VSA 9 will be fully decommissioned and cease operation on that date, and that all customers must have completed migration to Datto RMM or VSA 10 before it.
Does the August 31, 2027 end-of-life date apply to on-premises VSA 9?
Kaseya's notice gives one end-of-life date for VSA 9 and prints no separate date for on-premises servers or for SaaS. It says all customers must have completed migration before that date. The notice does not say how a server that a customer hosts itself is switched off, so ask your Kaseya account manager how the date applies to yours.
Is Kaseya VSA 9 still supported?
Yes, on current releases. Kaseya says only sustaining updates are being deployed until the end-of-life date. Its policy supports the current GA release, one prior Feature Release and any interim Maintenance Releases.
What is the minimum supported VSA 9 version?
The 9.5.26 Feature Release, according to Kaseya's release notes for 9.5.27a, which reached General Availability for on-premises customers on October 29, 2026. The minimum moves with each release, so check the newest release notes.
What replaces Kaseya VSA 9?
Kaseya names Datto RMM as its primary recommended platform and the primary migration target for VSA 9 customers. VSA 10 is available as an alternate path where required. Kaseya says the account manager confirms the recommended path for each environment.
Is Kaseya VSA in CISA's Known Exploited Vulnerabilities catalog?
Yes. The catalog lists 3 Kaseya VSA entries, all 3 flagged as known to be used in ransomware campaigns: CVE-2021-30116 (added November 3, 2021), CVE-2018-20753 (added April 13, 2022) and CVE-2017-18362 (added May 24, 2022).
Related
- Kaseya VSA — live status and EOL Risk Score
- Configuration Manager 2509 end of support — another endpoint management server with a dated end
- Three KEV-listed SolarWinds products at end of life — management software in CISA's catalog
- EOL Checker and How we verify our dates