CISA has added a critical Puppet flaw to its Known Exploited Vulnerabilities (KEV) catalog, citing evidence of active exploitation. The bug, CVE-2026-115731, is a deserialization of untrusted data vulnerability in Perforce Puppet Enterprise, scored 9.4 on the CVSS scale.
Puppet is configuration management software: a central Puppet Server holds the configuration that agents on an organization's managed machines check in to fetch and apply. That central role is why a code execution bug on the server itself deserves fast attention.
Any trusted agent certificate is enough
According to the NVD entry, the flaw sits in the report-processing code of Puppet, as used by Puppet Server. A client that holds any agent certificate signed by the Puppet certificate authority can run arbitrary code on the Puppet Server, as the server's service user, by sending a report that contains a crafted rich-data type in a PUT request. (Deserialization bugs arise when software rebuilds objects from data it receives without checking that the data is safe to rebuild.)
The NVD description adds an important caveat. Where the certificate authority autosigns certificate requests without strong verification, an unauthenticated attacker on the network can obtain such a certificate in the first place. In those setups the bar for exploitation drops from holding a legitimate agent's certificate to simply having network access.
CISA's alert does not say who is exploiting the flaw, how widely, or what attackers did after gaining access, and neither the KEV entry nor NVD lists the affected release numbers. Perforce's own advisory carries the version details. The CVE was published to NVD on November 3, two weeks before the KEV listing.
Patch Puppet Server and tighten autosigning
Organizations running Puppet Enterprise or Puppet Server should apply Perforce's fixed releases as a priority. Because the NVD description itself names weak autosigning as the route for an unauthenticated attacker, it is also worth checking whether your certificate authority autosigns requests and, if it does, what verification it applies before signing.
Given the KEV listing, a patch is not the end of the job. CISA's Binding Operational Directive 26-04 requires US federal civilian agencies to prioritize remediation of KEV entries on publicly exposed assets, and sets expectations for when they must check whether a system was compromised before it was patched. While the directive binds only federal agencies, CISA encourages every organization to prioritize KEV vulnerabilities the same way.
The listing joins recent KEV additions covering infrastructure that sits above many other systems, including Barracuda's email gateway and UnrealIRCd. Systems that tell other systems what to do deserve the shortest patch windows in the estate.
This briefing is provided by IntelFusions for informational and defensive purposes only. It is based on sources assessed to be reliable at the time of writing, and analytic judgments carry the confidence levels indicated. Indicators of compromise are defanged; re-arm them only in controlled environments. IntelFusions is not affiliated with the organizations named and makes no warranty as to completeness or accuracy.