What is Puppet Enterprise?
Puppet Enterprise is Perforce's configuration management platform. A central Puppet Server compiles catalogs, the declarative description of a machine's desired state, and agents installed on managed nodes fetch those catalogs, apply them, and send a run report back. Everything is authenticated with client certificates issued by a certificate authority that the Puppet Server itself runs.
That design makes the Puppet Server one of the highest-value hosts in any estate that uses it. It holds the CA signing key, it dictates the configuration of every node it manages, and in Puppet Enterprise it can run commands on managed hosts as root through PXP (the Puppet Execution Protocol). Code execution on the Puppet Server is, in practice, code execution across the fleet.
Overview
CVE-2026-115731 is a deserialization flaw in the code that handles agent run reports. Agents submit reports to the server over /puppet/v3/report, and those reports are encoded in Puppet's "rich data" format, which lets a JSON document name a Puppet type that the server should reconstruct. The server trusts the type name the client supplies. A crafted report drives that type machinery into generating Ruby source and evaluating it, giving the client arbitrary code execution as the puppet service user.
The precondition is a CA-signed agent certificate, which is why the CVSS v4.0 vector from the vendor (CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:H/VI:H/VA:H/SC:H/SI:H/SA:H, 9.4 Critical) marks privileges as low rather than none. In many real deployments that bar is close to zero: autosigning is commonly enabled so that new nodes can enroll without manual approval, and where autosign accepts requests without strong verification an unauthenticated attacker on the network can simply request a certificate and then use it. NVD scored the issue 9.9 under CVSS v3.1.
CISA added CVE-2026-115731 to the Known Exploited Vulnerabilities catalog on 2026-11-17 based on evidence of active exploitation, with a BOD 26-04 remediation deadline of 2026-12-01. Sources conflict on the details: several secondary write-ups published shortly after disclosure listed this CVE as not exploited and attributed in-the-wild activity to the companion flaw CVE-2026-115732 instead. CISA's listing is the authoritative statement on KEV status, but neither CISA nor the vendor has published victim details, indicators, or actor attribution.
Affected Versions
| Product | Vulnerable | Fixed |
|---|---|---|
| Puppet Enterprise 2026.0 | Before 2026.0.1 | 2026.0.1 |
| Puppet Enterprise 2025.12 | Before 2025.12.1 | 2025.12.1 |
| Puppet Enterprise 2023.8 (LTS) | Before 2023.8.13 | 2023.8.13 |
| Puppet Core | 8.x before 8.22.2, 9.x before 9.1.3 | 8.22.2, 9.1.3 |
| OpenVox Server | 8.17.0 and below, 9.1.0 and below | 8.18.0, 9.2.0 |
| OpenVox Agent | 8.31.1 and below, 9.2.0 and below | 8.32.0, 9.3.0 |
| Open Source Puppet | 6.24.0 (2021) through end of life | No fix; migrate to a supported product |
Neodyme reported exploiting Puppet Enterprise 2025.11.2 (Puppet 8.20.0) and confirmed that open source Puppet 6.24.0, released in July 2021, is vulnerable by the same path. The bug has therefore been reachable for roughly five years.
Technical Details
The sink is Puppet's rich data deserializer. A report event is handed to Puppet::Pops::Serialization::FromDataConverter.convert from transaction/event.rb. The converter reads the __ptype key out of the attacker's JSON, resolves it as a Puppet type, and calls .create(value) on it. For a PObjectType with no registered Ruby implementation class, resolution falls through to RubyGenerator.create_class, which builds Ruby source text for the class from the supplied definition, including attacker-controlled RubyMethod bodies, and then runs cls.class_eval on it. Backticks inside the injected method body execute shell commands at evaluation time.
In CWE terms this is deserialization of untrusted data (CWE-502) that resolves into code injection (CWE-94, the CWE assigned on the CVE record): the server lets remote input choose what code gets generated and then evaluates it. Attack complexity is low and no user interaction is needed. A single HTTP request to the report endpoint with a valid client certificate is enough; there is no chaining requirement and no memory corruption or race involved.
The blast radius goes past the one host. Execution as puppet grants read access to the CA signing key, which lets an attacker mint certificates for arbitrary node names, tamper with catalogs served to other hosts, and in Puppet Enterprise use PXP to execute as root on managed nodes. Neodyme demonstrated the CA key theft and the downstream root execution in a lab.
Discovery
The vulnerability was found by Alain of Neodyme AG while preparing for a red team engagement, and reported to both Perforce and the OpenVox project. Neodyme published a detailed write-up, "Pulling the Right Strings for RCE on a Puppet," on 2026-11-03, coordinated with the vendor fixes that went out at 17:00 UTC the same day. The OpenVox advisory GHSA-ffr6-rwpm-p5wq credits alain-neodyme as reporter and was published by binford2k.
The same research produced CVE-2026-115732, a certificate name authorization bypass in trapperkeeper-authorization where match-domain? compares only as many domain labels as the shorter name has, so a certificate for evil.target.lab.local authenticates as target.lab.local.
Exploitation Context
CISA's KEV addition on 2026-11-17 is the only authoritative statement that CVE-2026-115731 has been exploited in the wild, and CISA did not describe an intrusion or name an actor. There is no public ransomware association recorded for this entry.
What is not in dispute is the availability of working exploit code. The OpenVox GitHub advisory itself contains a malicious report that runs a shell command on the server, and Neodyme's post walks through the full chain including the proof of concept that copied the CA private key and minted a certificate. Anyone with a signed agent certificate, or with access to an autosigning CA, has everything needed.
No reliable exposure counts for internet-facing Puppet Servers were published alongside this CVE. That said, Puppet Servers are more often reachable from inside a network than from the internet, which makes this primarily a lateral movement and privilege escalation problem: any compromised managed node already holds a valid agent certificate, so a single foothold converts directly into fleet-wide control.
Remediation
- Upgrade Puppet Enterprise to 2026.0.1, 2025.12.1, or 2023.8.13, matching your release line, and restart Puppet Server afterward so the fixed code is loaded.
- For OpenVox, upgrade openvox-server to 8.18.0 or 9.2.0, openvox-agent to 8.32.0 or 9.3.0, and openvoxdb to 8.18.0 or 9.2.0, including the container image.
- Open source Puppet receives no fix. Migrate to Puppet Enterprise or OpenVox.
- Disable naive autosigning. Replace a blanket
autosign = trueor a wildcard pattern such as*.lab.localwith a policy-based autosign script that verifies a pre-shared challenge, or sign requests manually. - Restrict network access to Puppet Server so that only managed nodes can reach ports 8140 and 8142, and keep the service off the public internet.
- Patch CVE-2026-115732 at the same time. The two fixes ship in the same releases, and the certificate name bypass makes impersonation easier.
- Review logs for suspicious report submissions: Puppet Server access logs for PUT or POST requests to
/puppet/v3/reportfrom unexpected certificate names, unusualpuppetuser process activity, and CA logs for certificates issued to names you did not enroll. - If the server may have been compromised, treat the CA signing key as stolen. Rotate the CA, reissue agent certificates, and audit catalogs for unauthorized changes.
- Federal civilian agencies must remediate by 2026-12-01 under BOD 26-04, or discontinue use of the product if mitigations are unavailable.
Key Details
| Property | Value |
|---|---|
| CVE ID | CVE-2026-115731 |
| Vendor / Product | Perforce - Puppet Enterprise |
| NVD Published | 2026-11-03 |
| NVD Last Modified | 2026-11-17 |
| CVSS 3.1 Score | 9.9 |
| CVSS 3.1 Vector | CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:H/I:H/A:H |
| Severity | CRITICAL |
| CWE | CWE-94 find similar ↗ |
| CISA KEV Added | 2026-11-17 |
| CISA KEV Deadline | 2026-12-01 |
| Known Ransomware Use | No |
CVSS 3.1 Breakdown
Required Action
Timeline
| Date | Event |
|---|---|
| 2026-11-03 | Perforce and the OpenVox project publish fixes and advisories; Neodyme publishes its write-up |
| 2026-11-03 | CVE-2026-115731 published |
| 2026-11-17 | Added to CISA Known Exploited Vulnerabilities catalog |
| 2026-12-01 | CISA BOD 26-04 remediation deadline |
References
| Resource | Type |
|---|---|
| NVD - CVE-2026-115731 | Vulnerability Database |
| CISA KEV Catalog Entry | US Government |
| Perforce - Report Deserialization Code Execution | Vendor Advisory |
| OpenVox GHSA-ffr6-rwpm-p5wq - Authenticated RCE on OpenVox Server via Event Deserialization | Vendor Advisory |
| Neodyme - Pulling the Right Strings for RCE on a Puppet | Security Research |
| SecurityOnline - PoC Exploit and Technical Details Published for Puppet Server RCE Flaw | News |
| CISA Alert - CISA Adds One Known Exploited Vulnerability to Catalog | US Government |
| Puppet - Updates and Releases for Puppet Enterprise | Vendor Advisory |