Fedora End of Life (EOL) Dates & Support Timeline
Complete end-of-life dates, support windows, and security status for all Fedora versions. Data sourced from endoflife.date and official vendor documentation. Updated at every deploy.
Running an EOL version? Get matched with support options — free ↓| Version | Latest Release | Release Date | EOL Date | Days | Status |
|---|---|---|---|---|---|
| 1 (Yarrow) | 1 | Nov 5, 2003 | Sep 20, 2004 | 7993 days past EOL | EOL |
| 2 (Tettnang) | 2 | May 18, 2004 | Apr 11, 2005 | 7790 days past EOL | EOL |
| 3 (Heidelberg) | 3 | Nov 8, 2004 | Jan 16, 2006 | 7510 days past EOL | EOL |
| 4 (Stentz) | 4 | Jun 13, 2005 | Aug 7, 2006 | 7307 days past EOL | EOL |
| 5 (Bordeaux) | 5 | Mar 20, 2006 | Jul 2, 2007 | 6978 days past EOL | EOL |
| 6 (Zod) | 6 | Oct 24, 2006 | Dec 7, 2007 | 6820 days past EOL | EOL |
| 7 (Moonshine) | 7 | May 31, 2007 | Jun 13, 2008 | 6631 days past EOL | EOL |
| 8 (Werewolf) | 8 | Nov 8, 2007 | Jan 7, 2009 | 6423 days past EOL | EOL |
| 9 (Sulphur) | 9 | May 13, 2008 | Jul 10, 2009 | 6239 days past EOL | EOL |
| 10 (Cambridge) | 10 | Nov 25, 2008 | Dec 17, 2009 | 6079 days past EOL | EOL |
| 11 (Leonidas) | 11 | Jun 9, 2009 | Jun 25, 2010 | 5889 days past EOL | EOL |
| 12 (Constantine) | 12 | Nov 17, 2009 | Dec 2, 2010 | 5729 days past EOL | EOL |
| 13 (Goddard) | 13 | May 25, 2010 | Jun 24, 2011 | 5525 days past EOL | EOL |
| 14 (Laughlin) | 14 | Nov 2, 2010 | Dec 9, 2011 | 5357 days past EOL | EOL |
| 15 (Lovelock) | 15 | May 24, 2011 | Jun 26, 2012 | 5157 days past EOL | EOL |
| 16 (Verne) | 16 | Nov 8, 2011 | Feb 12, 2013 | 4926 days past EOL | EOL |
| 17 (Beefy Miracle) | 17 | May 29, 2012 | Jul 30, 2013 | 4758 days past EOL | EOL |
| 18 (Spherical Cow) | 18 | Jan 15, 2013 | Jan 14, 2014 | 4590 days past EOL | EOL |
| 19 (Schrödinger's Cat) | 19 | Jul 2, 2013 | Jan 6, 2015 | 4233 days past EOL | EOL |
| 20 (Heisenbug) | 20 | Dec 17, 2013 | Jun 23, 2015 | 4065 days past EOL | EOL |
| 21 | 21 | Dec 9, 2014 | Dec 1, 2015 | 3904 days past EOL | EOL |
| 22 | 22 | May 26, 2015 | Jul 19, 2016 | 3673 days past EOL | EOL |
| 23 | 23 | Nov 3, 2015 | Dec 20, 2016 | 3519 days past EOL | EOL |
| 24 | 24 | Jun 21, 2016 | Aug 8, 2017 | 3288 days past EOL | EOL |
| 25 | 25 | Nov 22, 2016 | Dec 12, 2017 | 3162 days past EOL | EOL |
| 26 | 26 | Jul 11, 2017 | May 29, 2018 | 2994 days past EOL | EOL |
| 27 | 27 | Nov 14, 2017 | Nov 30, 2018 | 2809 days past EOL | EOL |
| 28 | 28 | May 1, 2018 | May 28, 2019 | 2630 days past EOL | EOL |
| 29 | 29 | Oct 30, 2018 | Nov 26, 2019 | 2448 days past EOL | EOL |
| 30 | 30 | Apr 30, 2019 | May 26, 2020 | 2266 days past EOL | EOL |
| 31 | 31 | Oct 29, 2019 | Nov 24, 2020 | 2084 days past EOL | EOL |
| 32 | 32 | Apr 28, 2020 | May 25, 2021 | 1902 days past EOL | EOL |
| 33 | 33 | Oct 27, 2020 | Nov 30, 2021 | 1713 days past EOL | EOL |
| 34 | 34 | Apr 27, 2021 | Jun 7, 2022 | 1524 days past EOL | EOL |
| 35 | 35 | Nov 2, 2021 | Dec 13, 2022 | 1335 days past EOL | EOL |
| 36 | 36 | May 10, 2022 | May 16, 2023 | 1181 days past EOL | EOL |
| 37 | 37 | Nov 15, 2022 | Dec 5, 2023 | 978 days past EOL | EOL |
| 38 | 38 | Apr 18, 2023 | May 21, 2024 | 810 days past EOL | EOL |
| 39 | 39 | Nov 7, 2023 | Nov 26, 2024 | 621 days past EOL | EOL |
| 40 | 40 | Apr 23, 2024 | May 13, 2025 | 453 days past EOL | EOL |
| 41 | 41 | Oct 29, 2024 | Dec 15, 2025 | 237 days past EOL | EOL |
| 42 (Adams) | 42 | Apr 15, 2025 | May 27, 2026 | 74 days past EOL | EOL |
| 43 | 43 | Oct 28, 2025 | Dec 9, 2026 | 122 days remaining | Warning |
| 44 | 44 | Apr 28, 2026 | Jun 2, 2027 | 297 days remaining | Active |
Live EOL badge for your README — updates automatically at every build.
[](https://endoflife.ai/fedora)
What does Fedora end of life mean for your organization?
When a version of Fedora 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 Fedora 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 Fedora 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.
Extended Support Options
If you cannot migrate immediately, extended support vendors provide continued security patches for EOL Fedora versions. This is a bridge, not a permanent solution — plan your migration in parallel.
Fedora has 42 versions past end of life — security patches have stopped, but CVE disclosures haven't. The good news: extended support for Fedora exists — vetted vendors ship security patches for years past the official date. Tell us where to reach you and we'll reply with matched options and pricing guidance.