Complete end-of-life dates, support windows, and security status for all Zentyal versions. Data sourced from endoflife.date and official vendor documentation. Updated at every deploy.
| Version | Latest Release | Release Date | EOL Date | Days | Status |
|---|---|---|---|---|---|
| 2.2 | — | Sep 30, 2011 | Sep 1, 2012 | 4998 days past EOL | EOL |
| 3.0 | — | Sep 30, 2012 | Sep 1, 2013 | 4633 days past EOL | EOL |
| 3.2 | — | Sep 30, 2013 | Oct 1, 2014 | 4238 days past EOL | EOL |
| 4 | — | Oct 31, 2014 | Jan 1, 2016 | 3781 days past EOL | EOL |
| 5 | — | Nov 30, 2016 | Nov 1, 2018 | 2746 days past EOL | EOL |
| 6 | — | Nov 30, 2018 | Jan 1, 2021 | 1954 days past EOL | EOL |
| 7 | — | Jan 31, 2021 | Feb 1, 2024 | 828 days past EOL | EOL |
| 8 | — | Feb 29, 2024 | Already EOL | Supported | Active |
When a Zentyal 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 Zentyal 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.
Upload requirements.txt, package.json, or Gemfile — full EOL report instantly.
Open Stack Scanner →