Puppet Enterprise CVE-2026-115731: CVSS 9.4 Deserialization Flaw Exploited and Added to CISA KEV
Dr. Abeer Alshammari · Published 11/19/2026
CISA added Puppet Enterprise CVE-2026-115731 (CVSS 9.4) to its Known Exploited Vulnerabilities catalog on 17 November 2026. Patched releases have been available since 3 November. Federal deadline: 1 December 2026.
What happened
CISA listed an unsafe deserialization flaw in Puppet Server, the component that processes reports sent by Puppet agents, as exploited in the wild. Perforce, which owns Puppet, shipped fixes on 3 November 2026 and at that time said it knew of no attacks. CISA's later KEV entry cites evidence of active exploitation, but neither the attackers nor the number of victims have been named in the sources reviewed.
Why it matters
Puppet Server sits at the centre of configuration management. Code execution on it can reach the many servers it manages, so one compromised server can become a route into an entire fleet.
Who is affected
Puppet Enterprise before 2023.8.13, before 2025.12.1 and the 2026.0.0 release, plus Puppet Core builds before 9.1.3 and 8.22.2, as reported. Organisations running automatic certificate signing are at higher risk.
Technical impact
An attacker holding a certificate signed by the Puppet certificate authority can send a crafted report over HTTP PUT and run code with the privileges of the Puppet Server service account. If the CA signs certificate requests automatically without verification, an attacker with network access may be able to obtain such a certificate.
Governance impact
This is a control-plane risk. Configuration management servers should be classed as critical assets, with patch deadlines, certificate-issuance approval and logging owned by named people. For entities that follow CISA KEV timelines as a benchmark, the 1 December date is a useful reference point.
What security teams should do
Upgrade to Puppet Enterprise 2026.0.1, 2025.12.1 or 2023.8.13, or Puppet Core 9.1.3 or 8.22.2. Until then, restrict network access to the report service and turn off automatic certificate signing unless requests are strongly verified. Review recent certificate enrolments, look for unexpected processes started by the Puppet Server account, and if compromise is suspected, check whether the signing key or managed configurations were touched, because patching does not undo changes already made.
What executives should know
The patch exists and the exposure is manageable if acted on now. Ask for confirmation that every Puppet Server is on a fixed version and that certificate signing is controlled, and treat any gap as an incident risk, not a routine update.
Sources: CISA KEV alert of 17 November 2026 (the CISA page could not be opened directly, so details were checked against Security Affairs and Cybersecurity News), and Perforce release information as relayed by those outlets. Mitigation steps should be confirmed in the Perforce advisory.
Try it yourself
An interactive CyberAbeer experience for this topic is in development.
Coming soon