← All updates

Security / News explained

Puppet’s exploited report flaw needs the fixed release and a server restart

CISA added Puppet Enterprise’s report-deserialization flaw to KEV on November 17. Perforce lists fixed Enterprise releases and calls for restarting Puppet Server; certificate enrollment also shapes who can reach the vulnerable path.

By Zyel · Published · 4 min read

CISA added CVE-2026-115731, a Puppet Enterprise report-deserialization vulnerability, to its Known Exploited Vulnerabilities catalog on November 17, 2026. The new listing gives an already disclosed issue a stronger prioritization signal: exploitation is known, while the condition of any individual deployment still needs assessment. [1]

Perforce’s CVE record was published on November 3. It describes a client holding a CA-signed agent certificate sending a crafted report that results in code execution as the Puppet Server service user. Weakly verified automatic certificate signing can let an unauthenticated network actor obtain that prerequisite certificate. [2]

Our interpretation is that the certificate requirement makes enrollment part of the exposure review. A signed agent identity is meaningful, but it does not make every report submitted by that identity safe to deserialize. The report-processing path and the decision to admit a machine deserve attention together.

The stated execution context is the server’s service user. The practical reach then depends on that account and the systems around it. For an organisation using configuration management, the server’s own role is a reason to establish the facts promptly rather than treating the finding as an isolated application dependency.

Match the Enterprise release line

The vendor record lists affected Puppet Enterprise ranges as 2023.8.0 before 2023.8.13, 2025.0.0 before 2025.12.1, and 2026.0.0 before 2026.0.1. It identifies 2023.8.13, 2025.12.1 and 2026.0.1 as unaffected releases for this issue. [2]

Perforce’s solution also calls for restarting Puppet Server so the corrected code is loaded. The maintenance record needs to establish that the running process received the change, alongside the package or product upgrade. [2]

Puppet’s official release page independently identifies those three Enterprise versions as November 2026 security updates fixing CVE-2026-115731. The version list here concerns Puppet Enterprise; product release labels should be recorded precisely when planning the change. [3]

A useful acceptance record can connect the selected Enterprise release, the server restart and the subsequent health of normal configuration-management operations. Those are proposed outcomes for a controlled maintenance window. This article does not claim that we upgraded or tested a customer’s Puppet installation.

Certificate enrollment changes the entry conditions

Puppet’s documentation warns that basic autosigning is insecure because a requesting host can choose a certificate name. It limits that approach to environments where all computers able to connect to the primary server are fully trusted, and describes policy-based autosigning as another interface with different configuration complexity. [4]

Consider a hypothetical environment where automatic enrollment was enabled to make machine onboarding easier. Reviewing only whether the server asks for a certificate could leave the admission rule unexplained. The relevant question is how an untrusted machine could obtain an accepted identity, as well as which existing agent identities can submit reports.

That question should lead to an actual configuration review, not an assumption that every Puppet installation automatically signs arbitrary requests. The vendor describes a conditional route from weak verification to a usable agent certificate. An exposure assessment needs to retain that condition instead of flattening the issue into a universal anonymous attack.

CISA’s entry carries a December 1 action date and records ransomware-campaign use as unknown. The entry does not identify a victim or provide a complete incident history. Its value here is the exploitation-based priority signal and the direction to follow vendor mitigation guidance. [1]

Make the response describe the running system

In our view, the most useful handoff identifies who owns the Enterprise upgrade, who can authorize the restart and who understands certificate enrollment. Those responsibilities may sit with different teams. Keeping them on one response record reduces the chance that a successful package change is mistaken for the entire security outcome.

It is also useful to separate an inventory result from an incident conclusion. Finding an affected release establishes a remediation need under the advisory’s conditions. Determining whether unintended activity occurred requires the organisation’s own evidence and response process. Neither a public listing nor a completed restart supplies that history by itself.

The distinction between installing a fix and loading it is especially relevant to long-running services. The vendor has made the restart part of its stated remedy. An operator inheriting the ticket should be able to see whether that action happened, rather than having to infer it from a repository change or a download date.

For this disclosure, the practical combination is a correctly identified Enterprise release, the required server restart and an understood enrollment boundary. The November 17 listing changes the urgency of that work. It does not turn a November 3 disclosure into a newly released patch or establish what happened on any particular private server.

Sources + further reading

Source dates describe the original material. Publication above is the date this Zyel article went live.

  1. CISA KEV catalog: Puppet Enterprise CVE-2026-115731CISA official KEV data · Checked Nov 18, 2026
  2. Perforce CNA record: Report Deserialization Code ExecutionPerforce via the CVE Program · Checked Nov 18, 2026
  3. Puppet Enterprise November 2026 security releasesPuppet, a Perforce company · Checked Nov 18, 2026
  4. Basic certificate autosigning and its trust requirementsPuppet documentation · Checked Nov 18, 2026

Reader discussion

What would you ask next?

Questions, useful corrections and thoughtful disagreement are welcome. Comments are reviewed before they appear.

No reader comments yet.

10–2,000 characters. Plain text. Leave out passwords, private project data and personal contact details. A blank display name appears as Anonymous.

Complete the CAPTCHA before sending. Verification runs on your device.