Security & privacy

Active exploitation of critical Puppet and OpenVox RCE flaw confirmed by CISA

CISA adds CVE-2026-115731 to its Known Exploited Vulnerabilities catalog, citing active attacks against Perforce Puppet and OpenVox servers.

Illustration of a central server connecting to network nodes with one compromised node showing a red warning.
Illustration created for this article

The U.S. Cybersecurity and Infrastructure Security Agency (CISA) has added a critical remote code execution vulnerability affecting Perforce Puppet and OpenVox to its Known Exploited Vulnerabilities catalog. This action follows confirmed reports of active exploitation in the wild, urging immediate attention from system administrators managing enterprise infrastructure.

What happened

The vulnerability, identified as CVE-2026-115731, carries a CVSS score of 9.4 and stems from the deserialization of untrusted data within Puppet’s report-processing code. An attacker with a valid Certificate Authority (CA) signed agent certificate can execute arbitrary code on the Puppet Server by submitting a crafted report via a PUT request. The risk escalates significantly if the CA is configured to automatically sign requests without strong verification, allowing unauthenticated network attackers to obtain valid certificates and exploit the flaw.

Perforce Software released patches for this issue on November 3, 2026. The fix addresses multiple versions of Puppet Enterprise and Puppet Core. Specifically, Puppet Enterprise 2026.0.0, 2025.0.0, and 2023.8.0 are affected, along with Puppet Core 9.0.0 and 8.x branches. The open-source alternative, OpenVox, is also impacted, with fixes available in specific Agent and Server versions. CISA has mandated that Federal Civilian Executive Branch agencies apply these updates by December 1, 2026, under Binding Operational Directive 26-04.

Key details

  • Vulnerability ID: CVE-2026-115731 (CVSS 9.4) and CVE-2026-115732 (CVSS 9.0).
  • Attack Vector: Deserialization of untrusted data in report-processing code via PUT requests.
  • Prerequisite: Attacker needs a CA-signed agent certificate; weak CA verification allows unauthenticated access.
  • Affected Puppet Versions: Enterprise 2026.0.0 < 2026.0.1, 2025.0.0 < 2025.12.1, 2023.8.0 < 2023.8.13; Core 9.0.0 < 9.1.3, 8.x < 8.22.2.
  • Affected OpenVox Versions: Agent 9.3.0/8.32.0 and Server 9.2.0/8.18.0 require updates.
  • Discovery: Found by Alain Rödel at Neodyme AG using AI-assisted security research.

Background

Puppet and its fork OpenVox are central tools for infrastructure-as-code, allowing administrators to manage configurations across hundreds or thousands of servers from a single control plane. Because these systems hold high-level privileges, they are prime targets for attackers seeking lateral movement within a network. The specific flaw here involves "deserialization," a process where data is converted back into an object that the application can use. If the application trusts data from an external source without rigorous validation, an attacker can inject malicious code that executes when the server processes the data.

The severity is compounded by the role of the Certificate Authority (CA) in Puppet ecosystems. The CA issues digital certificates that authenticate agents (client servers) to the master server. If the CA is misconfigured to auto-sign any request, it effectively removes the authentication barrier, allowing any device on the network to pose as a trusted agent. Once an attacker gains remote code execution (RCE) on the Puppet server, they can potentially steal the CA signing keys, enabling them to impersonate any host in the infrastructure.

Why it matters

For teams running self-hosted configuration management, this incident highlights the catastrophic risk of centralized control planes. A compromise here does not just affect one server; it grants the attacker the keys to the kingdom. As noted by security researchers, an attacker with RCE on a Puppet server can deploy ransomware, exfiltrate mass data, or move laterally to other critical systems. The fact that exploitation was observed shortly after public disclosure suggests that threat actors are actively scanning for vulnerable instances, particularly those with weak CA configurations.

This event also underscores the importance of rigorous certificate management and verification protocols. Many organizations may have enabled auto-signing for convenience during initial setup, forgetting to tighten security as their fleet grew. The reliance on automated tools like Puppet means that any vulnerability in the core software can propagate rapidly. System administrators must treat the Puppet server as a high-value asset, equivalent to a domain controller, and apply patches with the same urgency.

What you can do

  • Patch immediately: Upgrade to Puppet Enterprise 2026.0.1, 2025.12.1, or 2023.8.13, or the corresponding Core and OpenVox versions.
  • Audit CA configuration: Disable auto-signing of certificate requests and enforce strict verification policies for all new agents.
  • Review network access: Restrict access to the Puppet Server’s API endpoints to trusted IP ranges only.
  • Monitor for indicators: Check logs for unusual PUT requests to report-processing endpoints and unexpected certificate issuance.
  • Rotate keys if compromised: If you suspect prior exploitation, revoke existing CA keys and re-issue certificates for all agents.
  • Verify OpenVox installations: If using the open-source fork, ensure you are on Agent 9.3.0/8.32.0 or Server 9.2.0/8.18.0 or later.

More news

All news