endoflife.ai
Puppet Exploited & Unpatchable EOL Watch

Puppet CVE-2026-115731 on CISA KEV: Fixed Versions and EOL Lines

By Scott Bissett  ·  Published: November 18, 2026  ·  EOL Watch — news analysis  ·  Read at Perforce's advisory, release notes and lifecycle pages, the CVE record, CISA's catalog and our tracked Puppet data

Puppet has a critical flaw that lets a managed machine run code on the Puppet Server, and CISA put it on the Known Exploited Vulnerabilities catalog on November 17, 2026. Perforce, which owns Puppet, names five fixed releases in its advisory: Puppet Enterprise 2026.0.1, 2025.12.1 and 2023.8.13, and Puppet Core 9.1.3 and 8.22.2. That list is the whole of what Perforce has said. Puppet 7, Puppet Enterprise 2021.7 and open source Puppet 8 are not in it, as fixed or as affected.

The lifecycle fact that decides what you do next. Puppet 7 and Puppet Core 7 have been end of life since April 2025. Puppet Enterprise 2021.7, the release line built on Puppet 7, passed its end of maintenance and support on February 25, 2025. Open source Puppet 8 stopped at 8.10.0, released in October 2024; every Puppet 8 release since then is Puppet Core, which Perforce ships from a protected repository. A server on any of those three has no fixed build named for it.
Quick answer: Puppet 9 is supported, with no end-of-life or end-of-support date announced yet. 5 of 7 tracked Puppet versions are past end of life; the most recent to reach it, 7, did so in April 2025. Every Puppet version's release and end-of-support date is on the Puppet lifecycle page.

What the flaw is

CVE-2026-115731 is a deserialization flaw in Puppet's report processing. The CVE record, written by Perforce, says it “allows a client that holds any CA-signed agent certificate to execute arbitrary code on the Puppet Server as its service user by submitting a report containing a crafted rich-data type via PUT request.” It continues: “Where the certificate authority autosigns requests without strong verification, an unauthenticated network attacker can obtain such a certificate.” Perforce scores it 9.4, Critical, under CVSS 4.0.

The Puppet Server holds the catalog for every node it manages, so code execution there reaches the whole estate. CISA's entry names the product as Perforce Puppet Enterprise, lists ransomware use as Unknown, and gives federal civilian agencies until December 1. The fixed releases also close a second flaw, CVE-2026-115732, an authorization bypass that Perforce's release notes describe as letting a managed machine impersonate another.

Running Puppet past end of life?
Extended support past the official EOL date exists for many products in this position — whether it covers Puppet 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.” Free, no obligation.

Free · No obligation · Independent — we track the dates, vendors don’t pay for placement · dates verified against vendor sources. See all support options →

Every line against the fix list

The affected ranges and fixed releases below are Perforce's advisory, word for word. The status column is from Perforce's lifecycle pages and release notes. Perforce prints the month, not the day, for every Puppet Core release: the fixed builds are dated November 2026.

LinePerforce's statusAffected range in the advisoryFixed release
Puppet Enterprise 2026.ySupported, the “Latest” track2026.0.0 before 2026.0.12026.0.1 (Puppet Core 9.1.3)
Puppet Enterprise 2025.yLimited active support, the “Latest-1” track2025.0.0 before 2025.12.12025.12.1 (Puppet Core 8.22.2)
Puppet Enterprise 2023.8.zSupported until its end date, below2023.8.0 before 2023.8.132023.8.13 (Puppet Core 8.22.2)
Puppet Core 9Supported, proprietary9.0.0 before 9.1.39.1.3
Puppet Core 8Supported, proprietary8.x before 8.22.28.22.2
Open source Puppet 8 (8.10.0 and earlier)“no longer maintained by Perforce”Not named as open sourceNone in the public repositories
Puppet 7 and Puppet Core 7End of life since April 2025Not namedNone named
Puppet Enterprise 2021.7 and olderPast end of maintenance and supportNot namedNone named

The advisory's wording for Puppet 8 is “Puppet Core 8.x before 8.22.2.” Puppet Core begins at 8.11.0; the releases before it, up to 8.10.0, were published as open source Puppet. Perforce does not say whether those earlier open source releases are inside that range.

What Perforce has not said. It has not said Puppet 7, Puppet Core 7 or Puppet Enterprise 2021.7 is affected, and it has not said they are unaffected. No Perforce page we read mentions them next to this CVE. The CVE record lists one product, Puppet Enterprise, with a default status of affected and no version below 2023.8.0. We are not calling those lines vulnerable or safe. We are saying they are end of life, they are outside the advisory, and Perforce's own policy for versions past end of maintenance and support is that they are “no longer eligible for software support or maintenance, including and without limitation, new features, defect fixes, or security patches.”

Open source Puppet 8: the fix is in Puppet Core

In November 2024 Perforce announced that from early 2025 it would “ship any new binaries and packages developed by our team to a private, hardened, and controlled location.” That product is Puppet Core. Its first release note, for 8.11.0 in February 2025, says: “Open source Puppet remains available but is no longer maintained by Perforce.” It points readers who run open source Puppet in production to Puppet Core for “the latest features, fixes, and security updates.”

Perforce's public repositories match that. When we read them for this article, the newest open source Puppet 8 release in Perforce's public source repository and public package repository was 8.10.0. The fix for CVE-2026-115731 is in Puppet Core 8.22.2 and 9.1.3, whose notes read: “Fixed CVE-2026-115731, a vulnerability that could allow arbitrary code execution on the Puppet Server host.” Perforce says Puppet Core “is available under a free Developer License for use on up to 25 nodes”; above that it is a commercial licence.

Perforce's pages are not consistent on one point. The 8.11.0 release note says open source Puppet is no longer maintained by Perforce. The Puppet Core product page answers its own question, whether open source Puppet is still free and being maintained, with “Yes.” We found no Perforce statement that open source Puppet receives security fixes.

The community fork has made its own statement. OpenVox, which is not Perforce and has its own interest here, wrote on the oss-security list that it had released updates for two vulnerabilities “that affect all known OpenVox and Puppet versions and implementations” and recommended that “any usage of OSS Puppet should be migrated to OpenVox as soon as possible, as Puppet will not be receiving security updates.” Those are OpenVox's words. Perforce has not confirmed either half.

Puppet Enterprise: the three supported tracks

These rows are Perforce's Puppet Enterprise support lifecycle page. The track names, including “LTS (Final)” for 2023.8, are Perforce's labels for Puppet Enterprise.

Puppet Enterprise versionPerforce's trackSupport statusFixed build for this CVE
PE 2026.y“Latest”Full active support2026.0.1
PE 2025.y“Latest-1”Limited active support until October 15, 20272025.12.1
PE 2023.8.z“LTS (Final)”Reaches end of maintenance and support on April 27, 20272023.8.13

Perforce prints two end dates for PE 2023.8. The lifecycle page above gives April 27, 2027. The Puppet Enterprise 2026 release notes tell PE 2023.8 customers they are in the overlap support period, which ends on February 27, 2027. Perforce has not reconciled the two. If you run PE 2023.8, plan your move to PE 2025 or 2026 against the earlier date.

Puppet 8 itself has no firm end date yet. Perforce's Puppet Core lifecycle page gives Puppet Core 8.x an end of life of “February 2028 (projected)” and Puppet Core 9.x “February 2029 (projected)”, and says each follows the end of maintenance and support of its Puppet Enterprise track. For Puppet Core 8.x that track is PE 2025.y, which the Puppet Enterprise page ends in October 2027. The two pages do not agree, so our Puppet page shows no end date for Puppet 8 or 9 until Perforce publishes a firm one.

What to do, by line

Puppet Enterprise 2026, 2025 or 2023.8: install 2026.0.1, 2025.12.1 or 2023.8.13. The CVE record's instruction is to upgrade “and restart puppet server so the fixed code is loaded.” An upgrade without the restart leaves the old code running.

Puppet Core 8 or 9: install 8.22.2 or 9.1.3, and restart Puppet Server.

Open source Puppet 8, on 8.10.0 or earlier: there is no newer open source build in Perforce's public repositories to install. Perforce's documented route is Puppet Core, free for development use on up to 25 nodes and licensed above that. Until the server is on a fixed build, look at how agent certificates are issued: the CVE record says an attacker needs a CA-signed agent certificate and that autosigning without strong verification lets an outsider get one.

Puppet 7, Puppet Core 7, or Puppet Enterprise 2021.7 and older: these lines are end of life and no fixed build is named for them. Perforce has not said whether they are affected. Do not wait for that answer to plan the move to a supported line, and apply the same care to certificate signing in the meantime.

Federal agencies: CISA's due date is December 1, 2026, under BOD 26-04. CISA's required action is to apply the vendor's mitigations or discontinue use of the product if mitigations are unavailable.

Frequently Asked Questions

Which Puppet versions fix CVE-2026-115731?

Perforce's advisory lists five fixed releases: Puppet Enterprise 2026.0.1, 2025.12.1 and 2023.8.13, and Puppet Core 9.1.3 and 8.22.2. The Puppet Enterprise releases bundle the fixed Puppet Core builds. The CVE record adds that Puppet Server must be restarted so the fixed code is loaded.

Is Puppet 7 affected by CVE-2026-115731?

Perforce has not said either way. Its advisory names Puppet Enterprise from 2023.8.0 and Puppet Core 8.x and 9.x, and nothing older. Puppet 7 and Puppet Core 7 reached end of life in April 2025, and Perforce's policy is that versions past end of maintenance and support are not eligible for security patches. The CVE record lists one product, Puppet Enterprise, with a default status of affected and no version below 2023.8.0. Treat a Puppet 7 server as unverified and unsupported, and plan the upgrade.

Does open source Puppet get the fix?

Not from Perforce's public repositories as we read them for this article: the newest open source Puppet 8 release there is 8.10.0, from October 2024. The fix ships in Puppet Core 8.22.2 and 9.1.3, which Perforce distributes from a protected repository. Perforce says Puppet Core is available under a free Developer License for use on up to 25 nodes, with a commercial licence above that. Its Puppet Core 8.11.0 release note says open source Puppet is no longer maintained by Perforce.

What is the CISA deadline for CVE-2026-115731?

CISA added CVE-2026-115731 to the Known Exploited Vulnerabilities catalog on November 17, 2026 with a due date of December 1, 2026 for federal civilian agencies. The entry names Perforce Puppet Enterprise and links Perforce's advisory. CISA lists ransomware use as Unknown.

Which Puppet Enterprise versions are still supported?

Perforce's lifecycle page lists three tracks. PE 2026.y is the current track. PE 2025.y is on limited active support until October 15, 2027. PE 2023.8.z reaches end of maintenance and support on April 27, 2027. Perforce's Puppet Enterprise 2026 release notes give PE 2023.8 an earlier day, saying its overlap support period ends on February 27, 2027; plan against the earlier one. PE 2021.7.z ended on February 25, 2025. All three supported tracks have a fixed build for CVE-2026-115731: 2026.0.1, 2025.12.1 and 2023.8.13.

Related

© 2026 endoflife.ai · How we verify our dates · API · About