Summary
CVE-2026-115731 is a critical remote code execution (RCE) vulnerability found in the report-processing code of Puppet, including Puppet Server and environments such as Red Hat Satellite. The vulnerability arises from the improper deserialization of untrusted data, specifically when processing a report containing a crafted rich-data type submitted via an HTTP PUT request. This issue is significant because it allows an attacker to execute arbitrary code with the privileges of the Puppet service user, potentially leading to the full compromise of the central certificate authority and all downstream managed systems.
Exploitation
- Active Exploitation: The vulnerability is highly severe; while authentication via a CA-signed agent certificate is typically required, permissive autosigning configurations can allow unauthorized actors to obtain such certificates and exploit the flaw.
- Threat Actors/Campaigns: No specific threat actors or ransomware campaigns have been publicly linked to this CVE at this time.
- PoC/Tool Availability: There is no specific mention of public exploit tools; however, the vulnerability is exploitable via a standard network-based HTTP PUT request to the `/puppet/v3/report` endpoint.
- Attack Prerequisites:
*
Network: The attack is remote, targeting the Puppet Server or OpenVox Server instance.
*
Authentication: Requires a CA-signed agent certificate. However, this prerequisite is effectively nullified in environments that use permissive autosigning without strong verification, allowing unauthenticated attackers to proceed.
*
User Interaction: None required.
Affected Products & Patches
- Affected Versions: Puppet Enterprise releases using puppet-agent versions before 8.22.2 or 9.1.3 are vulnerable. Specific affected releases include Puppet Enterprise 2023.8.13, 2025.12.1, and 2026.0.1.
- Patch Availability: Official patches are available. Users are advised to upgrade to openvox-server 9.2.0 or 8.18.0, and Puppet Core agent 9.1.3 or 8.22.2 (or the corresponding fixed Puppetserver/OpenVox Server builds).
- Mitigations/Workarounds:
* Disable or strictly restrict autosigning of certificate requests to prevent unauthorized clients from obtaining valid agent certificates.
* Restrict network access to the `PUT /puppet/v3/report` endpoint.
* Enforce allowlist validation on report payload schemas and event structures before deserialization.
* Deploy security monitoring (e.g., EDR, auditd, Falco, or eBPF) to detect anomalous child processes, unexpected shell invocations, or unauthorized system calls originating from the `puppetserver` service user.
Impact
- Capability: Successful exploitation grants the attacker the ability to execute arbitrary code on the Puppet Server as the `puppetserver` service user.
- Business Risk: For internet-facing or widely accessible deployments, this vulnerability poses a critical risk to infrastructure integrity. Because the Puppet Server typically acts as a central authority, compromise allows the attacker to gain control over the certificate authority, facilitating the potential compromise of all downstream managed systems and infrastructure within the Puppet ecosystem.