Foreman · Lifecycle Status

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.

Foreman 3.17.2 is actively supported. No versions approaching EOL in the next 6 months.
Latest Active
3.17.2
3.17 series
Next EOL
None upcoming
Active Versions
2
of 48 total
EOL Versions
46
no longer patched
Release Cycle Timeline
EOL   Warning   Active   Today
Release cycle timeline 20142015201620172018201920202021202220232024202520261.21.31.41.51.61.71.81.91.101.111.121.131.141.151.161.171.181.191.201.211.221.231.242.02.12.22.32.42.53.03.13.23.33.43.53.63.73.83.93.103.113.123.133.143.153.163.173.18TODAY
All Versions
VersionLatest ReleaseRelease DateEOL DateDaysStatus
1.2 1.2.3 Jul 1, 2013 Jan 29, 2014 4483 days past EOL EOL
1.3 1.3.2 Oct 14, 2013 May 9, 2014 4383 days past EOL EOL
1.4 1.4.5 Jan 29, 2014 Sep 10, 2014 4259 days past EOL EOL
1.5 1.5.3 May 9, 2014 Dec 2, 2014 4176 days past EOL EOL
1.6 1.6.3 Sep 10, 2014 Apr 28, 2015 4029 days past EOL EOL
1.7 1.7.5 Dec 2, 2014 Aug 18, 2015 3917 days past EOL EOL
1.8 1.8.4 Apr 28, 2015 Dec 23, 2015 3790 days past EOL EOL
1.9 1.9.3 Aug 18, 2015 Mar 31, 2016 3691 days past EOL EOL
1.10 1.10.4 Dec 23, 2015 Jul 8, 2016 3592 days past EOL EOL
1.11 1.11.4 Mar 31, 2016 Oct 5, 2016 3503 days past EOL EOL
1.12 1.12.4 Jul 8, 2016 Jan 13, 2017 3403 days past EOL EOL
1.13 1.13.4 Oct 5, 2016 May 9, 2017 3287 days past EOL EOL
1.14 1.14.3 Jan 13, 2017 Nov 29, 2017 3083 days past EOL EOL
1.15 1.15.7 May 9, 2017 Apr 11, 2018 2950 days past EOL EOL
1.16 1.16.2 Nov 29, 2017 Jul 12, 2018 2858 days past EOL EOL
1.17 1.17.4 Apr 11, 2018 Aug 30, 2018 2809 days past EOL EOL
1.18 1.18.3 Jul 12, 2018 Nov 15, 2018 2732 days past EOL EOL
1.19 1.19.1 Aug 30, 2018 Feb 26, 2019 2629 days past EOL EOL
1.20 1.20.3 Nov 15, 2018 Jul 2, 2019 2503 days past EOL EOL
1.21 1.21.4 Feb 26, 2019 Sep 18, 2019 2425 days past EOL EOL
1.22 1.22.2 Jun 4, 2019 Dec 9, 2019 2343 days past EOL EOL
1.23 1.23.2 Sep 10, 2019 Apr 2, 2020 2228 days past EOL EOL
1.24 1.24.3 Dec 9, 2019 Jul 2, 2020 2137 days past EOL EOL
2.0 2.0.3 Apr 2, 2020 Oct 28, 2020 2019 days past EOL EOL
2.1 2.1.4 Jul 2, 2020 Dec 1, 2020 1985 days past EOL EOL
2.2 2.2.3 Oct 28, 2020 Mar 19, 2021 1877 days past EOL EOL
2.3 2.3.5 Dec 1, 2020 Jun 9, 2021 1795 days past EOL EOL
2.4 2.4.1 Mar 19, 2021 Sep 7, 2021 1705 days past EOL EOL
2.5 2.5.4 Jun 2, 2021 Dec 9, 2021 1612 days past EOL EOL
3.0 3.0.2 Sep 7, 2021 Mar 15, 2022 1516 days past EOL EOL
3.1 3.1.3 Dec 9, 2021 Jun 9, 2022 1430 days past EOL EOL
3.2 3.2.1 Mar 15, 2022 Sep 8, 2022 1339 days past EOL EOL
3.3 3.3.1 Jun 9, 2022 Dec 14, 2022 1242 days past EOL EOL
3.4 3.4.1 Sep 8, 2022 Mar 21, 2023 1145 days past EOL EOL
3.5 3.5.3 Dec 14, 2022 Jun 20, 2023 1054 days past EOL EOL
3.6 3.6.2 Mar 21, 2023 Oct 10, 2023 942 days past EOL EOL
3.7 3.7.1 Jun 20, 2023 Dec 19, 2023 872 days past EOL EOL
3.8 3.8.0 Oct 10, 2023 Mar 22, 2024 778 days past EOL EOL
3.9 3.9.3 Dec 19, 2023 Jun 25, 2024 683 days past EOL EOL
3.10 3.10.1 Mar 22, 2024 Sep 19, 2024 597 days past EOL EOL
3.11 3.11.5 Jun 25, 2024 Dec 3, 2024 522 days past EOL EOL
3.12 3.12.1 Sep 19, 2024 Mar 19, 2025 416 days past EOL EOL
3.13 3.13.1 Dec 3, 2024 Jun 9, 2025 334 days past EOL EOL
3.14 3.14.0 Mar 19, 2025 Sep 9, 2025 242 days past EOL EOL
3.15 3.15.1 Jun 9, 2025 Dec 9, 2025 151 days past EOL EOL
3.16 3.16.3 Sep 9, 2025 Mar 10, 2026 60 days past EOL EOL
3.17 3.17.2 Dec 9, 2025 Already EOL Supported Active
3.18 3.18.1 Mar 10, 2026 Already EOL Supported Active

What does Foreman end of life mean for your organization?

When a Foreman version 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.

Check your full stack for EOL risk

Upload requirements.txt, package.json, or Gemfile — full EOL report instantly.

Open Stack Scanner →
Frequently Asked Questions
What is the end-of-life date for Foreman?
See the full table above for all Foreman version EOL dates.
What is the latest supported version of Foreman?
The latest active version of Foreman is 3.17.2. Always verify against the table above as support windows can change.
What happens when Foreman reaches end of life?
When Foreman reaches end of life, the vendor stops issuing security patches. Any CVEs disclosed after the EOL date accumulate indefinitely with no patch path — creating an ever-growing attack surface that most vulnerability scanners do not flag.
How do I check if I'm running an EOL version of Foreman?
Check your current version against the table above. If your version's EOL date has passed, you are running unsupported software. You can also use the endoflife.ai Stack Scanner to check your entire dependency file at once.
Is there extended support available for EOL Foreman versions?
Some vendors offer extended support for EOL software. Contact the original vendor or check with enterprise support providers for options.

Related Products

Data from endoflife.date API · endoflife.date · Generated at build time · How we source data →