Perforce Puppet CVE-2026-115731 Vulnerability Explained
A critical remote code execution vulnerability in Perforce Puppet, tracked as CVE-2026-115731, is currently under active exploitation. We examine the technical details and the required security response.
Table of Contents4 sections

On November 18, 2026, reports confirmed that a critical remote code execution (RCE) vulnerability, identified as CVE-2026-115731, is being actively exploited in the wild. This vulnerability affects Perforce Puppet Enterprise and Puppet Core implementations, carrying a CVSS score of 9.4. The flaw stems from a deserialization issue that allows unauthorized actors to execute arbitrary code on Puppet Servers. To trigger this, an attacker must submit a crafted rich-data type via a PUT request, provided they possess a CA-signed agent certificate.
Technical Scope and Exploitation Mechanics
The vulnerability was discovered by security researcher Alain Rödel, who identified the flaw alongside a separate certificate-name authorization bypass. By leveraging these weaknesses, an attacker can bypass standard authentication controls. The primary risk involves the potential for attackers to gain access to CA signing keys. Once these keys are compromised, the scope of the threat expands significantly, as it may facilitate the deployment of ransomware or enable lateral movement across the affected network infrastructure. The reliance on CA-signed certificates for machine-to-machine communication underscores the necessity of robust Agent Authentication and Machine Commerce Protocols to ensure that only verified entities can interact with management servers.
Patching Requirements and Compliance
Perforce Software issued patches for the affected versions of Puppet Enterprise, Puppet Core, and OpenVox implementations on November 3, 2026. Following the disclosure of active exploitation, the Cybersecurity and Infrastructure Security Agency (CISA) added this flaw to its Known Exploited Vulnerabilities catalog. Federal Civilian Executive Branch (FCEB) agencies are now mandated to apply the necessary security updates by December 1, 2026, to remain in compliance with Binding Operational Directive 26-04. Organizations operating Puppet infrastructure should prioritize these updates to mitigate the risk of unauthorized server access.
Practical Consequences and Unknowns
While the technical mechanism of the deserialization flaw is documented, the full extent of the exploitation campaigns remains an area of ongoing analysis. The requirement for a CA-signed agent certificate acts as a barrier to entry, but once that threshold is crossed, the potential for administrative-level compromise is high. It is currently unknown how many organizations have been impacted or if additional variants of this exploit exist. Administrators should verify their current versioning against the vendor’s security advisory to ensure they are running patched software. The reliance on specific certificate-based authentication highlights the importance of maintaining strict control over agent provisioning and lifecycle management within DevOps environments.
Continue Exploring
You Might Also Like

Microsoft 365 Global Outage Post Incident Report
Microsoft detailed how three distinct technical problems combined to cause a global Microsoft 365 outage, lasting slightly under 24 hours in November 2026.

Cloudflare Workers AI fallback across workflow retries
Learn how to preserve model selection and handle provider errors correctly when retrying durable serverless AI workflow steps.

Fix pnpm audit vulnerabilities in Wrangler dependencies
Learn how to remediate transitive pnpm audit findings in Wrangler, Miniflare, and Undici without bypassing package-age policies or weakening lockfile integrity.