Threat Intelligence

Critical Puppet Flaw Under Active Attack: Why Your Configuration Server Is a Prime Target

The Hacker News · 18 Nov 2026
Key Takeaway If you run Puppet or OpenVox, patch to the fixed versions now and check that your certificate authority does not automatically sign certificate requests.

The US Cybersecurity and Infrastructure Security Agency (CISA) has added a critical flaw in Perforce Puppet to its Known Exploited Vulnerabilities catalog, citing reports that attackers are already using it. Puppet is an enterprise platform used to manage and configure large numbers of systems through code. The flaw, tracked as CVE-2026-115731, has a severity score of 9.4 out of 10.

The problem is a deserialization of untrusted data bug in the way Puppet processes reports. According to CISA, a client holding any certificate signed by the Puppet certificate authority (CA) can run arbitrary code on the Puppet Server, as the service user, by submitting a report containing a specially crafted data type. If the CA automatically signs certificate requests without strong verification, an unauthenticated attacker on the network can obtain a valid certificate and then exploit the flaw. The issue also affects OpenVox, an open-source implementation of Puppet. Perforce released fixes on November 3, 2026.

Security researcher Alain Rödel of Neodyme AG reported the flaw, along with a second critical issue, CVE-2026-115732 (CVSS 9.0), a certificate-name authorization bypass affecting both Puppet and OpenVox. Neodyme said AI assistance was used in the discovery. It warned that an attacker with code execution on a Puppet server can steal the CA signing keys and impersonate other hosts. Because Puppet often has full access to a fleet of systems, the researchers describe worst-case outcomes including ransomware deployment, mass data theft and lateral movement.

There are no public details yet on how attackers are using the flaw. However, a Reddit user reported on November 4 that exploitation began shortly after public disclosure, tracing an intrusion back after finding a badly misconfigured CA in their fleet. US federal agencies have been told to apply fixes by December 1, 2026.

Why it matters

This flaw breaks the assumption that a CA-signed agent certificate is a trustworthy credential: with auto-signing enabled, an outsider can get one and reach code execution on the server that controls the whole fleet. Organisations with loosely configured CAs are most exposed, and a compromise there can include theft of CA signing keys, so patching alone may not undo an intrusion. It forces a review of certificate signing policy as well as software versions.

What to do

  • Upgrade Perforce Puppet Enterprise and OpenVox to the fixed versions released by the vendors.
  • Disable automatic certificate signing on the Puppet CA, or require strong verification of requests.
  • Review the CA for unexpected or unrecognised signed certificates, a sign of misconfiguration seen in reported intrusions.
  • Treat any Puppet server that may have been exploited as compromised and consider rotating CA signing keys.
Puppet CVE-2026-115731 Remote Code Execution CISA KEV Configuration Management

Summarised by CISO AI from The Hacker News, written with Claude Sonnet 5.5. We link back to every original so you can read it yourself.