Openzfs 2.0 · Version Status

Openzfs 2.0 End of Life Date

Openzfs 2.0 end-of-life date, support status, and CVE risk. Data from endoflife.date and official vendor documentation.

Openzfs 2.0 is past end of life. This version no longer receives security patches. 1598 days past EOL — migrate to a supported version immediately.
EOL Date
Dec 23, 2021
1598 days past EOL
Latest Release
2.0.7
Standard release
Release Date
Nov 30, 2020
Openzfs 2.0 series
← Openzfs 0.8 All Openzfs versions Openzfs 2.1 →
Recommended upgrade path
Openzfs 2.4
Latest release: 2.4.1 · EOL: Supported
View full Openzfs timeline →
All Openzfs Versions
VersionLatestEOL DateStatus
0.8 0.8.6 Dec 14, 2020 EOL
2.0 2.0.7 Dec 23, 2021 EOL
2.1 2.1.16 Jan 13, 2025 EOL
2.2 2.2.9 Dec 18, 2025 EOL
2.3 2.3.6 EOL Active
2.4 2.4.1 EOL Active

What does Openzfs 2.0 end of life mean?

When Openzfs 2.0 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: Most vulnerability scanners check for known CVEs but do not flag the ongoing accumulation of unpatched vulnerabilities in EOL software versions. Running Openzfs 2.0 past its EOL date creates a permanently growing attack surface that standard security tooling will not surface.

Migrate to Openzfs 2.4 or implement compensating controls — network segmentation, enhanced monitoring, restricted access — while migration is underway.

Frequently Asked Questions
When does Openzfs 2.0 reach end of life?
Openzfs 2.0 reached end of life on December 23, 2021. This version is no longer receiving security patches.
Is Openzfs 2.0 still supported?
No. Openzfs 2.0 reached end of life on December 23, 2021 and is no longer receiving security patches.
What should I upgrade to from Openzfs 2.0?
The recommended upgrade from Openzfs 2.0 is Openzfs 2.4 — the latest actively supported version. Check the Openzfs full timeline for all supported versions.
What are the security risks of running Openzfs 2.0 past EOL?
When Openzfs 2.0 reaches end of life, the maintainers stop issuing security patches. Any CVEs disclosed after the EOL date accumulate with no remediation path. Most vulnerability scanners do not flag this — it is the CVE blind spot. Organizations running EOL Openzfs should migrate immediately or implement compensating controls.
Data from endoflife.date API · Generated at build time · How we source data →