A Puppet Enterprise server can have the security update on disk while the running service has yet to load it. Perforce’s vulnerability record tells administrators to upgrade and restart Puppet Server. That second step matters now that the Cybersecurity and Infrastructure Security Agency added CVE-2026-115731 to its Known Exploited Vulnerabilities catalog on November 17.
Puppet Server sends configuration to the machines it manages and receives reports from them. Perforce says the flaw is in the server’s handling of those reports and can let someone run code with the Puppet Server service account’s privileges. The vendor’s release notice identifies three Puppet Enterprise releases with the fix: 2023.8.13, 2025.12.1 and 2026.0.1.
For the change record, capture the Puppet Enterprise release on the server and the time Puppet Server restarted. Then check the console for a fresh run report from a managed node. The Status page shows the most recent run for each node, so a result dated before the restart cannot tell you whether reporting resumed afterward. Check Operational status for infrastructure issues as well. The version and restart document the patch. A fresh report checks that the normal flow of work resumed for that node.
CISA’s catalog entry gives December 1 as the due date and directs federal teams to assess each asset’s internet exposure under its risk-based directive. The directive governs federal civilian executive branch agencies. Perforce’s upgrade and restart guidance applies to customers running affected releases. The catalog establishes that the flaw has been exploited in the wild. Whether a particular server was compromised before the update is a separate incident-response question.