VMware NSX NSX-T Data Center 3.2 End of Life Date
VMware NSX NSX-T Data Center 3.2 end-of-life date, support status, and CVE risk. Dates read at the vendor's own lifecycle pages (support.broadcom.com); the source of each date is on the product page.
The last patch it will ever receive is 3.2.4.3, published September 29, 2025 — 3 days before support ended. It has been without security patches for 1 year.
Commercial vendors offer security patches beyond EOL. Compare your options.
Compare Options →| Version | Latest | EOL Date | Status |
|---|---|---|---|
| NSX-T Data Center 3.0 | 3.0.3.2 | Apr 7, 2025 | EOL |
| NSX-T Data Center 3.1 | 3.1.3.8 | Apr 7, 2025 | EOL |
| → NSX-T Data Center 3.2 | 3.2.4.3 | Oct 2, 2025 | EOL |
| NSX 4.0 | 4.0.1.1 | Oct 11, 2027 | Active |
| NSX 4.1 | 4.1.2.7 | Oct 11, 2027 | Active |
| NSX 4.2 | 4.2.4.1 | Oct 11, 2027 | Active |
What does VMware NSX NSX-T Data Center 3.2 end of life mean?
When VMware NSX NSX-T Data Center 3.2 reaches end of life, the maintainers stop issuing security patches for this version. CVEs discovered after the EOL date are publicly disclosed on the National Vulnerability Database with no patch available. Exploit code frequently appears on GitHub within days of disclosure.
The CVE blind spot: A CVE-based scan does not show the ongoing accumulation of unpatched vulnerabilities in EOL software versions. Some scanners flag unsupported versions of common products, but coverage varies, and none of them give you the date in advance. Running VMware NSX NSX-T Data Center 3.2 past its EOL date creates a growing attack surface that a clean scan result does not rule out.
Migrate to VMware NSX NSX 4.2 or implement compensating controls — network segmentation, enhanced monitoring, restricted access — while migration is underway.