Check a site
Check a website Service status Outages Blog
Theme
All tools
Check a websiteBrowse all tools
Puppet Server report processing marked known exploited: a crafted report upload, the signed-certificate requirement with autosign as a risk, and the fixed releases

Server & Security News

CISA flags exploited Puppet Enterprise vulnerability: patch guidance for administrators

Posted Jimel S.3 min read

CISA added CVE-2026-115731, a code-execution flaw in Puppet Server’s report processing, to its Known Exploited Vulnerabilities catalog on 17 November. Fixed builds are out. Here’s who is exposed, why certificate autosigning matters, and what to do.

Illustration: UtiBox

What was disclosed

Puppet automates server configuration. A central Puppet Server tells thousands of machines (agents) how to configure themselves, and the agents send back reports of what they did.

CVE-2026-115731 is a flaw in how Puppet Server processes those reports. The National Vulnerability Database describes it as:

Deserialization of untrusted data in the report-processing code of Puppet, as used by Puppet Server, in the affected releases, 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.

In plain English: a machine that Puppet trusts can send a specially built report and make the Puppet Server run its code. Because Puppet Server controls the configuration of every managed machine, that is serious. Puppet’s own score is CVSS 4.0 9.4 (critical).

Why certificate autosigning matters

Normally only machines you’ve approved hold a signed agent certificate. NVD adds a warning: “Where the certificate authority autosigns requests without strong verification, an unauthenticated network attacker can obtain such a certificate.”

So if your Puppet CA automatically signs any certificate request, anyone who can reach it may be able to enrol a fake agent, then exploit this flaw. Autosigning that checks a pre-shared secret or an allowlist is much safer than signing everything.

What the CISA listing means, and what it doesn’t

CISA added CVE-2026-115731 to its Known Exploited Vulnerabilities (KEV) catalog on 17 November 2026, with a remediation due date of 1 December 2026 for US federal agencies. A KEV listing means CISA has evidence the vulnerability is being exploited somewhere.

It does not mean your own Puppet Server has been compromised. It means you should treat patching as urgent and check for signs of misuse. CISA’s entry lists ransomware use as “Unknown”.

Affected and fixed versions

From Puppet’s release notes (opens in a new tab), which say the November 2026 security updates fix CVE-2026-115731:

ProductFixed in
Puppet Enterprise 2026.x2026.0.1
Puppet Enterprise 2025.x2025.12.1
Puppet Enterprise 2023.8.x (LTS)2023.8.13
Puppet Core 9.x / 8.x9.1.3 / 8.22.1

Earlier releases in those lines are affected. Confirm the exact range for your build in Perforce’s advisory (opens in a new tab) (Perforce support portal sign-in may be required) before you plan the upgrade. If you run an open-source build from another distributor, check that distributor’s advisory.

A safe response plan

  1. Inventory. List every Puppet Server and compiler, including test and disaster-recovery copies, and record their versions.
  2. Patch. Upgrade to a fixed release, starting with any server reachable from untrusted networks.
  3. Review signing. Check whether autosigning is on, and what policy it uses. Tighten it to a verified policy, or sign requests by hand, if it signs everything.
  4. Review certificates. Look through the signed certificate list for agents you don’t recognise, and revoke any that shouldn’t be there.
  5. Review logs. Look at Puppet Server and system logs for unexpected processes started by the Puppet service user and unusual report uploads around and before your patch date. If anything looks wrong, treat the server as compromised and follow your incident-response process.
  6. Limit exposure. Puppet Server’s port should only be reachable by your own agents, not the whole internet.

We don’t publish exploit details or scanning instructions. Checking your own systems from the inside, against the vendor’s advisory, is the safe way to find out where you stand.

Sources

Related

More from Server & Security News

Most read

Latest

Most read

  1. 01November Patch Tuesday lands on the 10th: what October’s record release tells us19
  2. 02Introducing UtiBox: the Web’s Utility Box2
  3. 03Ivanti Connect Secure zero-days gave attackers root on VPN gateways1
  4. 04“Black October”: attackers raid secrets at cloud and AI developer platforms1

Embed this post

Paste this code into your page. It shows the post as a card that links back here. In WordPress you can also paste the post’s address on a line of its own.

Cookies on UtiBox

UtiBox is free because of ads. Google and its partners use cookies to show, limit and measure ads, Google Analytics, Ahrefs Web Analytics and Microsoft Clarity show us how the site is used, and we use a few essential cookies to run the site.