Exploited deserialization flaw in Puppet Enterprise allows code execution on Puppet Server
CISA has added a Puppet Enterprise flaw, CVE-2026-115731, to its Known Exploited Vulnerabilities catalogue; it lets a crafted agent report run arbitrary code on the Puppet Server. Any organisation managing systems with Puppet Enterprise is concerned, especially where the certificate authority signs requests automatically.
What to do now
- Product
- Perforce Puppet Enterprise
- Affected versions
- —
- CVE
- CVE-2026-115731
On 17 November 2026, the US Cybersecurity and Infrastructure Security Agency added CVE-2026-115731, affecting Perforce Puppet Enterprise, to its catalogue of vulnerabilities exploited in the wild. The weakness sits in the code the Puppet Server uses to process reports sent by agents.
That code deserializes untrusted data. A client holding any agent certificate signed by the Puppet certificate authority can send a PUT request carrying a report with a crafted rich-data type, causing the server to run arbitrary code as the Puppet service user. Because the Puppet Server drives configuration across many machines, a compromise there can spread its impact to the whole managed estate.
The exposure is much worse when the certificate authority automatically signs requests without strong verification. In that setup, an unauthenticated attacker with network access can obtain a valid certificate on their own and then exploit the flaw.
The source does not list affected or fixed versions. It points to a Perforce advisory and tells organisations to apply the vendor's mitigations, or stop using the product if none are available. US federal agencies must comply by 1 December 2026. Whether the flaw has been used in ransomware campaigns is listed as unknown.
What to do now
- Read Perforce's advisory for this vulnerability and apply the fix or mitigations it describes without delay.
- Turn off automatic certificate signing on the Puppet certificate authority, or enforce strict verification of signing requests.
- Review the list of signed agent certificates and revoke any you cannot account for.
- Check the Puppet Server for signs of compromise, such as unusual processes or files associated with the Puppet service account.
- As general good practice, restrict network access to the Puppet Server to managed nodes only.