The Library

Puppet Enterprise Vulnerability CVE-2026-115731: Exploited Flaw Lets Any Agent Certificate Run Code on Puppet Server, and the Fixed Versions to Install

Attackers are exploiting CVE-2026-115731, a critical flaw in Puppet Enterprise that lets any CA-signed agent certificate run code on the Puppet Server. Here are the fixed versions and what to check this week.

Elite Performance Exclusive LLC 6 min read

Where Worldwide

Puppet Enterprise Vulnerability CVE-2026-115731: Exploited Flaw Lets Any Agent Certificate Run Code on Puppet Server, and the Fixed Versions to Install
On this page 8 sections

Attackers are exploiting CVE-2026-115731, a critical remote code execution flaw in Perforce Puppet Enterprise. CISA has added it to its Known Exploited Vulnerabilities catalog. If your company or your IT provider runs Puppet, the risk is on the Puppet Server itself: any machine holding a CA-signed agent certificate can use this flaw to run its own code there.

Fixed versions are out. This post covers what is confirmed, what is only reported, what nobody has said yet, and what to do this week.

What is CVE-2026-115731?

CISA's catalog entry says the flaw "allows a client with any CA-signed agent certificate to execute arbitrary code on the Puppet Server as the service user".

In plain terms: machines managed by Puppet (the agents) prove who they are to the Puppet Server with certificates signed by its certificate authority. This flaw lets one of those trusted clients do far more than it should. Instead of taking instructions from the server, it can run code on the server. The description does not mention an administrator password. What an attacker needs is a certificate the server already trusts.

The code runs as the service user, which is the account the Puppet Server runs under. How much that account can reach depends on how your server is set up. The sources say nothing more about it.

Help Net Security describes it as "a critical remote code execution vulnerability in Perforce Puppet Enterprise".

Is CVE-2026-115731 being exploited?

Yes. Help Net Security reports: "Attackers are exploiting CVE-2026-115731". CISA lists the flaw in its Known Exploited Vulnerabilities catalog, in an entry dated Tuesday 17 November 2026, with the instruction to "Apply mitigations in accordance with vendor instructions". US federal agencies covered by the catalog have a due date of Tuesday 1 December 2026.

That deadline is set for federal agencies, but it works as a yardstick for everyone else too. If government networks get two weeks, a business running the same software should not take longer.

Which Puppet Enterprise versions are affected?

Help Net Security lists the affected and fixed versions below. The vendor's own advisory is not among the sources we could check for this post, so confirm these numbers against Perforce's advisory before you upgrade.

Product line Affected Fixed version
Puppet Enterprise 2023.8.0 2023.8.0 before 2023.8.13 2023.8.13
Puppet Enterprise 2025.0.0 2025.0.0 before 2025.12.1 2025.12.1
Puppet Enterprise 2026 2026.0.0 before 2026.0.1 2026.0.1
Puppet Core Not stated in our sources 9.1.3 or 8.22.2

The report gives the fixed releases for "Puppet Enterprise/Advanced", so the same version numbers apply if you run Puppet Advanced.

What is not known yet

  • Who is behind the attacks, and how many organizations have been hit. Neither source says.
  • How attackers got an agent certificate in the attacks seen so far, whether by stealing one from an enrolled machine or some other way.
  • What attackers did once their code was running on the Puppet Server.
  • Indicators of compromise, such as file names, addresses or log entries to search for. Our sources include none.
  • Which Puppet Core versions are affected. The sources name only the fixed Core versions.
  • The exact mitigations. CISA points to the vendor's instructions, and those instructions are not in our sources.

We will not guess at any of these. If Perforce or CISA publishes more, compare it with your own systems.

Why it matters for a business network

Every machine a configuration management server manages trusts it. That is the whole point: one place decides how servers and workstations are configured. It also makes that server one of the most valuable systems on the network to an attacker.

This flaw flips the usual direction of trust. Normally the server tells the agents what to do. Here, an agent, or anyone holding an agent's certificate, can run code on the server. That makes the Puppet Server only as safe as the least protected machine with a trusted certificate: an old test box, a forgotten virtual machine, a laptop that left with a former employee.

Many businesses do not run Puppet themselves. A managed provider or a contractor runs it for them. If that is you, the question is who patches it, and when.

What to do this week

  1. Find out whether you use Puppet. Ask your IT team or provider whether Puppet Enterprise, Puppet Advanced or Puppet Core runs anywhere in your environment, including servers someone else manages for you.
  2. Check the version against the table above.
  3. Upgrade. Puppet Enterprise or Advanced: 2026.0.1, 2025.12.1 or 2023.8.13, matching your branch. Puppet Core: 9.1.3 or 8.22.2.
  4. Read Perforce's advisory and apply its mitigations if you cannot upgrade straight away, as CISA directs. Check the version numbers there too.
  5. List which machines hold agent certificates. Any one of them could be a starting point. Go through the machines you no longer use or do not recognize with whoever runs Puppet.
  6. Treat a server that ran an affected version as possibly compromised. Exploitation is confirmed and our sources publish no indicators. Ask whoever runs the server to review its recent activity and the changes it pushed to managed machines, and to flag anything nobody can explain.
  7. Confirm the upgrade is actually running. An installed package is not the same as a patched, restarted service.

Puppet Enterprise vulnerability questions people are asking

Is the Puppet Enterprise vulnerability being exploited?

Yes. Help Net Security reports active exploitation, and CISA lists CVE-2026-115731 as a known exploited vulnerability.

Which version fixes CVE-2026-115731?

According to Help Net Security: Puppet Enterprise or Advanced 2026.0.1, 2025.12.1 or 2023.8.13, and Puppet Core 9.1.3 or 8.22.2.

Does an attacker need a password to exploit it?

CISA's description does not mention one. It says a client with any CA-signed agent certificate can run code on the Puppet Server.

Is Puppet Core affected?

The sources name fixed Puppet Core versions, 9.1.3 and 8.22.2. They do not say which Core versions are affected.

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

Tuesday 1 December 2026, for US federal agencies covered by the catalog.

Is there a workaround for the Puppet exploit?

CISA says to apply mitigations in accordance with vendor instructions. Our sources do not say what those mitigations are, so check Perforce's advisory. Upgrading to a fixed version is the clear fix.

The bigger lesson

The tools that manage everything else need the most protection. A configuration management server holds trust over every machine it touches. Patch it first, not last, and prune the list of machines it trusts as carefully as the list of people with admin passwords.

For help locking down and patching the servers that run your business, see security hardening or get a quote.

Get security alerts like this by email, with the free checklist, at security alerts.

Sources: CISA Known Exploited Vulnerabilities Catalog; Help Net Security.

Share X LinkedIn Facebook

Was this article helpful?

We only keep the note with this article. No name, no email.

Protected by reCAPTCHA - Privacy and Terms.

Have a question about this article?

Ask it here and we will answer you directly by email. Questions are private, never posted.

Protected by reCAPTCHA - Privacy and Terms.

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.

Protected by reCAPTCHA - Privacy and Terms.

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 Quote

Security alerts by email

The next security hole is already out there. Hear about it from us 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.

Protected by reCAPTCHA - Privacy and Terms.