End of life used to be a routine upgrade conversation. Under Broadcom, it's a forcing function: upgrading past EOL means moving onto a per-core subscription, so the EOL date on your version is effectively the deadline for your whole platform decision.
VMware support lifecycle dates
End of General Support (EoGS) is the date that matters: after it, no new security patches, bug fixes, or standard support. End of Technical Guidance (EoTG) adds only limited self-service help for low-severity issues, no patches.
| Product / Version | End of General Support | End of Technical Guidance | Status (June 2026) |
|---|---|---|---|
| vSphere / ESXi 6.5 & 6.7 | Oct 15, 2022 | Nov 2023 | Unsupported 3.5+ years |
| vSphere / ESXi 7.0 | Apr 2, 2025 | Apr 2, 2027 | Past EoGS, no new patches |
| vCenter Server 7.0 | Apr 2, 2025 | Apr 2, 2027 | Past EoGS |
| vSphere / ESXi 8.0 | Oct 11, 2027 | Oct 11, 2029 | Supported ~16 months more |
| vCenter Server 8.0 | Oct 11, 2027 | Oct 11, 2029 | Supported |
| VCF 9.x (current) | Per Broadcom lifecycle policy | - | Subscription required |
Dates reflect Broadcom's published lifecycle matrix as of June 2026; always verify your exact build against Broadcom's current lifecycle page, and note that extended support can sometimes be purchased, at a steep premium.
What running unsupported actually exposes you to
Security exposure
ESXi is one of the most attacked pieces of infrastructure software on earth. Ransomware families purpose-built for ESXi (the "ESXiArgs" wave being the most famous) have encrypted thousands of environments, and new hypervisor CVEs, including in-the-wild exploited vulnerabilities, appear every year. On an unsupported version, every one of those becomes a permanent hole. Broadcom has occasionally issued out-of-cycle patches for catastrophic flaws on EOL versions, but that's a courtesy, not a policy you can build a risk posture on.
Compliance impact
- PCI DSS requires vendor-supported, patchable system components; unsupported hypervisors are a standard audit finding.
- HIPAA security-rule risk analyses must address unpatchable infrastructure hosting ePHI.
- CMMC / NIST 800-171 flaw-remediation controls are effectively impossible to satisfy without a patch source.
- Cyber insurance applications increasingly ask directly about end-of-life software; a breach traced to an unpatched EOL hypervisor is a claim-denial scenario.
Operational risk
- No vendor support during a severity-1 outage, your cluster, your problem.
- New hardware won't be certified for old ESXi; a failed host may be irreplaceable.
- Backup, monitoring, and security vendors progressively drop EOL-version compatibility.
The EOL trap: why "just upgrade" isn't simple anymore
Pre-Broadcom, the answer to EOL was a weekend upgrade cycle. Now upgrading from 7.x means adopting a VCF/VVF per-core subscription, the very price increase you may be trying to avoid (see how the new licensing works). That's why the EOL date and the renewal quote have collapsed into a single decision: pay Broadcom's new price, or use the deadline to move.
Your options at end of life
| Option | What it means | Best when |
|---|---|---|
| Upgrade + subscribe | Move to vSphere 8 / VCF 9 on per-core subscription direct with Broadcom | Deep VMware dependencies, budget absorbs the increase |
| Move to a managed VMware provider | Run current, supported VMware in a provider's cloud at VCSP scale pricing | You want vSphere without Broadcom's direct pricing, see providers |
| Migrate platforms | Replatform to Nutanix, Proxmox, Hyper-V, or OpenShift | Hardware refresh due anyway; long-term cost control is the goal, see comparisons |
| Third-party support (bridge) | Independent support firms keep lights on while you execute a plan | Buying 6–18 months of runway, not a destination |
| Do nothing | Run unsupported and accept the exposure | Honestly: almost never defensible past a short, planned window |
Recommended action by where you are
- On 6.5/6.7: You're years past safe. Treat this as an active incident-in-waiting; pick a destination and a timeline this quarter.
- On 7.0: Past EoGS as of April 2025. Don't burn effort on an in-place upgrade to 8 unless you've already decided to stay and pay, evaluate alternatives first, because migration effort is similar either way.
- On 8.0: You have until October 2027, enough runway to do this right, not enough to defer it past your next budget cycle. A typical mid-market migration takes 3–9 months (cost guide).
- Perpetual with active SnS: Find your exact support expiry date today. That date, not the EOL date, is your real planning horizon.
Not sure which bucket you're in or what the move costs? A free assessment gives you a dated, priced plan in days.