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.
| Version | Latest Release | Release Date | EOL Date | Days | Status |
|---|---|---|---|---|---|
| 1.2 | 1.2.3 | Jul 1, 2013 | Jan 29, 2014 | 4528 days past EOL | EOL |
| 1.3 | 1.3.2 | Oct 14, 2013 | May 9, 2014 | 4428 days past EOL | EOL |
| 1.4 | 1.4.5 | Jan 29, 2014 | Sep 10, 2014 | 4304 days past EOL | EOL |
| 1.5 | 1.5.3 | May 9, 2014 | Dec 2, 2014 | 4221 days past EOL | EOL |
| 1.6 | 1.6.3 | Sep 10, 2014 | Apr 28, 2015 | 4074 days past EOL | EOL |
| 1.7 | 1.7.5 | Dec 2, 2014 | Aug 18, 2015 | 3962 days past EOL | EOL |
| 1.8 | 1.8.4 | Apr 28, 2015 | Dec 23, 2015 | 3835 days past EOL | EOL |
| 1.9 | 1.9.3 | Aug 18, 2015 | Mar 31, 2016 | 3736 days past EOL | EOL |
| 1.10 | 1.10.4 | Dec 23, 2015 | Jul 8, 2016 | 3637 days past EOL | EOL |
| 1.11 | 1.11.4 | Mar 31, 2016 | Oct 5, 2016 | 3548 days past EOL | EOL |
| 1.12 | 1.12.4 | Jul 8, 2016 | Jan 13, 2017 | 3448 days past EOL | EOL |
| 1.13 | 1.13.4 | Oct 5, 2016 | May 9, 2017 | 3332 days past EOL | EOL |
| 1.14 | 1.14.3 | Jan 13, 2017 | Nov 29, 2017 | 3128 days past EOL | EOL |
| 1.15 | 1.15.7 | May 9, 2017 | Apr 11, 2018 | 2995 days past EOL | EOL |
| 1.16 | 1.16.2 | Nov 29, 2017 | Jul 12, 2018 | 2903 days past EOL | EOL |
| 1.17 | 1.17.4 | Apr 11, 2018 | Aug 30, 2018 | 2854 days past EOL | EOL |
| 1.18 | 1.18.3 | Jul 12, 2018 | Nov 15, 2018 | 2777 days past EOL | EOL |
| 1.19 | 1.19.1 | Aug 30, 2018 | Feb 26, 2019 | 2674 days past EOL | EOL |
| 1.20 | 1.20.3 | Nov 15, 2018 | Jul 2, 2019 | 2548 days past EOL | EOL |
| 1.21 | 1.21.4 | Feb 26, 2019 | Sep 18, 2019 | 2470 days past EOL | EOL |
| 1.22 | 1.22.2 | Jun 4, 2019 | Dec 9, 2019 | 2388 days past EOL | EOL |
| 1.23 | 1.23.2 | Sep 10, 2019 | Apr 2, 2020 | 2273 days past EOL | EOL |
| 1.24 | 1.24.3 | Dec 9, 2019 | Jul 2, 2020 | 2182 days past EOL | EOL |
| 2.0 | 2.0.3 | Apr 2, 2020 | Oct 28, 2020 | 2064 days past EOL | EOL |
| 2.1 | 2.1.4 | Jul 2, 2020 | Dec 1, 2020 | 2030 days past EOL | EOL |
| 2.2 | 2.2.3 | Oct 28, 2020 | Mar 19, 2021 | 1922 days past EOL | EOL |
| 2.3 | 2.3.5 | Dec 1, 2020 | Jun 9, 2021 | 1840 days past EOL | EOL |
| 2.4 | 2.4.1 | Mar 19, 2021 | Sep 7, 2021 | 1750 days past EOL | EOL |
| 2.5 | 2.5.4 | Jun 2, 2021 | Dec 9, 2021 | 1657 days past EOL | EOL |
| 3.0 | 3.0.2 | Sep 7, 2021 | Mar 15, 2022 | 1561 days past EOL | EOL |
| 3.1 | 3.1.3 | Dec 9, 2021 | Jun 9, 2022 | 1475 days past EOL | EOL |
| 3.2 | 3.2.1 | Mar 15, 2022 | Sep 8, 2022 | 1384 days past EOL | EOL |
| 3.3 | 3.3.1 | Jun 9, 2022 | Dec 14, 2022 | 1287 days past EOL | EOL |
| 3.4 | 3.4.1 | Sep 8, 2022 | Mar 21, 2023 | 1190 days past EOL | EOL |
| 3.5 | 3.5.3 | Dec 14, 2022 | Jun 20, 2023 | 1099 days past EOL | EOL |
| 3.6 | 3.6.2 | Mar 21, 2023 | Oct 10, 2023 | 987 days past EOL | EOL |
| 3.7 | 3.7.1 | Jun 20, 2023 | Dec 19, 2023 | 917 days past EOL | EOL |
| 3.8 | 3.8.0 | Oct 10, 2023 | Mar 22, 2024 | 823 days past EOL | EOL |
| 3.9 | 3.9.3 | Dec 19, 2023 | Jun 25, 2024 | 728 days past EOL | EOL |
| 3.10 | 3.10.1 | Mar 22, 2024 | Sep 19, 2024 | 642 days past EOL | EOL |
| 3.11 | 3.11.5 | Jun 25, 2024 | Dec 3, 2024 | 567 days past EOL | EOL |
| 3.12 | 3.12.1 | Sep 19, 2024 | Mar 19, 2025 | 461 days past EOL | EOL |
| 3.13 | 3.13.1 | Dec 3, 2024 | Jun 9, 2025 | 379 days past EOL | EOL |
| 3.14 | 3.14.0 | Mar 19, 2025 | Sep 9, 2025 | 287 days past EOL | EOL |
| 3.15 | 3.15.1 | Jun 9, 2025 | Dec 9, 2025 | 196 days past EOL | EOL |
| 3.16 | 3.16.3 | Sep 9, 2025 | Mar 10, 2026 | 105 days past EOL | EOL |
| 3.17 | 3.17.2 | Dec 9, 2025 | TBD | Supported | Active |
| 3.18 | 3.18.1 | Mar 10, 2026 | TBD | Supported | Active |
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.
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.
We work with vetted extended support vendors. Tell us what you need and we'll connect you with the right provider.
Contact Us →