Puppet Enterprise is on CISA's exploited list. It configures your whole fleet.
By Lior AharonovFounder, 7IT Solutions ·
What happened
On Tuesday 17 November, CISA added CVE-2026-115731 in Perforce Puppet Enterprise to its Known Exploited Vulnerabilities catalog, with a 1 December deadline for federal agencies. Any client with a CA-signed agent certificate can run code on the Puppet Server through a crafted report. If the CA autosigns without strong checks, an unauthenticated attacker can get that certificate.
Why it matters
The OpenVox advisory for the same bug says the code runs as the puppet user with access to the CA signing key. Whoever holds that key can sign trusted certificates, and the advisory warns that can reach other hosts when orchestration is set up.
What to do
Apply the Perforce fix linked from CISA's KEV entry and stop autosigning without strong verification. On OpenVox, upgrade Server to 9.2.0 or 8.18.0 and Agent to 9.3.0 or 8.32.0, then look for certificates you never issued.

My take
Lior Aharonov
Founder, 7IT Solutions
Configuration management holds the master key to every server you own. Patch the locksmith first.
Sources
| CISA: CISA Adds One Known Exploited Vulnerability to Catalog | cisa.gov |
| OpenVox security advisory GHSA-ffr6-rwpm-p5wq: Authenticated RCE via Event Deserialization | github.com |
Researched with AI tools; every fact is checked against the linked sources.