Critical Puppet RCE Bug Under Active Attack — Fixes Urgently Needed

Enterprise environments using Puppet and its derivatives are facing a severe security risk from a newly exposed remote code execution (RCE) vulnerability. The U.S. Cybersecurity and Infrastructure Security Agency (CISA) has officially added the flaw—CVE-2026-115731—to its Known Exploited Vulnerabilities Catalog, citing verified incidents of exploitation. The bug allows attackers to run arbitrary code on Puppet servers if certain conditions are met.

What’s the Vulnerability?

Puppet—as both the Perforce Puppet Enterprise suite and OpenVox open-source components—is susceptible to a vulnerability caused by unsafe deserialization of untrusted data in its report-processing subsystem. Specifically, a client possessing any certificate signed by the Puppet Certificate Authority can submit a malicious report via a PUT request containing a crafted “rich-data” type. This opens the door to executing arbitrary code under the service user on the Puppet server.

An attacker might not even need full authentication, particularly if their organization’s CA setup automatically signs requests without robust verification. In such cases, almost any network-based attacker could generate a valid certificate and exploit the flaw without being properly authenticated.

Affected Versions and Patches

The issue impacts multiple versions of Puppet products:

  • Puppet Enterprise 2026.0.0 (before 2026.0.1), 2025.0.0 (before 2025.12.1), 2023.8.0 (before 2023.8.13)
  • Puppet Core 9.0.0 (before 9.1.3), and Core 8.x versions prior to 8.22.2
  • OpenVox Agent versions below 9.3.0 and 8.32.0; OpenVox Server versions before 9.2.0 and 8.18.0

Perforce and related maintainers released fixes on November 3, 2026. Users are urged to upgrade to:

  • Puppet Enterprise versions 2026.0.1, 2025.12.1, 2023.8.13
  • Puppet Core versions 9.1.3 and 8.22.2
  • OpenVox Agent 9.3.0 / 8.32.0, and OpenVox Server 9.2.0 / 8.18.0

Scope of Risk and Real-World Exploitation

The vulnerability’s real danger depends heavily on how organizations configure their Puppet servers and how their certificate authorities operate. Once compromised, Puppet servers grant access to Certificate Authority (CA) signing keys, which can then be used to pose as other trusted hosts.

Because Puppet is often woven deeply into corporate infrastructure—managing fleets of machines across environments—an adversary gaining RCE on these servers could deploy ransomware, exfiltrate data on a large scale, or move laterally within a network.

While official technical details on in-the-wild exploitation remain limited, a user on Reddit claimed that attacks began shortly after the disclosure. That user traced an intrusion tied to CVE-2026-115731 following discovery of a misconfigured CA in their network.

Government Advisory & Deadlines

Federal agencies under the U.S. Federal Civilian Executive Branch have been instructed to apply the patches by December 1, 2026, under Binding Operational Directive 26-04. The aim is to bolster security by addressing high-risk software vulnerabilities with known exploits.

Key Technical Risk Explained

Deserialization flaws are among the most dangerous in software security. They involve unsafe handling of data that, when manipulated, can cause programs to perform unintended actions. In this case, the attack vector lies in untrusted data parsed and processed by the report-handling path on Puppet servers. That makes even a CA-validated certificate a potential weapon if CA policies are lax.

Organizations must assess whether their certificate authorities automatically sign requests without stringent validation. If so, they should assume urgent exposure and act quickly—either by tightening CA controls or updating Puppet/OpenVox to the patched versions immediately.

This vulnerability highlights a broader trend: infrastructure tooling is becoming a frequent target, especially configuration management platforms. When attackers compromise systems like Puppet that orchestrate many downstream systems, the blast radius becomes enormous. The urgency around CVE-2026-115731 underscores the need for proactive security hygiene, particularly in certificate trust models and automation platforms. Going forward, expect similar risks in other orchestration tools—and a push for stricter CA policies will become a central part of enterprise security strategy.

What to Watch

  • Whether additional exploit tools are being released for CVE-2026-115731 and related flaws
  • Patterns in misconfigured CAs leading to proof of concept attacks, especially via open issue trackers or forums
  • How vendors like Perforce and OpenVox respond with guidance around hardening CA setup
  • Federal enforcement of the December 1 deadline and how agencies manage patch deployment