The US Cybersecurity and Infrastructure Security Agency (CISA) added one actively exploited vulnerability to its Known Exploited Vulnerabilities catalog on November 17, 2026. The flaw, CVE-2026-115731, affects Perforce Puppet Enterprise. It can let an attacker run code on the Puppet Server, and US federal agencies must address it by December 1, 2026.
| CVE | Vendor and product | Weakness | Added | US federal deadline | Known ransomware use |
|---|---|---|---|---|---|
| CVE-2026-115731 | Perforce Puppet Enterprise | Deserialization of Untrusted Data | 2026-11-17 | 2026-12-01 | Unknown |
Deadlines in the catalog are binding only on US federal civilian agencies. For everyone else, they are a useful benchmark: once CISA lists a flaw, it has confirmed that attackers are using it, and two weeks is a reasonable target for any organization running the affected product.
Perforce Puppet Enterprise: Code Execution Through Agent Reports
The weakness sits in the code that processes reports sent to the Puppet Server. Puppet clients submit these reports through a PUT request. A report can carry a specially crafted rich-data type, and the server deserializes it without treating it as untrusted input.
The result is remote code execution. An attacker who succeeds can run commands of their choosing on the Puppet Server, with the privileges of the service account the server runs under.
The attack has one precondition: the client must hold an agent certificate signed by the Puppet certificate authority. Any signed certificate is enough, so the attacker does not need one tied to a particular trusted machine.
That precondition is weaker than it looks in some setups. If the certificate authority automatically approves signing requests without strong checks, an attacker with network access but no prior credentials can request a certificate, receive it, and then exploit the flaw. Organizations that rely on automatic signing face the highest exposure.
Who should care: any organization running Perforce Puppet Enterprise, especially where the Puppet Server is reachable from networks an attacker might reach, or where certificate signing is automatic. The server is central to the environment it manages, so a compromise there deserves serious attention.
What to do: apply the vendor’s update or mitigation. CISA’s required action is to apply mitigations according to the vendor’s instructions, while following its BOD 26-04 guidance on prioritizing security updates by risk and its “Forensics Triage Requirements.” For cloud deployments, the applicable BOD 26-04 cloud guidance applies. If no mitigation is available, CISA directs agencies to stop using the product.
CISA lists ransomware use of this flaw as unknown. That means no confirmed link to ransomware campaigns has been recorded. It does not mean the risk is low.
What to Do This Week
- Find every Puppet Enterprise deployment and Puppet Server in your environment, including test and cloud instances.
- Apply Perforce’s update or mitigation for CVE-2026-115731 as soon as possible, and no later than the December 1, 2026 benchmark.
- Check whether your certificate authority signs agent requests automatically. If it does, tighten verification so that only known machines receive certificates.
- Review the list of signed agent certificates, and revoke any you cannot match to a known system.
- Look at the Puppet Server for signs of compromise, such as unexpected processes or files owned by the service account, and preserve evidence before you clean anything up.
FAQ
– Does an attacker need credentials to exploit CVE-2026-115731?
The attacker needs an agent certificate signed by the Puppet certificate authority. If that authority signs requests automatically without strong verification, an attacker with no prior access can obtain one and then carry out the attack.
– Is this Puppet flaw being used in ransomware attacks?
CISA lists known ransomware use as unknown. The flaw is confirmed as actively exploited, which is why it entered the catalog on November 17, 2026.
– Does the December 1 deadline apply to private companies?
No. The deadline binds US federal agencies only. Other organizations can use it as a practical target for fixing the flaw.