Puppet Enterprise End of Life (EOL) Dates & Support Timeline
Complete end-of-life dates, support windows, and security status for all Puppet Enterprise versions. Dates read at the vendor's own lifecycle pages (puppet.com). Updated at every deploy.
Puppet Enterprise 2026 is supported, with no end-of-life or end-of-support date announced yet. The next Puppet Enterprise version to reach end of life is 2023.8, on April 27, 2027. 1 of 4 tracked Puppet Enterprise versions is past end of life; the most recent to reach it, 2021.7, did so on February 25, 2025. The full Puppet Enterprise lifecycle, with every version's release and end-of-support date, is in the table below.
Running an EOL version? Get matched with support options — free ↓GET https://api.endoflife.ai/v1/score/puppet-enterprise/2023.8 returns this version's end-of-life date, its source and the EOL Risk Score as JSON. Get a free API key (150 requests a day, no expiry).| Version | Latest Release | Release Date | EOL Date | Days | Status |
|---|---|---|---|---|---|
| 2021.7 LTS | 2021.7.10 | Aug 30, 2022 | Feb 25, 2025 | 631 days past EOL | EOL |
| 2023.8 LTS | 2023.8.13 | Aug 27, 2024 | Apr 27, 2027 | 160 days remaining | Warning |
| 2025 | 2025.12.1 | Dec 12, 2024 | Oct 15, 2027 | 331 days remaining | Active |
| 2026 | 2026.0.1 | Oct 15, 2026 | TBD | Supported | Active |
[](https://endoflife.ai/puppet-enterprise)
Puppet Enterprise lifecycle status — the real story
Puppet Enterprise (PE) is Perforce's commercial configuration management platform, built on Puppet Core. It is tracked here apart from Puppet, which covers open source Puppet and Puppet Core. Perforce publishes the dates on its Puppet Enterprise Platform Support Lifecycle page. Starting with PE 2026, releases follow a Latest / Latest-1 model: the Latest major version "receives full active support for 12 months from its release date, or until a newer major version is released, whichever is later", and the previous major version then "transitions to limited active support for 12 months", which "includes security updates, defect fixes, minor changes, and technical support". PE 2023.8 is the last release under the older long-term support model; Perforce labels it LTS (Final).
Perforce's name for the end of a track is end of maintenance and support (EOMS). Its policy says versions that have reached EOMS "are no longer eligible for software support or maintenance, including and without limitation, new features, defect fixes, or security patches", and that once PE 2023.8 reaches EOMS, "any Puppet Enterprise version older than Latest-1 will be considered EOMS". The components inside a release follow the same dates: "Puppet Core components included in Puppet Enterprise, such as Puppet and Facter, follow the same maintenance and end-of-life timelines as the Puppet Enterprise release tracks in which they are included." Puppet Enterprise is in CISA's Known Exploited Vulnerabilities catalog for CVE-2026-115731; Perforce's advisory lists fixed releases for the 2026, 2025 and 2023.8 tracks and names no older track.
Field mapping: support is the day limited active support begins, which is the end of full active support; Perforce prints it only for the Latest-1 track. eol is the EOMS day. The Latest track has neither date until Perforce publishes them, and the long-term support tracks have an EOMS day only. Release days and the newest release in each track come from Perforce's release list; the release notes print the month only. The short-term support releases between the long-term support lines ended when the next release shipped and are not listed.
Puppet Enterprise release and support pattern
Across the 4 release lines with a published release date, Puppet Enterprise has shipped a new line roughly every 1.8 years (median interval). A line typically stays supported for about 2.7 years from its release to its end-of-life date (measured on the 3 lines with both dates published). 2 of the 4 tracked lines are designated long-term support, which is where the longer windows sit.
Of the 4 release lines tracked, 1 is past end of life and 3 are still within support. The newest line, 2026, was released October 15, 2026. The next scheduled end of life is 2023.8 on April 27, 2027 — 160 days from this build. The longest-supported line currently published is 2025, to October 15, 2027.
Computed from the tracked release data at every build — the figures above are the dates in the table, restated, not an editorial estimate.
Puppet Enterprise security intelligence
CISA KEV history: Puppet Enterprise is named in CISA's Known Exploited Vulnerabilities catalog 1 time, most recently on 2026-11-17. Derived from CISA's live catalog at every build.
What does Puppet Enterprise end of life mean for your organization?
When a version of Puppet Enterprise reaches end of life, the vendor's standard security patches for that version stop. Vulnerabilities found after that date are still published on the National Vulnerability Database, exploit code often becomes public, and systems on that version stay exposed until they are upgraded or covered by extended support.
The CVE blind spot: A CVE-based scan does not show the accumulation of unpatched vulnerabilities in EOL software. Some scanners flag unsupported versions of common products, but coverage varies, and none of them give you the date in advance. With a zero-day, nobody knows about the vulnerability. With EOL software, the vulnerability is public — listed, rated, and often weaponized — but the vendor's policy provides no patch for the ended version. This is one of the most dangerous gaps in enterprise security posture.
Organizations running EOL Puppet Enterprise 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 Puppet Enterprise 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, check whether the vendor or a third party sells extended support with security patches for your Puppet Enterprise version; coverage varies by product and version. Where it exists it is a bridge, not a permanent solution — plan your migration in parallel.
Puppet Enterprise has 1 version 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 Puppet Enterprise 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."