CISA added a Puppet Enterprise flaw, CVE-2026-115731, to its Known Exploited Vulnerabilities catalog on November 17. The entry describes a deserialization bug in Puppet’s report-processing code that lets a client holding any CA-signed agent certificate run code on the Puppet Server as the service user.

According to the KEV entry, the attacker submits a report containing a crafted rich-data type through a PUT request. If the certificate authority signs requests automatically without strong verification, CISA adds, an unauthenticated network attacker can obtain a valid certificate and exploit the flaw. CISA lists a December 1 due date for federal agencies and marks known ransomware use as unknown.

The bug is in the open-source line too. Security firm Neodyme, whose researcher Alain reported it, says it dates back to 2021 and allows code execution on the server in a default configuration. The OpenVox fork published fixed versions on November 3: Server 8.18.0 and 9.2.0, Agent 8.32.0 and 9.3.0, and OpenVoxDB 8.18.0 and 9.2.0. Perforce lists the fixed Puppet Enterprise and Puppet Core builds in its advisory.

A configuration management server has a path to every host it manages. “An attacker with RCE on a Puppet server can grab the CA signing keys and impersonate other hosts,” Neodyme writes. Neodyme also reports a second flaw, CVE-2026-115732, a certificate-name check that lets one host pose as another.

In our reading, the autosign setting decides how much of the first flaw an outsider can reach, and Neodyme notes that most large companies enable it. The OpenVox project advises limiting the server to the network segments that need it and tightening autosign where teams cannot upgrade yet, and warns that these steps do not remove the risk. We have argued that management interfaces belong on a network only administrators reach. Patch first, then review what the CA signed since early November. Rapid7 reported exploitation of another central tool this week.

Source: CISA Known Exploited Vulnerabilities Catalog