CISA has added CVE-2026-115731, a critical deserialization flaw in Perforce Puppet Server, to its Known Exploited Vulnerabilities catalog and ordered federal civilian agencies to remediate it by December 1. The listing follows the release of a public exploit earlier this month, and it comes even though Perforce says it is not aware of attacks.
CISA Sets a December 1 Federal Deadline Under BOD 22-01
The KEV addition was reported on November 18. Under Binding Operational Directive 22-01, CISA required federal civilian agencies to fix the flaw by December 1. The vulnerability carries a CVSS score of 9.4 and affects Perforce Puppet Enterprise and Puppet Server.
Why a KEV Listing Sits Alongside No Confirmed Exploitation of CVE-2026-115731
The listing creates a tension that is worth stating plainly. Perforce says it is not aware of attacks and found no evidence of customer data access. Reporting on the KEV addition says no reports confirm active exploitation and that no threat actor or campaign has been linked to the flaw. CISA’s catalog, by its nature, is reserved for vulnerabilities with evidence of exploitation, yet the public record available so far does not describe any specific attack. The gap between the two positions has not been explained.
How the Report-Processing Flaw Gives Code Execution on Puppet Server
CVE-2026-115731 is an improper deserialization of untrusted data in Puppet Server’s report-processing component. A client that holds a certificate signed by the Puppet certificate authority can send a crafted report by HTTP PUT and run code as the Puppet Server service account.
Auto-Signing Certificate Authorities Raise the Risk
The risk is higher where the CA automatically signs certificate requests without verification. In that configuration, a network attacker could first obtain a valid agent certificate and then use it to send the malicious report, removing the need to compromise an existing agent.
Patched Releases From Early November and the Earlier Public Exploit
Perforce released fixes on November 3. The patched versions are Puppet Enterprise 2026.0.1, 2025.12.1 and 2023.8.13, and Puppet Core 9.1.3 and 8.22.2. A public exploit for the Puppet Server remote code execution flaw appeared the following day, on November 4, which means attackers have had working code for two weeks before CISA’s listing.
CISA’s Alert Dated November 17 and Conflicting Severity Scores
CISA’s alert, titled “CISA Adds One Known Exploited Vulnerability to Catalog,” is dated November 17, and news coverage followed on November 18. CISA lists the flaw as “Perforce Puppet Enterprise Deserialization of Untrusted Data Vulnerability.” Trackers disagree on severity: Security Affairs and most outlets give a CVSS score of 9.4, while nFlo’s entry gives 9.9 along with an EPSS score of 0.4 percent, the 31st percentile. Reports also differ on which directive CISA cites in its required-action text.
How the Crafted Rich-Data Type Reaches the Puppet Server Service Account
The attacker submits a crafted rich-data type inside a report sent by HTTP PUT. The code then runs with the privileges of the Puppet Server service account. A public proof-of-concept repository exists and is listed on exploit aggregators, consistent with the November 4 public-exploit coverage. The KEV listing implies CISA holds evidence of exploitation, but neither Perforce nor CISA has said who exploited the flaw or how.
Why Puppet Server Takeover Reaches Beyond a Single Host
Puppet Server controls fleets of managed systems, so taking it over is a path to compromising all of them. That is what makes a deserialization bug in a configuration-management server more serious than the same bug in an ordinary application.
Perforce’s remediation guidance is to upgrade to a fixed release and to disable automatic certificate signing unless requests are strongly verified. The second step addresses the conditions that make exploitation easiest, and it applies even to organizations that have already patched.
For federal agencies the deadline is fixed. Other organizations that run Puppet Enterprise or Puppet Core face the same flaw, the same public exploit and the same available fixes, without a mandated date. CISA’s standard language tells agencies to discontinue use of the product if mitigations are unavailable. Restricting who can obtain agent certificates narrows the exposure further.
