Complete end-of-life dates, support windows, and security status for all Openzfs versions. Data sourced from endoflife.date and official vendor documentation. Updated at every deploy.
| Version | Latest Release | Release Date | EOL Date | Days | Status |
|---|---|---|---|---|---|
| 0.8 | 0.8.6 | May 21, 2019 | Dec 14, 2020 | 1972 days past EOL | EOL |
| 2.0 | 2.0.7 | Nov 30, 2020 | Dec 23, 2021 | 1598 days past EOL | EOL |
| 2.1 | 2.1.16 | Apr 19, 2021 | Jan 13, 2025 | 481 days past EOL | EOL |
| 2.2 | 2.2.9 | Jul 27, 2023 | Dec 18, 2025 | 142 days past EOL | EOL |
| 2.3 | 2.3.6 | Oct 17, 2024 | Already EOL | Supported | Active |
| 2.4 | 2.4.1 | Dec 18, 2025 | Already EOL | Supported | Active |
When a Openzfs 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 Openzfs 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 →