Foreman End of Life (EOL) Dates & Support Timeline
Complete end-of-life dates, support windows, and security status for all Foreman 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.2 | 1.2.3 | Jul 1, 2013 | Jan 29, 2014 | 4580 days past EOL | EOL |
| 1.3 | 1.3.2 | Oct 14, 2013 | May 9, 2014 | 4480 days past EOL | EOL |
| 1.4 | 1.4.5 | Jan 29, 2014 | Sep 10, 2014 | 4356 days past EOL | EOL |
| 1.5 | 1.5.3 | May 9, 2014 | Dec 2, 2014 | 4273 days past EOL | EOL |
| 1.6 | 1.6.3 | Sep 10, 2014 | Apr 28, 2015 | 4126 days past EOL | EOL |
| 1.7 | 1.7.5 | Dec 2, 2014 | Aug 18, 2015 | 4014 days past EOL | EOL |
| 1.8 | 1.8.4 | Apr 28, 2015 | Dec 23, 2015 | 3887 days past EOL | EOL |
| 1.9 | 1.9.3 | Aug 18, 2015 | Mar 31, 2016 | 3788 days past EOL | EOL |
| 1.10 | 1.10.4 | Dec 23, 2015 | Jul 8, 2016 | 3689 days past EOL | EOL |
| 1.11 | 1.11.4 | Mar 31, 2016 | Oct 5, 2016 | 3600 days past EOL | EOL |
| 1.12 | 1.12.4 | Jul 8, 2016 | Jan 13, 2017 | 3500 days past EOL | EOL |
| 1.13 | 1.13.4 | Oct 5, 2016 | May 9, 2017 | 3384 days past EOL | EOL |
| 1.14 | 1.14.3 | Jan 13, 2017 | Nov 29, 2017 | 3180 days past EOL | EOL |
| 1.15 | 1.15.7 | May 9, 2017 | Apr 11, 2018 | 3047 days past EOL | EOL |
| 1.16 | 1.16.2 | Nov 29, 2017 | Jul 12, 2018 | 2955 days past EOL | EOL |
| 1.17 | 1.17.4 | Apr 11, 2018 | Aug 30, 2018 | 2906 days past EOL | EOL |
| 1.18 | 1.18.3 | Jul 12, 2018 | Nov 15, 2018 | 2829 days past EOL | EOL |
| 1.19 | 1.19.1 | Aug 30, 2018 | Feb 26, 2019 | 2726 days past EOL | EOL |
| 1.20 | 1.20.3 | Nov 15, 2018 | Jul 2, 2019 | 2600 days past EOL | EOL |
| 1.21 | 1.21.4 | Feb 26, 2019 | Sep 18, 2019 | 2522 days past EOL | EOL |
| 1.22 | 1.22.2 | Jun 4, 2019 | Dec 9, 2019 | 2440 days past EOL | EOL |
| 1.23 | 1.23.2 | Sep 10, 2019 | Apr 2, 2020 | 2325 days past EOL | EOL |
| 1.24 | 1.24.3 | Dec 9, 2019 | Jul 2, 2020 | 2234 days past EOL | EOL |
| 2.0 | 2.0.3 | Apr 2, 2020 | Oct 28, 2020 | 2116 days past EOL | EOL |
| 2.1 | 2.1.4 | Jul 2, 2020 | Dec 1, 2020 | 2082 days past EOL | EOL |
| 2.2 | 2.2.3 | Oct 28, 2020 | Mar 19, 2021 | 1974 days past EOL | EOL |
| 2.3 | 2.3.5 | Dec 1, 2020 | Jun 9, 2021 | 1892 days past EOL | EOL |
| 2.4 | 2.4.1 | Mar 19, 2021 | Sep 7, 2021 | 1802 days past EOL | EOL |
| 2.5 | 2.5.4 | Jun 2, 2021 | Dec 9, 2021 | 1709 days past EOL | EOL |
| 3.0 | 3.0.2 | Sep 7, 2021 | Mar 15, 2022 | 1613 days past EOL | EOL |
| 3.1 | 3.1.3 | Dec 9, 2021 | Jun 9, 2022 | 1527 days past EOL | EOL |
| 3.2 | 3.2.1 | Mar 15, 2022 | Sep 8, 2022 | 1436 days past EOL | EOL |
| 3.3 | 3.3.1 | Jun 9, 2022 | Dec 14, 2022 | 1339 days past EOL | EOL |
| 3.4 | 3.4.1 | Sep 8, 2022 | Mar 21, 2023 | 1242 days past EOL | EOL |
| 3.5 | 3.5.3 | Dec 14, 2022 | Jun 20, 2023 | 1151 days past EOL | EOL |
| 3.6 | 3.6.2 | Mar 21, 2023 | Oct 10, 2023 | 1039 days past EOL | EOL |
| 3.7 | 3.7.1 | Jun 20, 2023 | Dec 19, 2023 | 969 days past EOL | EOL |
| 3.8 | 3.8.0 | Oct 10, 2023 | Mar 22, 2024 | 875 days past EOL | EOL |
| 3.9 | 3.9.3 | Dec 19, 2023 | Jun 25, 2024 | 780 days past EOL | EOL |
| 3.10 | 3.10.1 | Mar 22, 2024 | Sep 19, 2024 | 694 days past EOL | EOL |
| 3.11 | 3.11.5 | Jun 25, 2024 | Dec 3, 2024 | 619 days past EOL | EOL |
| 3.12 | 3.12.1 | Sep 19, 2024 | Mar 19, 2025 | 513 days past EOL | EOL |
| 3.13 | 3.13.1 | Dec 3, 2024 | Jun 9, 2025 | 431 days past EOL | EOL |
| 3.14 | 3.14.0 | Mar 19, 2025 | Sep 9, 2025 | 339 days past EOL | EOL |
| 3.15 | 3.15.1 | Jun 9, 2025 | Dec 9, 2025 | 248 days past EOL | EOL |
| 3.16 | 3.16.3 | Sep 9, 2025 | Mar 10, 2026 | 157 days past EOL | EOL |
| 3.17 | 3.17.2 | Dec 9, 2025 | Jun 9, 2026 | 66 days past EOL | EOL |
| 3.18 | 3.18.2 | Mar 10, 2026 | TBD | Supported | Active |
| 3.19 | 3.19.1 | Jun 9, 2026 | TBD | Supported | Active |
Live EOL badge for your README — updates automatically at every build.
[](https://endoflife.ai/foreman)
What does Foreman end of life mean for your organization?
When a version of Foreman 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 Foreman 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 Foreman 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 Foreman versions. This is a bridge, not a permanent solution — plan your migration in parallel.
Foreman has 47 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 Foreman 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."