Mastodon Mastodon Mastodon Mastodon

Puppet remote code execution vulnerability added to CISA KEV catalog: who is affected and what to do

Photo of author

CyberSecureFox Editorial Team

Published:

On November 17, 2026, CISA added a critical vulnerability CVE-2026-115731 in the configuration management platform Puppet by Perforce to its Known Exploited Vulnerabilities (KEV) catalog. The deserialization of untrusted data vulnerability allows arbitrary code execution on the Puppet server and is rated 9.4 under CVSS 4.0. Puppet Enterprise, Puppet Core and the related OpenVox project are affected. Patches have been available since November 3, 2026, and U.S. federal agencies have a remediation deadline of December 1, 2026. Organizations using Puppet for infrastructure management must immediately update server components or apply workarounds.

Vulnerability mechanism and exploitation conditions

CVE-2026-115731 is related to report processing on the Puppet server side. A client with a valid agent certificate signed by the Puppet certificate authority (CA) can send a PUT request with a report containing a specially crafted rich-data object. When this object is deserialized on the server, arbitrary code is executed under the service user account.

The key question is how an attacker obtains a valid client certificate. According to the OpenVox project advisory, the vulnerability formally requires authentication. However, as the Neodyme research team notes, many large infrastructures have certificate autosigning enabled, which is used by orchestration systems like Satellite or Ansible to automatically onboard new hosts. In such configurations, an attacker can obtain a valid certificate via the registration endpoint without any authentication, effectively turning the vulnerability into an unauthenticated attack vector.

This is the crucial distinction: the vulnerability is not unconditionally unauthenticated, but the autosign configuration — common in corporate environments — removes the authentication barrier.

Affected products and fixed versions

The vulnerability affects several product lines:

Puppet Enterprise and Puppet Core

  • Puppet Enterprise 2026.0.0 through 2026.0.1
  • Puppet Enterprise 2025.0.0 through 2025.12.1
  • Puppet Enterprise 2023.8.0 through 2023.8.13
  • Puppet Core 9.0.0 through 9.1.3
  • Puppet Core 8.x through 8.22.2

Perforce released fixes on November 3, 2026: Puppet Enterprise 2026.0.1, 2025.12.1, 2023.8.13, as well as Puppet Core 9.1.3 and 8.22.2.

OpenVox

According to the OpenVox advisory, OpenVox Agent versions up to 9.2.0 and up to 8.31.1 are affected, as well as OpenVox Server versions up to 9.1.0 and up to 8.17.0. The fixes are OpenVox Agent 9.3.0 / 8.32.0 and OpenVox Server 9.2.0 / 8.18.0.

Related vulnerability: CVE-2026-115732

In parallel with the deserialization vulnerability, CVE-2026-115732 (CVSS 4.0: 9.0) was disclosed — a flaw in the certificate name matching mechanism (CWE-697, incorrect comparison). According to the GitHub Advisory Database entry, a client with a certificate whose name is an extension or truncation of an authorized host name can be authorized as that host. This allows an attacker to impersonate other Puppet nodes and, in the case of Puppet Enterprise, gain access to certificate authority administration.

It is important not to conflate these two vulnerabilities: they have different exploitation prerequisites. CVE-2026-115731 requires a valid client certificate (or autosign), whereas CVE-2026-115732 requires a certificate with a colliding name, issued via autosign or manual approval. At the same time, only CVE-2026-115731 has been added to the CISA KEV catalog and should be given top priority for remediation.

Impact assessment

Puppet is a configuration management platform that often has full access to the fleet of servers in a corporate network. According to Neodyme, successful code execution on the Puppet server allows an attacker to extract CA signing keys and impersonate other hosts in the infrastructure. The downstream impact depends on the server configuration and enabled orchestration protocols, but potentially includes deployment of malware, mass data exfiltration and lateral movement across the network.

As for active exploitation: CISA has added the vulnerability to KEV, citing reports of exploitation. However, at the time of publication, public details of attacks, attribution to specific threat actors, the scale of any campaign, or technical indicators of compromise have not been established. A reported incident on Reddit from a user who discovered an intrusion via a misconfigured CA has not been confirmed by independent sources.

Remediation recommendations

  1. Update server components to fixed versions: Puppet Enterprise 2026.0.1 / 2025.12.1 / 2023.8.13, Puppet Core 9.1.3 / 8.22.2, OpenVox Agent 9.3.0 / 8.32.0, OpenVox Server 9.2.0 / 8.18.0.
  2. If immediate updating is not possible, the OpenVox project recommends restricting network access to the server only to those segments that genuinely need it, and disabling or tightening autosign settings.
  3. Review autosign configuration: if automatic certificate signing is enabled without strict verification, the vulnerability effectively becomes unauthenticated.
  4. Review logs for suspicious PUT requests to the reports endpoint and unusual certificate issuance requests.

CVE-2026-115731 is the only one of the two disclosed vulnerabilities that has been added to the CISA KEV catalog, with a remediation deadline for federal agencies set for December 1, 2026. For commercial organizations using Puppet as a central element of infrastructure management, update priority should be similar: the combination of a critical CVSS rating, confirmed exploitation and the widespread use of autosign makes this vulnerability one of the most dangerous for corporate configuration management environments.


CyberSecureFox Editorial Team

The CyberSecureFox Editorial Team covers cybersecurity news, vulnerabilities, malware campaigns, ransomware activity, AI security, cloud security, and vendor security advisories. Articles are prepared using official advisories, CVE/NVD data, CISA alerts, vendor publications, and public research reports. Content is reviewed before publication and updated when new information becomes available.

Leave a Comment

This site uses Akismet to reduce spam. Learn how your comment data is processed.