What happened
CVE-2026-115731 was disclosed on 3 November 2026; CISA added it to KEV on 17 November 2026 and set a federal due date of 1 December 2026. Attribution posture: CISA has confirmed active exploitation of CVE-2026-115731 but has not named an actor or described the attacks. CISA lists ransomware use as unknown, so the KEV decision establishes exploitation but not campaign type, victim scope or attacker identity.
CVE-2026-115731 lets a client holding any CA-signed agent certificate submit a crafted report to PUT /puppet/v3/report and execute code as the Puppet service user. The vulnerable report deserialisation path processes attacker-controlled rich-data types. Where autosign lacks strong verification, an unauthenticated attacker can first obtain a certificate and complete the chain. Red Hat assesses that access as the Puppet service account can place the central certificate authority and downstream managed systems at risk.
Puppet fixed the flaw in Puppet Enterprise 2026.0.1, 2025.12.1 and 2023.8.13. OpenVox Server users have separate fixed releases identified in the OpenVox advisory. OpenVox’s public proof of concept executes touch /tmp/pwned as the puppet user; unexpected child processes or files in that service context require investigation. No attack IP addresses, domains, hashes, filenames or victim details were published by CISA.
Why this matters now
The underlying flaw was disclosed earlier, but CISA’s KEV addition changes the decision from preventive patching to exploited-control-plane response. Puppet Server is not an ordinary application host: it distributes configuration and holds certificate-authority material that determines which managed machines are trusted. Successful exploitation can therefore affect the integrity of the management plane and potentially downstream systems.
The certificate prerequisite is not uniformly protective. Any client holding a CA-signed agent certificate can reach the vulnerable report-processing path, while permissive autosign can allow an unauthenticated actor to enrol first. Asset owners must assess certificate issuance, autosign rules and network reachability rather than classifying the issue solely as authenticated.
A fixed version proves only that the vulnerable code is gone. It does not prove that an attacker failed to execute commands before the update, obtain CA material, sign additional certificates or alter managed configuration. The closure standard must therefore include certificate and host forensics, not just a successful upgrade job.
The decision for security leaders
Classify Puppet Server as a privileged control plane and assign the response accordingly. Infrastructure automation owners should lead the upgrade, while incident response and identity teams assess certificate issuance, service-account execution and CA integrity. Internet exposure, permissive autosign or unexplained certificate requests should move the case into emergency handling.
Separate patch status from compromise status. Verify the running server version, then examine pre-patch logs, endpoint telemetry, certificate signing records, unexpected files and child processes under the puppet account. If evidence indicates CA access or unauthorised certificate issuance, scope downstream systems that accepted Puppet-issued trust and prepare controlled certificate rotation.
Do not accept autosign disablement as remediation for the underlying defect. It reduces one path but authorised or previously enrolled clients can still reach the vulnerable report endpoint until the server is fixed. Any temporary network restriction or autosign change requires an owner, validation test and expiry tied to the upgrade window.
Evidence of closure
- Running Puppet Enterprise servers report a fixed release.
- Certificate records contain no unexplained requests or issued identities.
- Host forensics find no unauthorised puppet-user execution or persistence.
- Autosign configuration requires strong, documented identity verification.、CA-key rotation has an approved evidence-based disposition.
The Security.io assessment
The KEV addition is the material change. Prior to it, organisations could treat the issue as a critical but conditional report-deserialisation flaw. CISA’s exploitation evidence removes that option and raises the closure standard, particularly because the affected server is trusted to manage configurations across the estate.
Public evidence does not describe who is exploiting the flaw, how targets are selected or what post-exploitation actions occurred. That uncertainty supports a focused compromise assessment rather than speculative attribution. Organisations should use their own certificate and endpoint evidence to determine whether the control plane remained trustworthy before and after patching.
A clean vulnerability scan after upgrade is necessary but insufficient. The most consequential unanswered question is whether an attacker executed as the puppet user and reached certificate-authority material. Closure requires a documented conclusion on that question, including the limitations of retained telemetry and an approved decision on CA-key or certificate rotation.
Questions for the morning meeting
- Where are Puppet Enterprise and OpenVox servers deployed, and which are reachable by untrusted networks?
- Is certificate autosign enabled without strong identity verification?
- Can we detect unexpected processes, files or certificate requests under the Puppet service context?
- What downstream systems depend on the affected Puppet certificate authority?