Puppet Server RCE actively exploited
Actively exploited
Risk assessment
Puppet Server deserialization lets any CA-signed agent run code as the service user (CVSS 9.9), now exploited in the wild. Patch Puppet.
What to do
The vendor has published a patch — see the "Vendor Patch" link in the references section. If you cannot patch immediately, review mitigation guidance in this advisory and monitor for exploitation attempts.
- Install the vendor fix: vendor patch
- Remediation and mitigation in this advisory
Actively exploited in the wild - CVE-2026-115731 is a critical deserialization vulnerability in Puppet and Puppet Server that lets any client holding a CA-signed agent certificate execute arbitrary code on the Puppet Server as its service user. Because deployments that autosign certificate requests without strong verification hand out certificates freely, an unauthenticated network attacker can often reach the same code execution path.
Overview
Puppet agents send reports back to the Puppet Server for processing. That report pipeline deserializes data submitted by the client, and CVE-2026-115731 is a case where a crafted rich-data type inside a report is deserialized without adequate safety checks. An attacker who can submit a PUT request with a malicious report triggers object instantiation that leads to code execution.
Two conditions set the severity:
- Low barrier to entry. Any valid CA-signed agent certificate is enough. You do not need admin rights on the Puppet Server, only the ability to authenticate as an agent.
- Autosigning widens the blast radius. If your certificate authority autosigns requests without strong verification, an attacker on the network can request and receive a certificate, then attack without any prior foothold.
The vulnerability is rated CRITICAL at CVSS 9.9, with a network attack vector, low complexity, low privileges required, and no user interaction. The EPSS score sits at roughly 0.4 percent, so while broad internet-wide scanning pressure is currently modest, the confirmed active exploitation and the ease of the prerequisite (one signed cert) make this a priority for anyone running an exposed Puppet Server.
Impact
Successful exploitation gives the attacker code execution as the Puppet Server service user. From there the practical consequences are severe: the service account typically has read access to the certificate authority material, node definitions, and catalog data that describe your entire fleet. An attacker can sign new certificates, impersonate nodes, push configuration changes to managed systems, and pivot deeper into infrastructure. In short, compromise of the Puppet Server is close to compromise of everything it manages.
Remediation and mitigation
- Patch first. Apply the vendor release that fixes the report-processing deserialization path. Check the official Puppet security advisory for the exact fixed versions and upgrade Puppet Server and the puppet agent accordingly.
- Tighten certificate autosigning. Remove or restrict autosign entries that do not perform strong verification. Require policy-based or challenge-based autosigning, and audit the autosign configuration file for wildcard or blanket entries.
- Restrict network exposure. Puppet Server’s report and catalog endpoints should only be reachable from managed nodes, not the open internet. Enforce this at the firewall and with network policy.
- Audit existing certificates. Review the CA for unexpected signed certificates and revoke anything you cannot account for.
- Rotate secrets. If compromise is suspected, treat CA keys and service credentials as exposed and rotate them.
For related incident coverage, see breach reports and security news.
Security Insight
Configuration management servers are among the highest-value targets in any environment precisely because they hold the keys to the rest of the fleet, yet they are often treated as internal-only plumbing and left with permissive autosign rules. This case echoes earlier deserialization incidents in Java and Ruby ecosystems, where trust in “internal” input formats repeatedly turned into remote code execution. The real lesson is that the certificate authority is now an attack surface: if obtaining a signed certificate is trivial, then every authenticated code path in the product is effectively unauthenticated.
Further Reading
Related
- CVE-2026-93674 · Langflow unauthenticated RCEOct 7, 2026
- CVE-2026-60004 · Gitea unauthenticated RCE exploited in wildAug 26, 2026
- CVE-2026-72530 · TrueConf server RCE exploited in the wildAug 19, 2026
- CVE-2026-9198 · Langflow unauthenticated RCE exploited in wildJul 17, 2026
- Puppet Server RCE CVE-2026-115731 exploited by hackersNov 18, 2026