Foreman 3.2 · Version Status
Foreman 3.2 End of Life Date
Foreman 3.2 end-of-life date, support status, and CVE risk. Data from endoflife.date and official vendor documentation.
⚠
Foreman 3.2 is past end of life. This version no longer receives security patches. 1339 days past EOL — migrate to a supported version immediately.
EOL Date
Sep 8, 2022
1339 days past EOL
Latest Release
3.2.1
Standard release
Release Date
Mar 15, 2022
Foreman 3.2 series
| Version | Latest | EOL Date | Status |
|---|
| 1.2 |
1.2.3 |
Jan 29, 2014 |
EOL |
| 1.3 |
1.3.2 |
May 9, 2014 |
EOL |
| 1.4 |
1.4.5 |
Sep 10, 2014 |
EOL |
| 1.5 |
1.5.3 |
Dec 2, 2014 |
EOL |
| 1.6 |
1.6.3 |
Apr 28, 2015 |
EOL |
| 1.7 |
1.7.5 |
Aug 18, 2015 |
EOL |
| 1.8 |
1.8.4 |
Dec 23, 2015 |
EOL |
| 1.9 |
1.9.3 |
Mar 31, 2016 |
EOL |
What does Foreman 3.2 end of life mean?
When Foreman 3.2 reaches end of life, the maintainers stop issuing security patches for this version. CVEs discovered after the EOL date are publicly disclosed on the National Vulnerability Database with no patch available. Exploit code frequently appears on GitHub within days of disclosure.
The CVE blind spot: Most vulnerability scanners check for known CVEs but do not flag the ongoing accumulation of unpatched vulnerabilities in EOL software versions. Running Foreman 3.2 past its EOL date creates a permanently growing attack surface that standard security tooling will not surface.
Migrate to Foreman 3.18 or implement compensating controls — network segmentation, enhanced monitoring, restricted access — while migration is underway.
Frequently Asked Questions
When does Foreman 3.2 reach end of life?
Foreman 3.2 reached end of life on September 8, 2022. This version is no longer receiving security patches.
Is Foreman 3.2 still supported?
No. Foreman 3.2 reached end of life on September 8, 2022 and is no longer receiving security patches.
What should I upgrade to from Foreman 3.2?
The recommended upgrade from Foreman 3.2 is
Foreman 3.18 — the latest actively supported version. Check the
Foreman full timeline for all supported versions.
What are the security risks of running Foreman 3.2 past EOL?
When Foreman 3.2 reaches end of life, the maintainers stop issuing security patches. Any CVEs disclosed after the EOL date accumulate with no remediation path. Most vulnerability scanners do not flag this — it is the CVE blind spot. Organizations running EOL Foreman should migrate immediately or implement compensating controls.