Puppet Enterprise Vulnerability CVE-2026-115731: CISA Lists the Exploited Flaw, the Certificate Key Risk, and the Fixed Versions to Install
CISA added Puppet Enterprise flaw CVE-2026-115731 (CVSS 9.4) to its exploited list on November 17. Here is what is confirmed, what is not known, and the fixed versions to install this week.
Where Worldwide
On this page 8 sections
A serious flaw in Perforce Puppet Enterprise, tracked as CVE-2026-115731, is being used in real attacks, and CISA added it to its Known Exploited Vulnerabilities (KEV) catalog on November 17. If your company or your IT provider runs Puppet, patch the Puppet server this week. A successful attack could expose the server's certificate-signing key, which would let an attacker create certificates your own systems trust.
This post covers what has been confirmed, what has not, which versions fix it, and what to check before the week is out.
What happened with CVE-2026-115731
CISA's KEV catalog describes the problem this way: Perforce Puppet Enterprise has a deserialization of untrusted data vulnerability in Puppet's report-processing code. Put simply, the part of Puppet that reads incoming reports can be tricked into handling data it should never trust.
SecurityWeek reports that the flaw has a CVSS score of 9.4, which puts it in the critical range. According to the same report, CVE-2026-115731 was flagged as exploited on November 4. CISA added it to the KEV catalog on November 17 and is urging federal agencies to patch it within two weeks, in line with BOD 26-04.
Perforce has released fixed versions of both Puppet Enterprise and Puppet Core. SecurityWeek says those releases contain patches for two flaws. The sources we checked do not identify the second flaw, so we can't tell you anything more about it.
What is confirmed and what is not
| Point | Status | Where it comes from |
|---|---|---|
| The flaw is a deserialization of untrusted data issue in Puppet's report-processing code | Confirmed | CISA KEV catalog |
| The flaw is in CISA's Known Exploited Vulnerabilities catalog | Confirmed | CISA KEV catalog, date reported by SecurityWeek |
| CVSS score of 9.4 | Reported | SecurityWeek |
| Flagged as exploited on November 4 | Reported | SecurityWeek |
| Fixed versions of Puppet Enterprise, Enterprise Advanced and Core are available | Reported | SecurityWeek |
| Who is behind the attacks | Not known | Not stated in the sources we checked |
| How many organizations were hit | Not known | Not stated in the sources we checked |
| Whether an attacker needs a login first | Not known | Not stated in the sources we checked |
| Whether a workaround exists | Not known | Not stated in the sources we checked |
One caution: the primary source here is the CISA catalog entry. The vendor's own advisory wasn't among the pages we verified, so the version numbers and the score come from SecurityWeek's reporting. Before you upgrade, confirm the exact build against Perforce's release notes.
Why the certificate risk matters
SecurityWeek describes the impact this way: "A successful attack could expose the server's certificate-signing key, allow an attacker to issue trusted certificates".
That matters because certificates are how systems prove who they are to each other. If someone outside your company can issue certificates your environment already trusts, they may be able to pass as one of your own machines. A Puppet server usually sits at the centre of an IT environment, with many other machines answering to it. A problem there can reach much further than a single bad server.
The sources do not say whether patching alone is enough if the signing key has already been exposed, and they give no official guidance on replacing it. Ask Perforce or your provider about this directly.
Which Puppet versions fix CVE-2026-115731
SecurityWeek lists these versions as containing the patches:
| Product | Fixed versions |
|---|---|
| Puppet Enterprise | 2026.0.1, 2025.12.1, 2023.8.13 |
| Puppet Enterprise Advanced | 2026.0.1, 2025.12.1, 2023.8.13 |
| Puppet Core | 9.1.3, 8.22.2 |
If you run a release line that isn't on this list, the sources do not say which version you should move to. Ask Perforce before you assume you are covered.
What to do this week
- Find every Puppet server. Check whether your company, a developer or a managed provider runs Puppet Enterprise, Puppet Enterprise Advanced or Puppet Core anywhere, including test and old systems.
- Check the installed version. Compare it with the table above. A version older than the fixed release in its line should be treated as exposed.
- Install the fixed version. For Puppet Enterprise and Enterprise Advanced, that is 2026.0.1, 2025.12.1 or 2023.8.13. For Puppet Core, it is 9.1.3 or 8.22.2.
- Confirm the patch is actually running. A downloaded update isn't the same as an installed one. Our post on why updated is not the same as patched explains why.
- Ask about the signing key. If the server was exposed before you patched, ask Perforce or your provider whether the certificate-signing key should be treated as compromised.
- Review what the server did recently. Look for unexpected certificates, new machines you don't recognize, or changes nobody on your team made since early November.
- Write down who owns this system. If nobody can say who patches the Puppet server, fix that gap now.
Why this matters for a company network
Tools like Puppet exist so one team can manage a lot of systems from one place. That is also what makes them a valuable target. If an attacker controls the central server, they don't have to break into each machine one at a time. The trusted-certificate risk makes that worse, because what the attacker creates can look legitimate to your own systems.
Many businesses don't know they run Puppet at all. It may have been set up years ago by a contractor, or it may come bundled with a managed hosting arrangement. That is the same question we raised in who is patching the software that runs your business: if nobody is clearly responsible, a KEV listing can go unnoticed until it is too late.
Puppet Enterprise vulnerability questions people are asking
Is CVE-2026-115731 being exploited?
Yes. CISA has added it to its Known Exploited Vulnerabilities catalog. SecurityWeek reports it was flagged as exploited on November 4.
What is the fixed version of Puppet Enterprise?
Puppet Enterprise and Puppet Enterprise Advanced 2026.0.1, 2025.12.1 and 2023.8.13, according to SecurityWeek. Check the exact build against Perforce's release notes.
Is Puppet Core affected?
SecurityWeek reports that Puppet Core 9.1.3 and 8.22.2 contain the patches, so Puppet Core users should update as well.
Is this a Puppet RCE?
You may see it called a Puppet RCE in headlines. The CISA entry describes it as a deserialization of untrusted data flaw in report-processing code. Beyond that, the sources we checked only spell out the certificate-signing key risk quoted above.
Who is behind the attacks?
Not known. The sources we checked do not name an attacker or say how many organizations were targeted.
Do I need to patch if I am not a federal agency?
Yes. CISA's two-week deadline applies to federal agencies, but a flaw being used in real attacks is just as dangerous on a company network.
Is there a workaround?
The sources we checked do not mention one. Treat installing the fixed version as the fix.
The bigger lesson
The systems that manage your other systems deserve the most attention, not the least. A configuration server that runs quietly for years can end up holding the keys to everything else on your network. Every business should know where those servers are, who patches them, and how quickly.
If you want help finding and locking down systems like this, see our security hardening service or request a quote.
Get security alerts like this by email, with our free checklist, at /security-alerts.
Sources: CISA Known Exploited Vulnerabilities catalog; SecurityWeek.
Have a question about this article?
Ask it here and we will answer you directly by email. Questions are private, never posted.
Security alerts by email
Hear about the next one first.
When attackers start using a flaw in software businesses run on, we email what it is, whether it touches you and what to do that week, with a round-up of our latest security writing. Free, one-click unsubscribe. You get the checklist straight away: 12 things to secure this week.
Want a result like this?
Security alerts, breaches and the technology a business runs on: what happened, who it affects and what to do.
Get a Tech QuoteKeep reading
Cursor Security Incident: Malicious Claude Code Extension Versions 2.1.312 and 2.1.313 Tried to Plant an SSH Backdoor, Credentials Exposed, and What to Check This Week
Cursor confirms an attacker obtained an access key, malicious Claude Code extension versions 2.1.312 and 2.1.3...
Agent Framework PyPI Malware
Attackers published malicious releases of Microsoft's official Agent Framework package on PyPI on November 17,...
Optimizely Supply Chain Attack: OPTIMJACK Put Card Skimmers and Crypto Clippers in 188 Optimizely Scripts, What Is Confirmed and What to Check This Week
Attackers exploited a vulnerability in Optimizely Experimentation to add card-skimming and crypto-clipping Jav...