Exploited Puppet flaw puts the server that configures your endpoint fleet at risk (CVE-2026-115731)
Puppet is currently under active attack due to a flaw that enables unauthorized code execution, elevating this situation beyond a typical disclosure.

Puppet is currently under active attack due to a flaw that enables unauthorized code execution, elevating this situation beyond a typical disclosure.
The affected service can be accessed over the network without authentication.
Puppet may already be functioning normally in your environment while remaining accessible from networks that attackers can reach.
The active exploitation transforms the situation entirely: this has shifted from a theoretical risk to a live attack method.
While specific details about the in-the-wild attacks have not yet been disclosed, the US Cybersecurity and Infrastructure Security Agency (CISA) included the flaw in its Known Exploited Vulnerabilities catalog on Tuesday and directed US federal civilian agencies to address it by December 1, 2026.
CVE-2026-115731 is a deserialization of untrusted data vulnerability in Puppet’s report-processing code, which is responsible for handling the reports that agents send back after each configuration run.
Anyone using Puppet is at risk, and since this flaw can be accessed without authentication, exposure is not contingent on user action.
Attackers are exploiting CVE-2026-115731, a critical remote code execution vulnerability in Perforce Puppet Enterprise, a solution utilized by IT teams for centralized endpoint management.
Perforce Puppet operates on a client-server model, where a central Puppet Server contains the configuration code for each managed machine, and a Puppet agent installed on every endpoint periodically checks in with the server to retrieve and apply its configuration.
This vulnerability is tracked as CVE-2026-115731 and is rated critical severity, which should be referenced when checking vendor guidance.
While requiring a signed agent certificate may appear to be a significant barrier to exploitation, if the CA signs certificate requests without stringent verification (such as when autosigning is enabled), an unauthenticated attacker on the network could obtain a certificate and exploit the vulnerability.
If exploited, this vulnerability could enable an attacker to execute arbitrary code on the Puppet Server with the privileges of its service account.
Perforce released security updates addressing CVE-2026-115731 and CVE-2026-115732, a certificate name authorization bypass flaw also reported by Alain Rödel of Neodyme AG, on November 3.
Customers should upgrade to the latest applicable security release and restart the server as soon as possible.
The fixed versions include Puppet Enterprise/Advanced 2026.0.1, 2025.12.1, or 2023.8.13, and Puppet Core 9.1.3 or 8.22.2, with the company advising customers unable to upgrade immediately to review their autosign configuration and authorization rules as a temporary mitigation.
Why it matters
The potential gain for an attacker: successful exploitation allows them to execute code with the permissions of the affected process.
Such systems are intentionally positioned at the network's edge, precisely where attackers focus their scans as soon as a CVE is disclosed.
A client holding any certificate signed by the Puppet CA can submit a report containing a crafted rich-data type via a PUT request, prompting the server to execute arbitrary code with the privileges of the Puppet Server service user, according to CISA.
What security teams should do
- Verify whether Puppet is present in your asset and software inventory.
- Treat any exposed instances as urgent, as exploitation has already been reported.
- Patching should be prioritized for any organization relying on autosigning or whose Puppet Server is accessible from untrusted networks (it listens on port 8140 by default).