Puppet, the configuration management platform now owned by Perforce Software, sits in a position in enterprise data centers that is easy to overlook and hard to replace. Agents on managed machines check in with a central Puppet Server, which compiles and distributes the configuration each node is supposed to enforce. That makes the server a control point through which software, credentials and policy flow to every machine in the fleet, and its built-in certificate authority issues the certificates agents use to prove who they are.
That design is what turned the disclosure of CVE-2026-115731 in early November 2026 into more than a routine server patch. The flaw is a deserialization error in the code that processes the reports agents send back after every run, and it lets a client holding a certificate signed by the Puppet certificate authority execute arbitrary code on the Puppet Server itself. The United States Cybersecurity and Infrastructure Security Agency has now judged the bug serious enough to require federal civilian agencies to fix it on a fixed deadline.
The Known Exploited Vulnerabilities catalog is CISA's public list of flaws the agency has evidence are being attacked. Each entry carries a remediation due date that binds federal agencies under the relevant binding operational directive. CISA's snapshot for the November 17, 2026 release lists 1,782 entries, a figure that speaks to how routine the mechanism has become even as each addition still signals real danger.
Key Facts
CISA announced on November 17, 2026 that it had added CVE-2026-115731, described as a Perforce Puppet Enterprise deserialization of untrusted data vulnerability, to the catalog on evidence of active exploitation, with a due date of December 1, 2026. The agency said this class of flaw is a frequent attack vector for malicious cyber actors and poses significant risks to the federal enterprise. The entry maps the bug to CWE-502, deserialization of untrusted data, and CWE-94, code injection, lists known use in ransomware campaigns as unknown, and states that forensic triage is not required under BOD 26-04. The required action is to apply mitigations in line with vendor instructions and in compliance with BOD 26-04, and to discontinue use of the product if no mitigations are available.
The severity numbers are stark. SecurityAffairs reported on November 18, 2026 that the flaw carries a CVSS 4.0 score of 9.4, with the NVD CVSS 3.1 score at 9.9. The affected component is Puppet Server, and successful exploitation yields remote code execution. Perforce shipped fixes on November 3, 2026, covering Puppet Enterprise 2026.0.1, 2025.12.1 and 2023.8.13, together with Puppet Core 9.1.3 and 8.22.2. Organizations that cannot upgrade immediately should disable automatic certificate signing unless requests are subject to strong verification.
Corgea Research reported on November 17, 2026 that Neodyme found the bug while preparing a red team engagement and reported it to Perforce and the OpenVox project in October. Puppet agents send a JSON report to the server after every run, and the server reconstructs each event as Ruby objects using Puppet's rich-data deserializer, which honors a __ptype key. An attacker can place a complete Pcore object type definition in that key, including a RubyMethod annotation whose body string is pasted into a generated class and executed through class_eval. Ruby evaluates backtick delimited shell commands in a class body at definition time, so the command runs as soon as the server parses the report, which arrives over a PUT request.
The authentication requirement is a certificate signed by the Puppet certificate authority, and that is a weaker gate than it sounds. Every managed node already holds one, including CI runners, build agents and developer workstations, and many fleets automatically sign new certificate requests. In that setup an attacker with network access to port 8140 can enroll a certificate and then run code on the server. Once code runs as the service user, the certificate authority private key is readable and can mint certificates for any node. Neodyme also noted that the community puppet gem on RubyGems, last released as version 8.10.0, will not be patched, and reproduced the remote code execution back to version 6.24.0 from July 2021. The EPSS score on November 17 was 0.00366.
A companion flaw, CVE-2026-115732, complicates the picture further. It scores 9.0 and lives in trapperkeeper-authorization, where exact hostname rules matched like prefix wildcards, so a certificate issued for evil.target.example.com passed a rule written for target.example.com. That turns a single compromised node into a way to impersonate another. Fixes for the pair shipped on November 3, and the OpenVox fork published its own versions: agent 9.3.0 and 8.32.0 with server 9.2.0 and 8.18.0. MLQ.ai Newsroom reported on November 18, 2026 that a working exploit was referenced in the OpenVox advisory, citing Daily Security Review, and that code execution as the puppet user also exposes the certificate authority signing key.
Analysis
The most interesting tension here is between two statements that are not quite contradictory but sit awkwardly together. Perforce said it was not aware of attacks exploiting the flaw and had found no evidence of customer data being accessed. CISA nonetheless added the bug to a catalog whose entire premise is evidence of active exploitation. What this really means is that the agency's exploitation evidence is likely independent of the vendor's incident response, drawn from federal telemetry, third party reporting or intelligence Perforce has not seen, and defenders should weight the government signal more heavily than a vendor statement carefully limited to what the vendor knows.
The scoring supports treating this as a top tier issue rather than a curiosity. An EPSS score of 0.00366 suggests a low probability of exploitation in the next 30 days. But EPSS models probability across the whole population, not the consequences for one estate, and it does not capture a flaw that grants a durable foothold in the system that controls configuration for every managed host. A publicly referenced exploit plus a trust model where any enrolled node can reach the vulnerable endpoint outranks a generic score.
The bigger picture here is that the certificate authority, not the deserializer, is the real weakness. Puppet's design makes the certificate the primary authentication boundary, and many operators autosign requests because manual signing does not scale. That convenience converts a network position into an authenticated one. The same logic applies to the companion flaw: hostname matching that behaves like a prefix wildcard undermines the assumption that a certificate identifies exactly one node. The gap between the enterprise product, fixed on November 3, and the community gem, which will never be fixed, is where quiet exposure will live for months.
Why It Matters
Control of a Puppet Server is not a single host compromise. Puppet pushes configuration and software to fleets of servers, so an attacker who holds the server can change what every managed machine runs, and with the certificate authority key in hand can issue trusted certificates for nodes that were never compromised. Puppet estates often include the systems that build, deploy and monitor other services, so the blast radius extends well past the server itself.
The federal deadline of December 1, 2026 compresses the response window to about two weeks from the listing. Agencies must inventory their deployments, determine whether autosign is enabled, and either upgrade to the fixed releases or apply mitigations. The private sector has no such deadline, so patch cadence will vary wildly between organizations running the same software. CISA's guidance under BOD 26-04 asks agencies to prioritize updates by risk, and a CVSS 9.4 flaw with a public exploit reference and a KEV entry is about as clear a priority signal as that process produces.
Detection is the harder half. CISA lists ransomware use as unknown and states that forensic triage is not required under BOD 26-04 for this entry, so agencies are not being pushed to hunt for evidence of past compromise. Given that exploitation leaves the attacker holding the signing key and able to mint certificates, the absence of a mandated hunt is a meaningful gap.
Next Up
The immediate work is unglamorous. Operators should identify every Puppet Enterprise and Puppet Core installation, confirm whether certificate autosign is enabled, apply the November 3 releases where possible, and treat CVE-2026-115732 as part of the same remediation rather than a separate ticket. Organizations running the community gem or the OpenVox fork need to map their versions against the fixed builds, since the guidance differs by product.
Beyond this entry, expect the KEV catalog to keep growing at its current pace, now standing at 1,782 entries. Neodyme has shown that the flaw reaches back to version 6.24.0 from July 2021, so a long tail of unpatched installations exists regardless of how quickly the fixed releases are adopted. The question for most organizations is not whether they will patch, but whether they will know, before an attacker does, that a certificate issued months ago is the credential that opens the door.
Comments (0)
Log in or sign up to leave a comment.
No comments yet. Be the first to share your thoughts.