All articles

NewsNovember 17, 20264 min read

Puppet Enterprise: RCE CVE-2026-115731 exploited (CISA KEV)

CISA confirms exploitation of CVE-2026-115731: with an agent certificate, a crafted report executes arbitrary code on Puppet Server.

Monitor showing a security shield next to a row of servers, over a networked world map

On 17 November 2026 the US CISA added CVE-2026-115731, a deserialization of untrusted data vulnerability in Perforce Puppet Enterprise, to its Known Exploited Vulnerabilities (KEV) catalog. Inclusion in the catalog means CISA has evidence of real-world exploitation of the flaw.

This article is based on a single source: the CISA entry in the KEV catalog, with data from the National Vulnerability Database (NVD). The entry does not say who is exploiting the flaw, against which organizations or with which tools.

What the KEV entry says

  • Name: Perforce Puppet Enterprise Deserialization of Untrusted Data Vulnerability.
  • Added to the catalog: 17 November 2026.
  • Deadline for US federal agencies: 1 December 2026.
  • Use in ransomware campaigns: unknown («Unknown»).
  • Required action: apply mitigations according to the vendor’s instructions, in line with CISA’s BOD 26-04 directive on prioritizing security updates based on risk and its «Forensics Triage Requirements»; for cloud services follow the same directive, or stop using the product if mitigations are not available. CISA also asks organizations to assess the internet exposure of every system.

The reference to forensic triage requirements means that fixing the flaw is not enough: you also need to check whether the server has already been compromised.

Technical details

According to the description published by the NVD, the flaw lies in the report-processing code of Puppet, as used by Puppet Server. A client holding any agent certificate signed by the Puppet CA can submit, via a PUT request, a report containing a crafted «rich data» type. Deserializing that data leads to arbitrary code execution on Puppet Server, with the privileges of its service user.

The description adds an important point: if the CA automatically signs certificate requests (autosign) without strong verification, an unauthenticated network attacker can obtain a valid certificate and therefore exploit the flaw.

The weaknesses listed are CWE-502 (deserialization of untrusted data) and CWE-94 (code injection). The scores:

  • CVSS 3.1: 9.9 (critical), assigned by the NVD, vector AV:N/AC:L/PR:L/UI:N/S:C/C:H/I:H/A:H: network attack, low complexity, low privileges (the agent certificate), no user interaction and an impact that extends beyond the vulnerable component;
  • CVSS 4.0: 9.4 (critical), assigned by Puppet, with high impact on connected systems as well (SC:H/SI:H/SA:H).

The NVD entry is marked as analyzed («Analyzed»); it was published on 3 November 2026 and last modified on 18 November 2026.

Affected versions

According to NVD data (CPE configurations):

Product Affected versions
Puppet from 8.0.0 up to, but not including, 8.22.2
Puppet from 9.0.0 up to, but not including, 9.1.3
Puppet Enterprise from 2023.8.0 up to, but not including, 2023.8.13
Puppet Enterprise from 2025.0.0 up to, but not including, 2025.12.1
Puppet Enterprise 2026.0.0

For Puppet Enterprise 2026.0.0 the entry does not state the fixed version: check Perforce’s advisory «Report deserialization code execution», listed among the NVD references.

What it means for European companies

Puppet Server is the central point from which agents receive their configurations: this is why Puppet’s score reports high impact on connected systems too. The KEV catalog is binding only on US federal agencies, but it is a widely used reference for prioritizing updates. For organizations subject to NIS2 (in Italy, Legislative Decree 138/2024), which must manage vulnerabilities based on risk, a critical flaw with confirmed exploitation in a configuration management system should be handled with top priority.

What to do now

  1. Inventory: identify all Puppet Server and Puppet Enterprise installations, including test instances and those managed by suppliers, and compare their versions with the table.
  2. Update: apply the fixes and mitigations given by Perforce in its advisory and verify that they are actually installed.
  3. Automatic certificate signing: check whether the CA uses autosign and with which checks. According to the NVD, this is the condition that opens the flaw to unauthenticated attackers too.
  4. Exposure: assess, as CISA asks, whether Puppet Server can be reached from the internet or from untrusted networks.
  5. Compromise assessment, as required by CISA’s forensic triage: look for anomalous activity by the Puppet service user on the server and review the signed agent certificates to find any that do not match known machines.
  6. Updating does not remove access that has already been gained: if you see suspicious signs, contact Perforce support and treat the event as an incident.

How ARXDOME helps

ARX Shield brings the open vulnerabilities of monitored machines into the portal and lets you isolate a suspicious machine from the network. ARX Sentry collects logs and events from servers, useful for spotting anomalous activity, and ARX Expose shows which of your company’s services are visible from the internet.

Last updated:

Any questions?

Let’s talk about your company’s needs, with no obligation.

Contact us

Related articles