The Library

Puppet Enterprise Vulnerability CVE-2026-115731: CISA Lists an Exploited Report-Processing Flaw, the Versions to Check and What Is Still Unknown

CISA has added Puppet Enterprise flaw CVE-2026-115731 to its Known Exploited Vulnerabilities catalog. Here is what is confirmed, which versions are named, what is still unknown and what to check this week.

Elite Performance Exclusive LLC 7 min read

Where Worldwide

Puppet Enterprise Vulnerability CVE-2026-115731: CISA Lists an Exploited Report-Processing Flaw, the Versions to Check and What Is Still Unknown
On this page 8 sections

CISA has added CVE-2026-115731, a flaw in Perforce's Puppet Enterprise, to its Known Exploited Vulnerabilities catalog, which means the agency has evidence that attackers are already using it. If your company uses Puppet Enterprise to manage its servers, the tool that controls your other systems has a known, exploited flaw, and it belongs at the top of this week's patch list.

What happened with CVE-2026-115731

CISA published an alert adding one vulnerability to its catalog: CVE-2026-115731 in Puppet Enterprise. CISA said it added the flaw "based on evidence of active exploitation" and described this type of vulnerability as a frequent attack vector for malicious cyber actors.

The National Vulnerability Database (NVD) record describes the weakness as deserialization of untrusted data in the report-processing code of Puppet. In plain terms, deserialization is when software takes data it has received and turns it back into working objects in memory. If the software trusts that data without checking it, someone who can send it carefully crafted data may be able to make the program do things it was never meant to do.

The NVD record is dated 2026-11-03. CISA's catalog entry sets a due date of Tuesday, December 1, 2026. That is the deadline US federal civilian agencies have to deal with listed flaws. It does not legally bind private companies, but it is a sensible deadline for anyone running the product.

Puppet Enterprise CVE-2026-115731: what is confirmed and what is not

We checked the NVD record, the CISA catalog entry and CISA's alert. Here is what they show and where they say nothing.

Confirmed by the primary sources Not stated in the sources we checked
CVE-2026-115731 affects Puppet Enterprise (Perforce) Who is exploiting it or how many organizations were hit
CISA listed it based on evidence of active exploitation How attackers are exploiting it in practice
The weakness is deserialization of untrusted data in Puppet's report-processing code A fixed release for version 2025.12.1
Version 2025.12.1 is listed as affected Any official workaround or temporary mitigation
Version 2023.8.13 is listed as a fixed version Signs of compromise to look for
The severity vector is CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:H/I:H/A:H Whether other Puppet editions are affected
CISA's due date is 2026-12-01 Whether ransomware groups are involved

If a vendor bulletin or researcher report fills in any of these gaps, trust that over this article. Until then, these are open questions, not answers.

How serious is the Puppet Enterprise vulnerability?

The NVD record gives the severity as a CVSS vector string rather than a headline number. Translated into plain English, it says:

  • AV:N (network): the attack can be carried out over the network. The attacker does not need to be at the machine.
  • AC:L (low complexity): no unusual conditions are needed for it to work.
  • PR:L (low privileges): the attacker needs some level of access, such as a low-level account or credential, but not an administrator account.
  • UI:N (no user interaction): nobody on your team has to click anything.
  • S:C (scope changed): the damage can reach beyond the vulnerable component itself.
  • C:H, I:H, A:H: high impact on confidentiality, integrity and availability. That means data can be read, changed or made unavailable.

Taken together, this is a serious profile: reachable over the network, simple to carry out once an attacker has a foothold, and able to spread beyond where it starts.

Which Puppet Enterprise versions are affected and fixed

This part needs care, because the version numbers in the record do not line up the way people expect.

The NVD record lists 2025.12.1 as affected and 2023.8.13 as a fixed version. Those are two different release lines. A fix in 2023.8.13 does not mean every release with a higher number is safe. The newer 2025.12.1 release is listed as affected.

The record we checked does not name a fixed release for version 2025.12.1. We are not going to guess one. If you run 2025.12.1, get the fixed version directly from Perforce before you upgrade, and confirm in writing that it covers CVE-2026-115731.

Why this matters for a company network

Puppet Enterprise is the kind of tool IT teams use to set up and keep many servers consistent from one place. That is exactly what makes a flaw in it worrying. A management tool is trusted by every machine it manages. If an attacker can take control of it, they may not need to break into each server separately.

The scope changed part of the severity vector points the same way: the impact is not limited to the vulnerable component. For a company, that can mean customer databases, web servers and internal applications all depend on the security of one management system that rarely gets the attention a firewall or email gateway gets.

This is a common gap. Back-office infrastructure tools often sit outside the regular patch routine because they just work. If nobody owns updates for them, see our notes on self-hosting infrastructure.

What to do this week: Puppet Enterprise checklist

Step What to do
1. Find every install List every Puppet Enterprise server you run, including test, staging and disaster-recovery copies.
2. Check the version Record the exact Puppet Enterprise version on each one from the console or your install records.
3. If below the fixed version Upgrade to 2023.8.13 or later.
4. On 2025.12.1 Treat it as affected. Get the fixed release for your line from Perforce and schedule it before 2026-12-01.
5. On any other version Ask Perforce whether your version is affected and what to install. Do not assume.
6. Limit who can reach it Make sure the Puppet Enterprise server is reachable only from the machines it manages and from your admin network, never from the open internet.
7. Review accounts Exploitation needs only low privileges, so remove unused accounts, rotate shared credentials and check who has access.
8. Look back Review recent logs for changes, new accounts or activity you cannot explain. The sources give no specific signs to look for, so anything unexpected is worth a closer look.

If you cannot patch a 2025.12.1 system right away, steps 6 and 7 reduce your exposure. They are not a fix.

Puppet Enterprise vulnerability questions people are asking

What is CVE-2026-115731?

It is a vulnerability in Perforce's Puppet Enterprise, caused by deserialization of untrusted data in Puppet's report-processing code.

Is CVE-2026-115731 being exploited?

Yes, according to CISA, which added it to the Known Exploited Vulnerabilities catalog based on evidence of active exploitation. CISA has not said who is behind the attacks or how many organizations were affected.

Which Puppet Enterprise version fixes CVE-2026-115731?

The NVD record lists 2023.8.13 as a fixed version. It lists 2025.12.1 as affected and does not name a fix for that line, so ask Perforce for the right release.

Does an attacker need a password to exploit it?

The severity vector says low privileges are required. That means an attacker needs some access, but not administrator rights. That is why reviewing accounts matters.

Is there a workaround for the Puppet Enterprise flaw?

The sources we checked do not mention one. Limiting network access and reviewing accounts lowers your risk, but upgrading is the actual fix.

Do private companies have to meet the December 1 deadline?

No. The 2026-12-01 due date applies to US federal civilian agencies. It is still a reasonable deadline for any business running Puppet Enterprise.

Is open source Puppet affected?

The catalog entry names Puppet Enterprise. The sources we checked do not say whether other Puppet editions are affected.

The bigger lesson

Attackers go after the tools that manage everything else, because one break-in there can reach every system behind it. Configuration management, monitoring and remote management servers need the same patch routine as your firewall, with someone clearly responsible for them and a list of every copy you run. If version numbers on different release lines leave you unsure whether you are fixed, assume you are not until the vendor confirms it.

For help keeping management servers locked down and patched, see security hardening or request a quote.

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

Sources: NVD: CVE-2026-115731; CISA Known Exploited Vulnerabilities catalog: CVE-2026-115731; CISA: CISA Adds One Known Exploited Vulnerability to Catalog.

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.