Who is affected
Perforce Puppet Enterprise is affected by a deserialization vulnerability in its report-processing code. Any deployment that accepts agent certificate requests and processes agent reports is at risk. The vulnerability allows code execution on the Puppet Server under the service user account. The record does not specify affected version ranges.
How to check whether this touches you
- Inventory whether you operate Puppet Enterprise (not Puppet Open Source) anywhere in your infrastructure.
- Confirm whether your Puppet Server accepts inbound reports from agents, particularly whether it is reachable from networks you do not fully control.
- Check your certificate authority configuration: determine whether your CA automatically signs agent certificate requests without strong verification, as this widens the attack surface to unauthenticated network attackers.
- If possible, retrieve the running Puppet Server version from the management console or by querying the service directly; version alone is a signal of potential exposure but does not exclude backported fixes.
What to do
- Contact Perforce for patching guidance and timelines specific to your Puppet Enterprise version. The vendor instructions are authoritative.
- If you cannot patch immediately, restrict network access to your Puppet Server: use firewall rules, VPNs, or network segmentation to limit inbound connections to known agent subnets only.
- Reconfigure your certificate authority to enforce strong verification before signing agent certificates. Avoid automatic signing of all requests.
- Enable and centralise logging of all PUT requests to the report endpoint. Log certificate details, source IP, and report contents where feasible.
- If your Puppet Server is internet-facing, escalate to your security team immediately. Refer to CISA BOD 26-04 guidance for prioritisation and patching deadlines.
- Follow your organisation's change control process before applying patches to production Puppet infrastructure.
If you find you were exposed
Exploitation of deserialization flaws typically precedes public disclosure, so review Puppet Server logs for the period before the vulnerability was added to the CISA catalog (17 November 2026) and earlier. Search for unusual PUT requests to report endpoints, especially those from unexpected certificate subjects or IP ranges. Check whether arbitrary code execution occurred by reviewing service user process logs, file modifications, and privilege escalation events during the exposure window. Log retention is often the limiting factor; retrieve and retain logs as soon as possible if breach investigations are warranted.