Cfengine · Lifecycle Status

Cfengine End of Life (EOL) Dates & Support Timeline

Complete end-of-life dates, support windows, and security status for all Cfengine versions. Data sourced from endoflife.date and official vendor documentation. Updated at every deploy.

Cfengine 3.24.4 is actively supported. Next EOL: version 3.24 on July 31, 2027.
Latest Active
3.24.4
3.24 series
Next EOL
3.24
Jul 31, 2027
Active Versions
2
of 13 total
EOL Versions
11
no longer patched
Release Cycle Timeline
EOL   Warning   Active   Today
Release cycle timeline 202020212022202320242025202620273.153.163.173.183.193.203.213.223.233.243.253.263.27TODAY
All Versions
VersionLatest ReleaseRelease DateEOL DateDaysStatus
3.15 LTS 3.15.7 Dec 19, 2019 Dec 31, 2022 1225 days past EOL EOL
3.16 3.16.0 Jun 23, 2020 Nov 19, 2020 1997 days past EOL EOL
3.17 3.17.0 Nov 19, 2020 Jun 24, 2021 1780 days past EOL EOL
3.18 LTS 3.18.8 Jun 24, 2021 Aug 31, 2024 616 days past EOL EOL
3.19 3.19.0 Dec 10, 2021 Jul 1, 2022 1408 days past EOL EOL
3.20 3.20.0 Jul 1, 2022 Dec 21, 2022 1235 days past EOL EOL
3.21 LTS 3.21.8 Dec 21, 2022 Dec 31, 2025 129 days past EOL EOL
3.22 3.22.0 Jun 16, 2023 Dec 5, 2023 886 days past EOL EOL
3.23 3.23.0 Dec 5, 2023 Jul 22, 2024 656 days past EOL EOL
3.24 LTS 3.24.4 Jul 22, 2024 Jul 31, 2027 448 days remaining Active
3.25 3.25.0 Jan 6, 2025 May 20, 2025 354 days past EOL EOL
3.26 3.26.0 May 20, 2025 Jan 9, 2026 120 days past EOL EOL
3.27 LTS 3.27.1 Jan 9, 2026 Already EOL Supported Active

What does Cfengine end of life mean for your organization?

When a Cfengine 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 Cfengine 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 Cfengine?
The next Cfengine version reaching EOL is 3.24 on July 31, 2027. See the full table above for all version EOL dates.
What is the latest supported version of Cfengine?
The latest active version of Cfengine is 3.24.4. Always verify against the table above as support windows can change.
What happens when Cfengine reaches end of life?
When Cfengine 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 Cfengine?
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 Cfengine 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 →