Skip to main content
Emerging ThreatsMalware & Ransomware

Hackers Actively Exploit Critical Puppet RCE Flaw in Enterprise Servers

Rows of rack-mounted servers in a brightly-lit data center with a single unoccupied workstation in the foreground.

"Perforce Puppet Enterprise contains a deserialization of untrusted data vulnerability in Puppet's report-processing code that 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," CISA said.

CVE-2026-115731: the technical bite

The vulnerability tracked as CVE-2026-115731 (CVSS score: 9.4) is a deserialization-of-untrusted-data flaw that can lead to remote code execution (RCE) on Puppet servers. The U.S. Cybersecurity and Infrastructure Security Agency (CISA) added the flaw to its Known Exploited Vulnerabilities (KEV) catalog on Tuesday, citing reports of active exploitation.

CISA's advisory makes two operational points clear: an attacker can trigger code execution by submitting a crafted rich-data type via a PUT request, and the exploit requires possession of a CA-signed agent certificate. The bulletin warns that where a certificate authority automatically signs requests "without strong verification," an unauthenticated network attacker may be able to obtain a valid certificate and exploit the flaw.

Affected Puppet and OpenVox releases and Perforce's fixes

The shortcoming impacts multiple Puppet Enterprise and Puppet Core releases. Versions affected, as listed in the advisory, are:

  • Puppet Enterprise 2026.0.0 before 2026.0.1
  • Puppet Enterprise 2025.0.0 before 2025.12.1
  • Puppet Enterprise 2023.8.0 before 2023.8.13
  • Puppet Core 9.0.0 before 9.1.3
  • Puppet Core 8.x before 8.22.2

Perforce Software released fixes on November 3, 2026, issuing patched builds labeled:

  • Puppet Enterprise 2026.0.1 (Puppet Core 9.1.3)
  • Puppet Enterprise 2025.12.1 (Puppet Core 8.22.2)
  • Puppet Enterprise 2023.8.13 (Puppet Core 8.22.2)
  • Puppet Core 9.1.3 and Puppet Core 8.22.2

The advisory also notes the issue affects OpenVox, an open-source implementation of Puppet, and that OpenVox patches are available in OpenVox Agent 9.3.0 and 8.32.0 and OpenVox Server 9.2.0 and 8.18.0.

Discovery, dual CVEs, and the role of AI-assisted research

Alain Rödel, a security researcher at Neodyme AG, is credited with discovering and reporting CVE-2026-115731 and a second related issue, CVE-2026-115732 (CVSS score: 9.0), described as a certificate-name authorization bypass affecting both Puppet and OpenVox. Neodyme said both issues were discovered "with artificial intelligence (AI) assistance and precise steering."

Neodyme's published report underscores how the tangible impact will vary by configuration. "The impact highly depends on the Puppet server configuration and the orchestration protocols used, if any are enabled at all," the German cybersecurity company wrote. It added a stark operational warning: "Independent of the configuration, an attacker with RCE on a Puppet server can grab the CA signing keys and impersonate other hosts."

Neodyme also highlighted the potential downstream consequences: "Puppet is a powerful software, often with full access to a fleet of systems in a corporate network. Remote Code Execution on such a central and important system can lead to worst-case scenarios: Deployment of ransomware, mass data exfiltration, and potentially lateral movement to other parts of the network."

Active exploitation: signals and uncertainty

CISA's KEV listing cites reports of active exploitation, but the agency's advisory does not provide technical indicators or details of specific intrusions. The source material states explicitly: "As of writing, there are no details on how the vulnerability is being weaponized in the wild."

That lack of public forensic detail has not stopped individual operators from reporting incidents. A Reddit user named transdimensia posted on November 4 that they had traced a [CVE-2026-]115731 intrusion back to a severely misconfigured CA in their fleet. "After finding a severely misconfigured CA in my fleet, I traced the actions backwards on a [CVE-2026-]115731 intrusion," the user said, according to the advisory.

What this means for FCEB agencies, enterprise security teams, and OpenVox maintainers

  • Federal Civilian Executive Branch (FCEB) agencies: CISA advises these agencies to apply the fixes by December 1, 2026, under Binding Operational Directive (BOD) 26-04: Prioritizing Security Updates Based on Risk. The deadline formalizes a concrete remediation window for affected federal systems.
  • Enterprise security teams: Because an exploited Puppet server can yield CA signing keys and control over many managed endpoints, teams should prioritize patching the listed Puppet Enterprise and Puppet Core releases or applying mitigations where upgrades are not immediately possible. The advisory links exploitation to high-impact outcomes including ransomware deployment and mass data exfiltration.
  • OpenVox maintainers and users: OpenVox-based deployments are explicitly affected and have corresponding patched releases. Operators running OpenVox Agent or Server should move to patched versions (Agent 9.3.0 / 8.32.0; Server 9.2.0 / 8.18.0) to remove the vulnerability.

Perforce released patches on November 3, 2026; CISA has placed CVE-2026-115731 on its KEV list and given federal agencies a December 1 remediation deadline. Beyond those dates, the public record in this advisory leaves a single, practical question: will further technical indicators of exploitation appear publicly to help defenders attribute activity and harden verification of CA-signing processes? For now, the immediate, concrete actions are supplied — and the clock to patch is running.

Original story