Vmware Srm · Lifecycle Status

Vmware Srm End of Life (EOL) Dates & Support Timeline

Complete end-of-life dates, support windows, and security status for all Vmware Srm versions. Data sourced from endoflife.date and official vendor documentation. Updated at every deploy.

All Vmware Srm versions are past end of life. No security patches are being issued. Migrate to a supported alternative or purchase extended support.
Latest Active
— series
Next EOL
None upcoming
Active Versions
0
of 13 total
EOL Versions
13
no longer patched
Release Cycle Timeline
EOL   Warning   Active   Today
Release cycle timeline 20142015201620172018201920202021202220232024202520265.85.56.16.06.58.18.28.38.48.58.68.78.8TODAY
All Versions
VersionLatest ReleaseRelease DateEOL DateDaysStatus
5.5 5.5.1.7 Sep 19, 2013 Sep 19, 2018 2789 days past EOL EOL
5.8 5.8.1.1 Sep 19, 2013 Sep 19, 2018 2789 days past EOL EOL
6.0 6.0.0.1 Mar 12, 2015 Mar 12, 2020 2249 days past EOL EOL
6.1 6.1.2.2 Mar 12, 2015 Mar 12, 2020 2249 days past EOL EOL
6.5 6.5.1.3 Nov 15, 2016 Nov 15, 2021 1636 days past EOL EOL
8.1 8.1.2.4 Apr 17, 2018 Nov 15, 2021 1636 days past EOL EOL
8.2 8.2.1.2 May 9, 2019 Nov 15, 2021 1636 days past EOL EOL
8.3 8.3.1.6 Apr 1, 2020 Apr 1, 2023 1134 days past EOL EOL
8.4 8.4.0.5 Mar 9, 2021 Apr 1, 2023 1134 days past EOL EOL
8.5 8.5.0.8 Oct 5, 2021 Apr 1, 2023 1134 days past EOL EOL
8.6 8.6.0.2 Oct 11, 2022 Oct 11, 2025 210 days past EOL EOL
8.7 8.7.0.4 Apr 18, 2023 Oct 11, 2025 210 days past EOL EOL
8.8 8.8.0.3 Sep 21, 2023 Oct 11, 2025 210 days past EOL EOL

What does Vmware Srm end of life mean for your organization?

When a Vmware Srm version 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: Most vulnerability scanners check for known CVEs but do not flag the accumulation of unpatched vulnerabilities in EOL software. With a zero-day, nobody knows about the vulnerability. With EOL software, the vulnerability is public — listed, rated, and often weaponized — but no patch will ever exist. This is the most dangerous gap in enterprise security posture.

Organizations running EOL Vmware Srm 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.

Check your full stack for EOL risk

Upload requirements.txt, package.json, or Gemfile — full EOL report instantly.

Open Stack Scanner →
Frequently Asked Questions
What is the end-of-life date for Vmware Srm?
See the full table above for all Vmware Srm version EOL dates.
What is the latest supported version of Vmware Srm?
The latest active version of Vmware Srm is . Always verify against the table above as support windows can change.
What happens when Vmware Srm reaches end of life?
When Vmware Srm reaches end of life, the vendor stops issuing security patches. Any CVEs disclosed after the EOL date accumulate indefinitely with no patch path — creating an ever-growing attack surface that most vulnerability scanners do not flag.
How do I check if I'm running an EOL version of Vmware Srm?
Check your current version against the table above. If your version's EOL date has passed, you are running unsupported software. You can also use the endoflife.ai Stack Scanner to check your entire dependency file at once.
Is there extended support available for EOL Vmware Srm versions?
Some vendors offer extended support for EOL software. Contact the original vendor or check with enterprise support providers for options.

Related Products

Data from endoflife.date API · endoflife.date · Generated at build time · How we source data →