What changed
Exploitation evidence raises the urgency
Perforce fixed CVE-2026-115731 in Puppet Server's report-processing path earlier this month. On 17 November, CISA added it to the Known Exploited Vulnerabilities catalogue. A client with any certificate signed by the Puppet certificate authority can submit a crafted report and execute code on the server as the service user. CISA says an unauthenticated network attacker may first obtain a certificate if the CA auto-signs requests without strong verification.
The fixed Puppet Enterprise and Enterprise Advanced releases are 2026.0.1, 2025.12.1 and 2023.8.13; Puppet Core fixes are 9.1.3 and 8.22.2. The same release also addresses CVE-2026-115732, a separate certificate-name authorization bypass. CISA's KEV entry specifically names CVE-2026-115731.
The certificate condition matters
Defender workflow
Protect the server that manages the fleet
- 1
Confirm the server build. Identify Puppet Enterprise, Advanced and Core servers, then upgrade to the applicable fixed release. Verify the service restarted into that build.
- 2
Check certificate issuance. Review CA auto-signing rules, recently issued agent certificates and unexpected node identities. Tighten weak issuance rules while the upgrade is prepared.
- 3
Look back at reports and server activity. Review unusual report submissions and Puppet Server process behavior during the exposure window. Preserve logs before assuming the patch resolved an earlier compromise.
Defender note
The central server has wider reach
Puppet can distribute configuration and software to managed machines. If investigation finds server compromise, scope the trust chain and subsequent changes across the fleet, rather than stopping at the single host. CISA's federal remediation date is 1 December 2026; other organizations should prioritize according to their own exposure and the observed exploitation.