CVE-2026-115731
Puppet Enterprise report deserialization code execution in Puppet Server (CVE-2026-115731)
Puppet Enterprise's Puppet Server deserialises untrusted report data. A CA-signed agent certificate allows code execution as the service user; autosigning without verification extends this to unauthenticated attackers. CISA KEV lists active exploitation. Fixed: 2023.8.13, 2025.12.1, 2026.0.1.
What happened
The report-processing code in Puppet Server deserialises untrusted data in affected Puppet Enterprise releases. An attacker who holds any CA-signed agent certificate can submit a crafted report containing a malicious rich-data type via a PUT request, leading to arbitrary code execution on the Puppet Server as its service user. The CVSS 4.0 vector describes a network attack with low privileges, no user interaction, and high impact across confidentiality, integrity and availability on both the vulnerable system and subsequent systems (score 9.4).
Where the certificate authority autosigns requests without strong verification, an unauthenticated network attacker can obtain such a certificate, removing the need to hold credentials.
Active exploitation is recorded by CISA KEV, CISA SSVC (active), and ENISA EUVD (exploited since 2026-11-17). CISA added the flaw to KEV on 2026-11-17, with a due date of 2026-12-01.
Who is affected
Affected versions are Puppet Enterprise 2023.8.0 through before 2023.8.13, 2025.0.0 through before 2025.12.1, and 2026.0.0 through before 2026.0.1. Puppet Server is the central component that agents report to, so this affects organisations running Puppet Enterprise in a configuration-management or infrastructure-automation role. The risk is higher where the certificate authority autosigns agent certificate requests without strong verification, because that can remove the need for an attacker to hold a valid certificate.
What to do now
- Patch to the fixed release for your line: Puppet Enterprise 2023.8.13, 2025.12.1, or 2026.0.1 as appropriate.
- Follow CISA's required action for KEV entry CVE-2026-115731: apply vendor mitigation instructions and align with CISA BOD 26-04 prioritisation and forensics triage guidance. CISA's due date is 2026-12-01.
- If patching cannot be completed immediately, restrict network access to the Puppet Server report endpoint and review the certificate authority's autosigning policy so that unverified requests cannot obtain an agent certificate.
- Because active exploitation is recorded, treat unpatched Puppet Servers as potentially compromised and review for signs of post-exploitation activity.
How to detect it
Monitor Puppet Server logs for unexpected PUT requests to the report-processing endpoint, particularly submissions that contain rich-data type structures. If autosigning is enabled, review newly issued agent certificates for hosts you do not recognise. Certificate issuance records can help identify whether an unauthenticated attacker obtained a trusted certificate before patching.
Beyond the patch
Active exploitation on a management server means patch first, then investigate. Our Managed Detection & Response (MDR) service monitors for the post-exploitation activity that follows code execution on central infrastructure, matching the detection and response focus CISA's guidance calls for. If you are unsure whether your Puppet Server is reachable from untrusted networks or whether autosigning would admit an unauthorised certificate, an assessment from Implementation & Assessment Services can identify the exposure before it is used.
Affected and fixed versions
| Product | Affected | Fixed in |
|---|---|---|
| Puppet Enterprise | 2023.8.0 – < 2023.8.13 2025.0.0 – < 2025.12.1 2026.0.0 – < 2026.0.1 | 2023.8.13 2025.12.1 2026.0.1 |