FreeBSD End of Life (EOL) Dates & Support Timeline
Complete end-of-life dates, support windows, and security status for all FreeBSD versions. Data sourced from endoflife.date and official vendor documentation. Updated at every deploy.
FreeBSD releng/14.5 is supported until June 30, 2027, its end-of-support date. The next FreeBSD version to reach end of life is releng/15.0, on September 30, 2026. 83 of 89 tracked FreeBSD versions are past end of life; the most recent to reach it, releng/14.3, did so on June 30, 2026. The full FreeBSD lifecycle, with every version's release and end-of-support date, is in the table below.
Running an EOL version? Get matched with support options — free ↓| Version | Latest Release | Release Date | EOL Date | Days | Status |
|---|---|---|---|---|---|
| releng/1.0 | — | Nov 30, 1993 | Aug 31, 1994 | 11711 days past EOL | EOL |
| releng/1.1 | — | May 31, 1994 | May 31, 1995 | 11438 days past EOL | EOL |
| releng/2.0 | — | Nov 22, 1994 | Feb 28, 1996 | 11165 days past EOL | EOL |
| releng/2.1 | — | Nov 30, 1995 | Jun 30, 1997 | 10677 days past EOL | EOL |
| releng/2.2 | — | Mar 31, 1997 | Mar 31, 1998 | 10403 days past EOL | EOL |
| releng/3.0 | — | Oct 16, 1998 | May 31, 1999 | 9977 days past EOL | EOL |
| releng/3.1 | — | Feb 28, 1999 | Aug 31, 1999 | 9885 days past EOL | EOL |
| releng/3.2 | — | May 31, 1999 | Dec 31, 1999 | 9763 days past EOL | EOL |
| releng/3.3 | — | Sep 30, 1999 | Feb 29, 2000 | 9703 days past EOL | EOL |
| releng/3.4 | — | Dec 31, 1999 | Sep 30, 2000 | 9489 days past EOL | EOL |
| stable/4 | — | Mar 14, 2000 | Jan 31, 2007 | 7175 days past EOL | EOL |
| releng/4.0 | — | Mar 14, 2000 | Oct 31, 2000 | 9458 days past EOL | EOL |
| releng/3.5 | — | Jun 30, 2000 | Jun 30, 2001 | 9216 days past EOL | EOL |
| releng/4.1 | — | Jul 27, 2000 | Feb 28, 2001 | 9338 days past EOL | EOL |
| releng/4.2 | — | Nov 21, 2000 | Jul 31, 2001 | 9185 days past EOL | EOL |
| releng/4.3 | — | Apr 20, 2001 | Dec 31, 2001 | 9032 days past EOL | EOL |
| releng/4.4 | — | Sep 20, 2001 | Apr 30, 2002 | 8912 days past EOL | EOL |
| releng/4.5 | — | Jan 29, 2002 | Sep 30, 2002 | 8759 days past EOL | EOL |
| releng/4.6 | — | Jun 15, 2002 | Jan 31, 2003 | 8636 days past EOL | EOL |
| releng/4.7 | — | Oct 10, 2002 | Jul 31, 2003 | 8455 days past EOL | EOL |
| stable/5 | — | Jan 14, 2003 | May 31, 2008 | 6689 days past EOL | EOL |
| releng/5.0 | — | Jan 14, 2003 | Sep 30, 2003 | 8394 days past EOL | EOL |
| releng/4.8 | — | Apr 3, 2003 | Feb 28, 2004 | 8243 days past EOL | EOL |
| releng/5.1 | — | Jun 9, 2003 | Apr 30, 2004 | 8181 days past EOL | EOL |
| releng/4.9 | — | Oct 28, 2003 | Aug 31, 2004 | 8058 days past EOL | EOL |
| releng/5.2 | — | Jan 9, 2004 | Feb 28, 2005 | 7877 days past EOL | EOL |
| releng/4.10 | — | May 27, 2004 | Jan 31, 2007 | 7175 days past EOL | EOL |
| releng/5.3 | — | Nov 6, 2004 | Oct 31, 2006 | 7267 days past EOL | EOL |
| releng/4.11 | — | Jan 25, 2005 | Jan 31, 2007 | 7175 days past EOL | EOL |
| releng/5.4 | — | May 9, 2005 | Oct 31, 2006 | 7267 days past EOL | EOL |
| stable/6 | — | Nov 4, 2005 | Nov 30, 2010 | 5776 days past EOL | EOL |
| releng/6.0 | — | Nov 4, 2005 | Jan 31, 2007 | 7175 days past EOL | EOL |
| releng/6.1 | — | May 9, 2006 | May 31, 2008 | 6689 days past EOL | EOL |
| releng/5.5 | — | May 25, 2006 | May 31, 2008 | 6689 days past EOL | EOL |
| releng/6.2 | — | Jan 15, 2007 | May 31, 2008 | 6689 days past EOL | EOL |
| releng/6.3 | — | Jan 18, 2008 | Jan 31, 2010 | 6079 days past EOL | EOL |
| stable/7 | — | Feb 27, 2008 | Feb 28, 2013 | 4955 days past EOL | EOL |
| releng/7.0 | — | Feb 27, 2008 | Apr 30, 2009 | 6355 days past EOL | EOL |
| releng/6.4 | — | Nov 28, 2008 | Nov 30, 2010 | 5776 days past EOL | EOL |
| releng/7.1 | — | Jan 4, 2009 | Feb 28, 2011 | 5686 days past EOL | EOL |
| releng/7.2 | — | May 4, 2009 | Jun 30, 2010 | 5929 days past EOL | EOL |
| stable/8 | — | Nov 25, 2009 | Aug 1, 2015 | 4071 days past EOL | EOL |
| releng/8.0 | — | Nov 25, 2009 | Nov 30, 2010 | 5776 days past EOL | EOL |
| releng/7.3 | — | Mar 23, 2010 | Mar 31, 2012 | 5289 days past EOL | EOL |
| releng/8.1 | — | Jul 23, 2010 | Jul 31, 2012 | 5167 days past EOL | EOL |
| releng/8.2 | — | Feb 24, 2011 | Jul 31, 2012 | 5167 days past EOL | EOL |
| releng/7.4 | — | Feb 24, 2011 | Feb 28, 2013 | 4955 days past EOL | EOL |
| stable/9 | — | Jan 10, 2012 | Dec 31, 2016 | 3553 days past EOL | EOL |
| releng/9.0 | — | Jan 10, 2012 | Mar 31, 2013 | 4924 days past EOL | EOL |
| releng/8.3 | — | Apr 18, 2012 | Apr 30, 2014 | 4529 days past EOL | EOL |
| releng/9.1 | — | Dec 30, 2012 | Dec 31, 2014 | 4284 days past EOL | EOL |
| releng/8.4 | — | Jun 9, 2013 | Aug 1, 2015 | 4071 days past EOL | EOL |
| releng/9.2 | — | Sep 30, 2013 | Dec 31, 2014 | 4284 days past EOL | EOL |
| stable/10 | — | Jan 20, 2014 | Oct 31, 2018 | 2884 days past EOL | EOL |
| releng/10.0 | — | Jan 20, 2014 | Feb 28, 2015 | 4225 days past EOL | EOL |
| releng/9.3 | — | Jul 16, 2014 | Dec 31, 2016 | 3553 days past EOL | EOL |
| releng/10.1 | — | Nov 14, 2014 | Dec 31, 2016 | 3553 days past EOL | EOL |
| releng/10.2 | — | Aug 13, 2015 | Dec 31, 2016 | 3553 days past EOL | EOL |
| releng/10.3 | — | Apr 4, 2016 | Apr 30, 2018 | 3068 days past EOL | EOL |
| stable/11 | — | Oct 10, 2016 | Sep 30, 2021 | 1819 days past EOL | EOL |
| releng/11.0 | — | Oct 10, 2016 | Nov 30, 2017 | 3219 days past EOL | EOL |
| releng/11.1 | — | Jul 26, 2017 | Sep 30, 2018 | 2915 days past EOL | EOL |
| releng/10.4 | — | Oct 3, 2017 | Oct 31, 2018 | 2884 days past EOL | EOL |
| releng/11.2 | — | Jun 28, 2018 | Oct 31, 2019 | 2519 days past EOL | EOL |
| stable/12 | — | Dec 11, 2018 | Dec 31, 2023 | 997 days past EOL | EOL |
| releng/12.0 | — | Dec 11, 2018 | Feb 29, 2020 | 2398 days past EOL | EOL |
| releng/11.3 | — | Jul 9, 2019 | Sep 30, 2020 | 2184 days past EOL | EOL |
| releng/12.1 | — | Nov 4, 2019 | Jan 31, 2021 | 2061 days past EOL | EOL |
| releng/11.4 | — | Jun 16, 2020 | Sep 30, 2021 | 1819 days past EOL | EOL |
| releng/12.2 | — | Oct 27, 2020 | Mar 31, 2022 | 1637 days past EOL | EOL |
| stable/13 | — | Apr 13, 2021 | Apr 30, 2026 | 146 days past EOL | EOL |
| releng/13.0 | — | Apr 13, 2021 | Aug 31, 2022 | 1484 days past EOL | EOL |
| releng/12.3 | — | Dec 7, 2021 | Mar 31, 2023 | 1272 days past EOL | EOL |
| releng/13.1 | — | May 16, 2022 | Jul 31, 2023 | 1150 days past EOL | EOL |
| releng/12.4 | — | Dec 5, 2022 | Dec 31, 2023 | 997 days past EOL | EOL |
| releng/13.2 | — | Apr 11, 2023 | Jun 30, 2024 | 815 days past EOL | EOL |
| stable/14 | — | Nov 20, 2023 | Nov 30, 2028 | 799 days remaining | Active |
| releng/14.0 | — | Nov 20, 2023 | Sep 30, 2024 | 723 days past EOL | EOL |
| releng/13.3 | — | Mar 5, 2024 | Dec 31, 2024 | 631 days past EOL | EOL |
| releng/14.1 | — | Jun 4, 2024 | Mar 31, 2025 | 541 days past EOL | EOL |
| releng/13.4 | — | Sep 17, 2024 | Jun 30, 2025 | 450 days past EOL | EOL |
| releng/14.2 | — | Dec 3, 2024 | Sep 30, 2025 | 358 days past EOL | EOL |
| releng/13.5 | — | Mar 11, 2025 | Apr 30, 2026 | 146 days past EOL | EOL |
| releng/14.3 | — | Jun 10, 2025 | Jun 30, 2026 | 85 days past EOL | EOL |
| releng/15.0 | — | Dec 2, 2025 | Sep 30, 2026 | 7 days remaining | Warning |
| stable/15 | — | Dec 2, 2025 | Dec 31, 2029 | 1195 days remaining | Active |
| releng/14.4 | — | Mar 10, 2026 | Dec 31, 2026 | 99 days remaining | Warning |
| releng/15.1 | — | Jun 16, 2026 | Mar 31, 2027 | 189 days remaining | Active |
| releng/14.5 | — | Sep 8, 2026 | Jun 30, 2027 | 280 days remaining | Active |
Live EOL badge for your README — updates automatically at every build.
[](https://endoflife.ai/freebsd)
FreeBSD release and support pattern
Across the 89 release lines with a published release date, FreeBSD has shipped a new line roughly every 4 months (median interval). A line typically stays supported for about 1.2 years from its release to its end-of-life date.
Of the 89 release lines tracked, 83 are past end of life and 6 are still within support. The newest line, 14.5, was released September 8, 2026. The next scheduled end of life is 15.0 on September 30, 2026 — 6 days from this build. The longest-supported line currently published is 15, to December 31, 2029.
Computed from the tracked release data at every build — the figures above are the dates in the table, restated, not an editorial estimate.
What does FreeBSD end of life mean for your organization?
When a version of FreeBSD 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: A CVE-based scan does not show the accumulation of unpatched vulnerabilities in EOL software. Some scanners flag unsupported versions of common products, but coverage varies, and none of them give you the date in advance. With a zero-day, nobody knows about the vulnerability. With EOL software, the vulnerability is public — listed, rated, and often weaponized — but no vendor patch is coming. This is one of the most dangerous gaps in enterprise security posture.
Organizations running EOL FreeBSD 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.
Your options when FreeBSD reaches end of life
There are four realistic paths. Which one is right depends far more on how long the system needs to keep running than on the version you are on today.
| Option | Best when | Watch out for |
|---|---|---|
| Move to a supported version | The system will outlive the current version's support window and you can schedule the work | Budget for compatibility testing, not just the upgrade itself — that is where the real cost sits |
| Replace the component | The project is unmaintained, or a better-supported alternative exists | The replacement has its own lifecycle and its own end-of-life date — you are changing vendors, not escaping the problem |
| Buy extended support | Migration is genuinely underway but cannot finish before the deadline, or the workload is frozen by certification or a third-party application | A bridge, not a destination — every year purchased is a year the migration still has to happen |
| Document accepted risk | The system is isolated, short-lived, or scheduled for retirement | Only defensible with real compensating controls and a written decision — auditors treat undocumented end-of-life software as a finding |
How to choose, in one question: how many more years does this system need to run? Under a year, extended support (where it exists) is usually cheaper than an emergency migration. One to three years, migrate — support purchased repeatedly costs more than doing the project once, and the project only gets harder as the version ages. Indefinitely, migrate now and plan the next migration before it surprises you.
Worth saying plainly, because vendors selling extended support rarely will: extended support is often the more expensive choice over a multi-year horizon. It is the right answer when a deadline is genuinely unreachable, not as a default. Compare the annual fee against the one-time cost of migrating before committing to either.
Formalizing decisions like this across your estate? Our free EOL policy template is a ready-to-adopt policy with risk tiers, remediation SLAs, and audit mapping — no signup, free to use and share.
Extended Support Options
If you cannot migrate immediately, extended support vendors provide continued security patches for EOL FreeBSD versions. This is a bridge, not a permanent solution — plan your migration in parallel.
FreeBSD has 83 versions past end of life — security patches have stopped, but CVE disclosures haven't. Extended support past the official date exists for many products in this position — whether it exists for FreeBSD is exactly what we check. Tell us where to reach you and we'll reply with matched options and pricing guidance — or an honest "no vendor covers this."