Science & Tech · Cybersecurity · 10 hrs ago

CISA Flags Critical Puppet Server Flaw After Reports of Exploitation

CISA Flags Critical Puppet Server Flaw After Reports of Exploitation

CISA added a critical Perforce Puppet flaw to its Known Exploited Vulnerabilities list on November 17, citing reports of attacks.

Puppet is a tool organizations use to manage software and settings across their computer systems.

The flaw, CVE-2026-115731, can let a client with a Puppet-authority-signed certificate run code on a Puppet server by sending a malicious report.

If attackers gain control of the server, they could access its certificate-signing key and affect systems it manages.

Reports of exploitation conflict with Perforce’s account: some sources describe attacks, but Perforce says it is unaware of exploitation and has found no evidence of customer data being accessed.

Perforce released fixes on November 3, and organizations are advised to update or turn off automatic certificate signing unless requests are strongly verified.

Federal agencies must fix the flaw by December 1, 2026; the flaw also affects OpenVox, which has its own fixed versions.

3 sources

Related

What people are saying

CISAU.S. cybersecurity agency
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
via The Hacker News
NeodymeCybersecurity company
Independent of the configuration, an attacker with RCE on a Puppet server can grab the CA signing keys and impersonate other hosts.
via The Hacker News
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.
via The Hacker News
Reddit user transdimensiaReddit user
After finding a severely misconfigured CA in my fleet, I traced the actions backwards on a [CVE-2026-]115731 intrusion
via The Hacker News