CISA Adds Perforce Puppet Enterprise Flaw to KEV Catalog
A deserialization flaw in Puppet Server report-processing code lets attackers with a CA-signed certificate run code as the service user, CISA warns, setting a December 1 federal patch deadline.

CISA added CVE-2026-115731, a critical deserialization vulnerability in Perforce's Puppet Enterprise configuration management platform, to its Known Exploited Vulnerabilities (KEV) catalog on November 17, 2026. The flaw lets a client holding any CA-signed agent certificate execute arbitrary code on a Puppet Server as the service user, and in environments that autosign certificate requests without strong verification, an unauthenticated network attacker can obtain that certificate and exploit the bug remotely. Federal civilian agencies have until December 1, 2026 to patch or mitigate under Binding Operational Directive 26-04, and Perforce is urging every Puppet Enterprise operator, not just government users, to update immediately.
What CISA added to the KEV catalog
CVE-2026-115731 is listed in the CISA Known Exploited Vulnerabilities catalog as the "Perforce Puppet Enterprise Deserialization of Untrusted Data Vulnerability." The catalog entry names Perforce as the vendor and Puppet Enterprise as the affected product, with the vulnerability added on November 17, 2026 and a required-action deadline of December 1, 2026. CISA's own description, repeated in its notes, is specific about the mechanism: the bug sits in "Puppet's report-processing code" and allows "a client with any CA-signed agent certificate to execute arbitrary code on the Puppet Server as the service user by submitting a report containing a crafted rich-data type through a PUT request."
The KEV catalog exists to flag vulnerabilities CISA has confirmed are being exploited in the wild, and federal agencies are required to remediate catalog entries by their listed due date under BOD 26-04, the directive that replaced the agency's earlier vulnerability-management mandate. That requirement is legally binding only on U.S. federal civilian executive branch agencies, but CISA has long framed KEV additions as a signal every organization should act on, since the vulnerabilities it lists have a demonstrated history of being weaponized.
What Puppet Enterprise is and who runs it
Puppet is a declarative configuration-management tool originally built by Puppet Labs and now developed by Puppet, a Perforce company following Perforce's 2022 acquisition. It lets infrastructure teams define the desired state of servers, network devices, and cloud instances in code, and a Puppet agent on each managed node checks in with a central Puppet Server to pull configuration changes and report back on compliance. Puppet Enterprise is the commercial, supported edition of the platform, widely deployed by organizations that need to manage configuration drift and compliance across large fleets of Unix-like and Windows systems. Background on the broader project and its ownership is available on Wikipedia's Puppet (software) entry.
Because Puppet Server sits at the center of an organization's infrastructure automation, with trusted agents checking in constantly, a remote code execution flaw there is serious by design: the service typically runs with broad access to provision, reconfigure, or tear down the systems it manages. Configuration-management platforms like Puppet are also attractive targets precisely because of their reach. A single compromised Puppet Server can, in principle, be used to push malicious configuration changes out to every agent node it manages, turning one foothold into fleet-wide access rather than a single compromised host.
Vulnerability details at a glance
| Field | Detail |
|---|---|
| CVE ID | CVE-2026-115731 |
| Vendor | Perforce |
| Product | Puppet Enterprise |
| Vulnerability name | Perforce Puppet Enterprise Deserialization of Untrusted Data Vulnerability |
| CWE classification | CWE-502 (Deserialization of Untrusted Data); CWE-94 (Improper Control of Generation of Code, i.e. Code Injection) |
| CVSS v3.1 score (NVD, primary) | 9.9 Critical — AV:N/AC:L/PR:L/UI:N/S:C/C:H/I:H/A:H |
| CVSS v4.0 score (Puppet/Perforce) | 9.4 Critical |
| CVE published | November 3, 2026 |
| Added to CISA KEV catalog | November 17, 2026 |
| Federal remediation deadline (BOD 26-04) | December 1, 2026 |
| Known ransomware campaign use | Unknown, per CISA |
| Forensic triage flagged by CISA | No |
| Fixed Puppet Enterprise versions | 2023.8.13, 2025.12.1, 2026.0.1, or later |
Note on severity: Perforce's own CVSS v4.0 rating of 9.4 and the National Vulnerability Database's independently calculated CVSS v3.1 score of 9.9 both land in the Critical band, reflecting a vulnerability that requires no user interaction, can be triggered over the network, and threatens full confidentiality, integrity, and availability impact once an attacker holds a valid certificate. The NVD vector breaks down to: attack vector network (AV:N), low attack complexity (AC:L), low privileges required (PR:L) in the sense of holding a valid certificate rather than an administrative account, no user interaction needed (UI:N), a changed scope (S:C) reflecting that the impact extends beyond the vulnerable component itself, and high impact across confidentiality, integrity, and availability (C:H/I:H/A:H). That combination is what pushes the score close to the maximum of 10.
How the attack works, in plain English
Puppet's architecture relies on a certificate-based trust model: every agent that wants to check in with Puppet Server needs a certificate signed by the deployment's certificate authority (CA). Normally, only legitimate, enrolled agents hold such a certificate, and the report data those agents submit back to the server is assumed to be trustworthy.
The vulnerability breaks that assumption at the report-processing stage. According to CISA's description, Puppet Server deserializes incoming report data without adequately restricting what object or data types that process can instantiate. An attacker who can present a report containing a specially crafted "rich-data type" through a PUT request can get the server to deserialize and execute attacker-controlled code, running as whatever service account Puppet Server uses. In short, the entry point is not an authentication bypass in the usual sense; it is an unsafe deserialization bug reachable by anyone who already holds, or can obtain, a CA-signed agent certificate.
That second clause is what turns a bad bug into a potentially unauthenticated one. Many Puppet deployments use "autosigning," where the CA automatically approves certificate-signing requests from new agents to simplify fleet enrollment, rather than requiring an administrator to manually verify and approve each request. CISA's advisory notes that if the CA autosigns requests without strong verification, an attacker with no prior access or credentials can request a certificate, receive it automatically, and then use that certificate to submit the malicious report and achieve code execution. In deployments that disable autosigning or pair it with strict request verification (such as matching expected hostnames or using a one-time password/challenge), an attacker would need to first compromise or socially engineer their way to a valid certificate, which is a materially higher bar.
Who is affected
The vulnerability affects Puppet Enterprise releases in three branches, per the CVE record: versions in the 2023.8 line before 2023.8.13, versions in the 2025.x line before 2025.12.1, and the initial 2026.0.0 release before 2026.0.1. Any organization running an affected Puppet Server that accepts agent check-ins from clients outside a tightly controlled, fully trusted network segment should treat this as urgent, and that caution applies with particular force to deployments where autosigning is enabled for convenience. Organizations running the open-source Puppet Server or related community forks should separately check whether their specific build and version are covered by the same underlying report-processing issue, since CISA's KEV entry and the CVE record here specifically track Perforce's commercial Puppet Enterprise product.
Exposure also depends heavily on network placement. A Puppet Server reachable only from a tightly segmented management network, with certificate issuance restricted to known, pre-approved hosts, presents a much smaller attack surface than one reachable from a broader corporate network or, worse, from the public internet. Security teams reviewing their own exposure should start by mapping exactly which networks and hosts can reach their Puppet Server's agent-facing port, independent of whether autosigning is enabled.
The December 1, 2026 federal deadline
CISA's KEV catalog entry sets November 17, 2026 as the date added and December 1, 2026 as the required action date. Under BOD 26-04, that two-week window is a binding compliance deadline for federal civilian executive branch agencies, which must apply the vendor's patch, implement any CISA-approved mitigation, or stop using the product if neither is feasible, by that date. CISA's required action language for this entry also permits applying vendor-provided mitigations as an interim step where immediate patching isn't possible.
The directive does not legally bind state, local, or private-sector organizations, but CISA consistently frames every KEV catalog addition the same way: these are vulnerabilities with a documented history of real-world exploitation, and the agency recommends all organizations, regardless of sector, prioritize remediation on the same accelerated timeline federal agencies are required to follow.
Ransomware and exploitation context
CISA's KEV catalog tracks a "Known ransomware campaign use" field for every entry, and for CVE-2026-115731 that field is marked "Unknown." That designation means CISA has not confirmed this vulnerability has been used in ransomware operations specifically; it does not rule it out, but it also should not be read as confirmation of ransomware activity. CISA likewise marked the entry "No" for mandatory forensic triage under BOD 26-04, a separate flag reserved for a subset of especially high-risk KEV entries. The underlying justification for KEV inclusion remains that CISA has evidence of in-the-wild exploitation of the vulnerability itself, independent of whether that exploitation is tied to ransomware.
- CVE-2026-115731 affects Perforce Puppet Enterprise via a deserialization flaw in report-processing code (CWE-502, CWE-94).
- CVSS 9.9 (v3.1, NVD) / 9.4 (v4.0, Puppet) — both Critical.
- Exploitable by any client with a CA-signed agent certificate; autosigning without strong verification can make it exploitable by an unauthenticated network attacker.
- Fixed in Puppet Enterprise 2023.8.13, 2025.12.1, and 2026.0.1.
- Federal patch/mitigation deadline: December 1, 2026.
Remediation and mitigation guidance
Perforce's own advisory for this issue, published on the company's support portal, is the authoritative source for fix guidance, and CISA's KEV notes link directly to it. The core remediation is to upgrade Puppet Enterprise to a fixed release: 2023.8.13 or later for the 2023.8 branch, 2025.12.1 or later for the 2025.x branch, or 2026.0.1 or later for the 2026.0 branch, as reflected in the NVD CVE record for CVE-2026-115731. Administrators should plan to restart the Puppet Server service after upgrading so the patched report-processing code is actually loaded.
Where an immediate upgrade isn't possible, the interim control follows directly from how the bug is reachable: tighten certificate issuance so an attacker cannot simply request and receive a valid agent certificate. That means auditing whether autosigning is enabled, and if it is, replacing blanket autosigning with a verification step, such as per-request approval, a pre-shared challenge password, or matching against an expected allowlist of hostnames, rather than approving every incoming signing request automatically. Organizations should also review Puppet Server logs for unexpected certificate-signing requests and unusual report submissions during the period before they patch, and treat any Puppet Server exposed to a broader network than strictly necessary as a priority to isolate while remediation is in progress.
Teams that also run community Puppet Server builds or related forks outside Perforce's commercial product should check vendor-specific advisories for those projects separately, since this CVE record and KEV entry are scoped to Perforce's Puppet Enterprise.
Part of a broader patching push
This addition lands in a month where CISA has repeatedly used the KEV catalog to push enterprises toward faster patching of infrastructure software. It follows closely on the heels of CISA's decision to add a Cisco BroadWorks XXE flaw to the same catalog with its own federal deadline, and an earlier entry covering a Check Point Gaia privilege-escalation bug. Security teams juggling both KEV deadlines and routine patch cycles, including fixes that came out of November's Patch Tuesday round, should treat infrastructure-automation software such as Puppet Server as a high-value target precisely because of the trust it holds over everything it manages.
What to do next
Puppet Enterprise administrators should confirm their running version against the fixed releases above, schedule an upgrade to 2023.8.13, 2025.12.1, or 2026.0.1 (or later) as soon as possible, and restart Puppet Server once patched. Anyone who cannot patch immediately should audit and lock down certificate autosigning as an interim measure, and review Puppet Server access and report-submission logs for signs of attempted exploitation. Federal civilian agencies are bound to complete remediation by December 1, 2026 under BOD 26-04; every other Puppet Enterprise operator should treat that same date as the practical deadline, since CISA's KEV listing confirms this vulnerability already has a track record of exploitation in the wild.
Frequently asked questions
What is CVE-2026-115731?
CVE-2026-115731 is a critical deserialization of untrusted data vulnerability in Perforce's Puppet Enterprise. It lets a client holding any CA-signed agent certificate execute arbitrary code on the Puppet Server as the service user by submitting a report containing a crafted rich-data type through a PUT request.
Is CVE-2026-115731 in the CISA KEV catalog?
Yes. CISA added CVE-2026-115731 to its Known Exploited Vulnerabilities catalog on November 17, 2026, with a required federal remediation date of December 1, 2026.
What is the CVSS score for this Puppet Enterprise vulnerability?
NVD lists a primary CVSS v3.1 base score of 9.9 (Critical). Puppet's own CNA submission rates it 9.4 (Critical) under CVSS v4.0. Both reflect a network-exploitable flaw with high impact to confidentiality, integrity, and availability.
Which Puppet Enterprise versions are affected, and what fixes it?
Per the NVD CVE record, affected versions are 2023.8.x before 2023.8.13, 2025.x before 2025.12.1, and 2026.0.0 before 2026.0.1. Upgrading to 2023.8.13, 2025.12.1, or 2026.0.1 (or later) resolves the issue.
Is this vulnerability being used in ransomware attacks?
CISA lists known ransomware campaign use for CVE-2026-115731 as 'Unknown.' That means CISA has not confirmed ransomware use of this specific flaw; it should not be read as confirmation that ransomware groups are exploiting it.
Does the December 1, 2026 deadline apply to private companies?
The deadline is legally binding only on U.S. federal civilian executive branch agencies under Binding Operational Directive 26-04. CISA recommends that all Puppet Enterprise operators, including private-sector organizations, patch on the same timeline given the vulnerability's KEV status.
Sources
- CISA Known Exploited Vulnerabilities Catalogcisa.gov
- NVD - CVE-2026-115731 Detailnvd.nist.gov
- Perforce Advisory: Report Deserialization Code Executionportal.perforce.com
- Wikipedia: Puppet (software)en.wikipedia.org
Sana Qureshi runs the security and privacy desk. She reports on actively exploited vulnerabilities, vendor patches and data breaches, and covers the password managers, VPNs and authentication tools readers use to protect themselves. Her alerts cite vendor advisories, CISA and the CVE record directly.

