ZeroDayAlert

CVE-2026-115731: Perforce Puppet Enterprise Deserialization of Untrusted Data Vulnerability

Perforce Puppet Enterprise contains a deserialization of untrusted data vulnerability in Puppet’s report-processing code that allows a client with any CA-signed agent certificate to execute arbitrary code on the Puppet Server as the service user by submitting a report containing a crafted rich-data type through a PUT request. If the certificate authority automatically signs requests without strong verification, an unauthenticated network attacker can obtain a valid certificate and exploit the vulnerability.

Perforce Puppet Enterprise Added to KEV 2026-11-17 Federal due 2026-12-01 Known ransomware use

Required action — quoted from CISA

Apply mitigations in accordance with vendor instructions, ensuring compliance with CISA’s BOD 26-04 Prioritizing Security Updates Based on Risk (see URL in Notes) guidance and CISA’s “Forensics Triage Requirements” (see URL in Notes). Follow applicable BOD 26-04 guidance for cloud services or discontinue use of the product if mitigations are unavailable. Stakeholders are responsible for evaluating each asset's internet exposure and ensuring adherence to BOD 26-04 patching guidelines.

Where this comes from. The identifier, product, dates and required action above are copied verbatim from the CISA Known Exploited Vulnerabilities catalog. The action plan below is written by an AI agent from that record and published automatically. AssurePort has not independently tested this vulnerability and makes no claim about whether any specific system is affected.

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

  1. Contact Perforce for patching guidance and timelines specific to your Puppet Enterprise version. The vendor instructions are authoritative.
  2. 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.
  3. Reconfigure your certificate authority to enforce strong verification before signing agent certificates. Avoid automatic signing of all requests.
  4. Enable and centralise logging of all PUT requests to the report endpoint. Log certificate details, source IP, and report contents where feasible.
  5. 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.
  6. 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.

Get these the morning they land.

One email, only when a vulnerability is newly confirmed as exploited — the CISA record plus our action plan. No more than one a day, and nothing on quiet days.

Knowing it exists is not the same as knowing you are exposed.

This page can tell you that CVE-2026-115731 is being exploited. It cannot tell you whether Puppet Enterprise is running somewhere of yours that is reachable. That question is what a scan answers.

Check your own surface →