Perforce Puppet flaw CVE-2026-115731 exploited in attacks, letting a certificate holder run code on the Puppet server

· CyberSecurity

TLDR

  • Flaw CVE-2026-115731 (CVSS 9.4) lets any client with a CA-signed agent certificate run code on a Puppet server.14
  • CISA added it to its Known Exploited Vulnerabilities catalogue on 17 November, citing evidence of active exploitation.3
  • Perforce patched Puppet Enterprise and Puppet Core on 3 November; the OpenVox fork is also affected and fixed.126

Attackers are exploiting a critical flaw in Perforce Puppet, an infrastructure-as-code and configuration management platform, to run code on vulnerable servers, according to SecurityWeek and CISA's Known Exploited Vulnerabilities listing.123 The flaw, CVE-2026-115731, carries a CVSS 4.0 score of 9.4, assigned by Perforce, and is a deserialisation of untrusted data issue in the report-processing code of Puppet Enterprise and Puppet Core.14 A client holding any certificate signed by the Puppet certificate authority (CA) can submit a report containing a crafted rich-data type through a PUT request and execute arbitrary code on the server as its service user.24 Where the CA signs requests automatically without strong verification, an unauthenticated network attacker can obtain such a certificate.24 SecurityWeek quotes a Perforce advisory saying a successful attack could expose the server's certificate-signing key, allow an attacker to issue trusted certificates and enable changes to the software and configuration delivered to managed systems on their next Puppet run.1 Administrators are advised to turn off auto-signing and enforce strong validation.1

The OpenVox project's advisory describes the mechanism: events in an agent's report reach Puppet's deserialiser, which reads an attacker-supplied type field and ends up evaluating attacker-supplied Ruby code.5 It says code execution as the puppet user gives access to the CA signing key, which would let the attacker sign certificates.5 Alain Rödel of Neodyme AG is credited with reporting CVE-2026-115731 together with CVE-2026-115732, a certificate-name authorisation bypass that The Hacker News lists at CVSS 9.0 and that affects both Puppet and OpenVox, and Neodyme says the issues were found with AI assistance and precise steering.2 Neodyme says the impact depends on the Puppet server configuration and the orchestration protocols used, but that an attacker with code execution on a Puppet server can take the CA signing keys and impersonate other hosts.2 SecurityWeek describes CVE-2026-115732 as letting an attacker use a certificate whose name extends an approved name to bypass authorisation and impersonate a managed machine.1

Perforce released fixes on 3 November in Puppet Enterprise 2026.0.1, 2025.12.1 and 2023.8.13, and in Puppet Core 9.1.3 and 8.22.2, and SecurityWeek says both CVEs are addressed in those releases.12 The Hacker News lists the affected ranges as Puppet Enterprise 2026.0.0 before 2026.0.1, 2025.0.0 before 2025.12.1 and 2023.8.0 before 2023.8.13, and Puppet Core 9.0.0 before 9.1.3 and 8.x before 8.22.2.2 OpenVox, an open-source implementation of Puppet, is also affected and is fixed in OpenVox Agent 9.3.0 and 8.32.0 and OpenVox Server 9.2.0 and 8.18.0.256 The OpenVox project says all known Puppet implementations are vulnerable to the CVEs fixed in its 3 November releases and that open-source Puppet is not receiving further updates.6 For those unable to upgrade, it suggests limiting server reachability to the network segments that need it and disabling or tightening autosign.6

SecurityWeek says exploitation was first flagged in a 4 November comment on Reddit's r/Puppet and that a proof-of-concept exploit targeting OpenVox was published shortly after the patch.1 CISA added it to the Known Exploited Vulnerabilities catalogue on 17 November based on evidence of active exploitation, and federal civilian agencies have until 1 December to apply fixes under Binding Operational Directive 26-04.234 The Hacker News says there are no details on how the flaw is being weaponised, and cites a self-reported Reddit post from 4 November, not separate corroboration, in which a user said that, after finding a severely misconfigured CA in their fleet, they traced the actions backwards on an intrusion using CVE-2026-115731.2 The Centre for Cybersecurity Belgium says a public proof of concept is available and the flaw is actively exploited, and advises patching with the highest priority, adding that patching does not remediate a historic compromise.7 Security Affairs reports that, on the latest vendor information it had, Perforce was not aware of attacks exploiting the flaw, had found no evidence of customer data being accessed, and that no threat actor or campaign has been linked to it.8 That sits at odds with CISA's finding of active exploitation, and Security Affairs does not reconcile the two.38

Why it matters: a Puppet server typically holds the certificate-signing key and delivers configuration to the systems it manages, and Perforce says a successful attack could let an attacker issue trusted certificates and change what those systems receive.15

Sources

  1. Critical Perforce Puppet RCE Exploited in Attacks (SecurityWeek)
  2. Hackers Exploiting Critical Puppet RCE Flaw Affecting Enterprise Management Servers (The Hacker News)
  3. CISA Adds One Known Exploited Vulnerability to Catalog (CISA)
  4. NVD - CVE-2026-115731 (NIST National Vulnerability Database)
  5. Authenticated RCE on OpenVox server via Event Deserialization (OpenVox Project (GitHub Security Advisory))
  6. Critical CVE Updates in all known versions of Puppet and OpenVox (Vox Pupuli)
  7. WARNING: Deserialization of Untrusted Data in Puppet Server Can Be Exploited to Execute Arbitrary Code. Public PoC Available, Actively Exploited in the Wild, Patch Immediately! (Centre for Cybersecurity Belgium)
  8. U.S. CISA adds Perforce Puppet Enterprise flaw to its Known Exploited Vulnerabilities catalog (Security Affairs)