Back to Insights
  • Enterprise

· ASC Editorial Team

The Server That Configures Everything: Puppet Enterprise Flaw Now Exploited

On 17 November 2026, CISA, the US cyber security agency, added CVE-2026-115731 to its catalogue of known exploited vulnerabilities, "based on evidence of active exploitation". The flaw is in Perforce Puppet Enterprise, and CISA describes it as the deserialisation of untrusted data. Perforce disclosed it on 3 November, and its fixes are in Puppet Enterprise 2023.8.13, 2025.12.1 and 2026.0.1. CISA hasn't said who is exploiting it or how widely.

Puppet is configuration management software. A central Puppet server tells every machine it manages how it should be set up: which software to install, which accounts exist, which settings apply. That is what makes it useful, and it is why an attacker who controls the Puppet server can change every one of those machines at once.

According to published analyses of the flaw, an attacker needs a machine holding a certificate signed by the Puppet server's own certificate authority. With that, they can send the server crafted data and run code on it. A second flaw fixed in the same releases, CVE-2026-115732, concerns how the server checks certificate names. That makes the way certificates are issued as important as the patch.

This is the third trusted management tool to be exploited in a week. We wrote about N-central, used by IT providers to manage their customers' computers, and about Confluence joining it in the Apache Axis attacks. The lesson is the same each time: the tools that manage everything else need the strongest protection.

If you run Puppet Enterprise, three steps follow.

First, patch the Puppet server to a fixed release, and check whether your agents need updating too.

Second, review how certificates are signed. If the server signs requests automatically, check what its rules allow. Signing any request without checking it means anyone who can reach the server can join the estate. Look at the list of signed certificates for machines you don't recognise.

Third, treat the Puppet server as one of your most sensitive systems. Limit which networks can reach it, keep administrative access to a small, named group, and review its logs and recent configuration changes for anything you didn't expect.

Who in your organisation can get a certificate signed by your Puppet server, and would you know if someone new did?

Source: CISA: CISA adds one known exploited vulnerability to catalog

Get Insights by email

A short round-up of new articles every Monday morning. Nothing else.

We only keep your email address, and we don't track opens or clicks. Every email has an unsubscribe link. See our Privacy Notice.