Back Redpacketsecurity CVE Alert: CVE-2026-115731 – Perforce
Deserialization of untrusted data in the report-processing code of Puppet, as used by Puppet Server, in the affected releases, allows a client that holds any CA-signed agent certificate to execute arbitrary code on the Puppet Server as its service user by submitting a report containing a crafted rich-data type via PUT request. Where the certificate authority autosigns requests without strong verification, an unauthenticated network attacker can obtain such a certificate.
**Risk verdict:** Urgent: active exploitation is reported, and exposed Puppet Server instances should be investigated and remediated immediately.
**Why this matters:** Successful exploitation can give an attacker code execution as the server’s service account, with potential to disrupt configuration management or access sensitive infrastructure data. Because Puppet Server is a central management component, compromise may also provide a foothold for broader intrusion; the extent depends on its permissions and network reach.
**Most likely attack path:** A network-reachable server can be targeted without user interaction, but the attacker needs a CA-signed agent certificate. Weakly verified automatic certificate signing could make that prerequisite easier to obtain; otherwise, a compromised or maliciously controlled agent is the more likely route. Scope-impact indicators suggest effects may extend beyond the server itself.
**Who is most exposed:** Organisations running Puppet Enterprise with Puppet Server reachable from agent networks are most at risk, especially where certificate autosigning is enabled or server access is broadly permitted.
Review Puppet Server logs for unusual report-submission requests, especially from unexpected agents.
Check for abnormal child processes, command execution, or files created by the Puppet Server service account.
Audit recent certificate requests, autosigning decisions, and newly trusted agents.
Hunt for unexpected outbound connections from Puppet Server.
Mitigation and prioritisation
Treat as priority 1 due to active exploitation; upgrade to a vendor-fixed release and restart Puppet Server.
Restrict server access to trusted agent networks while patching.
Disable or tightly validate autosigning; revoke suspicious certificates.
Preserve logs and investigate for service-account compromise before restoring normal access.
A considerable amount of time and effort goes into maintaining this website, creating backend automation and creating new features and content for you to make actionable intelligence decisions. Everyone that supports the site helps enable new functionality.
If you like the site, please support us on Patreon or Buy Me A Coffee using the buttons below.
The full story
This article is one source in a clustered incident — the cluster page carries the summary, timeline and every other outlet covering it.
