HomeTech NewsCybersecurityCISA Adds Puppet Enterprise RCE CVE-2026-115731 to KEV

CISA Adds Puppet Enterprise RCE CVE-2026-115731 to KEV

The US Cybersecurity and Infrastructure Security Agency has added a Perforce Puppet Enterprise remote-code-execution flaw, CVE-2026-115731, to its Known Exploited Vulnerabilities catalogue, with a federal due date of 1 December 2026.

The catalogue entry, in version 2026.11.17 dated 17 November 2026, 17:53 GMT, is titled “Perforce Puppet Enterprise Deserialization of Untrusted Data Vulnerability.” CISA says the flaw “allows a client with any CA-signed agent certificate to execute arbitrary code on the Puppet Server as the service user by submitting a report containing a crafted rich-data type through a PUT request.” “If the certificate authority automatically signs requests without strong verification, an unauthenticated network attacker can obtain a valid certificate and exploit the vulnerability.” Known ransomware campaign use is listed as “Unknown.” CISA gives no public detail on who is exploiting the flaw, how widely it is being used, or when exploitation began. The required action is to apply vendor mitigations in line with CISA’s current binding operational directive on risk-based updates.

The underlying patches are older than today’s listing. On 3 November 2026, the Vox Pupuli project published a coordinated advisory covering critical flaws in “all known Puppet implementations,” including OpenVox and Puppet Enterprise. “November 3rd was the most reasonable coordinated release date that allowed Puppet Enterprise to also be fixed and published,” the post said. “All known Puppet implementations are vulnerable to the CVEs fixed in today’s releases.” For OpenVox, it lists fixed versions of openvox-server 8.18.0 and 9.2.0, openvox-agent 8.32.0 and 9.3.0, and openvoxdb 8.18.0 and 9.2.0. The OpenVox security advisory maps the report-deserialisation issue to CVE-2026-115731 and gives a CVSS 4.0 score of 9.4. NVD, citing Perforce, lists Puppet Enterprise releases 2023.8.13, 2025.12.1 and 2026.0.1 as unaffected. The same NVD record is still marked as awaiting enrichment and does not yet carry a NIST base score of its own. The 9.4 figure used in this article is the CVSS 4.0 score in the OpenVox advisory, not a CISA or NIST score.

Catalogue version 2026.11.17 contains 1,782 entries. CISA’s addition of CVE-2026-115731 is one of those entries. This article is only about that KEV item. Vox Pupuli’s 3 November advisory also discussed other flaws fixed in the same release round; CISA has not, in catalogue 2026.11.17, added a second Puppet CVE.

What administrators can do, and what is still unknown

Vox Pupuli said that if an upgrade has to wait, the exposure can be reduced by ensuring the server is reachable only from the network segments that need access, and by disabling or tightening access to autosign. Those are the project’s mitigations, not a finding that any named operator has used them. The same post told administrators who have not yet moved off Open Source Puppet that “Puppet will not be receiving any more updates, security or not,” and pointed them to OpenVox.

The researcher who identified the server issues is named by Vox Pupuli as Alain from Neodyme. The project thanked Perforce’s Puppet security and engineering teams for coordinating a same-day Puppet Enterprise release.

The listing sits in a line of recent TSN accounts of CISA KEV additions, including the addition of a Check Point Gaia zero-day and an exploited Outlook spoofing flaw. It is a catalogue decision, rather than a new vendor-observed intrusion of the kind Huntress described in ScreenConnect this week.

Today’s news is the KEV date, not the November patches

The important clock on this story is 17 November, not 3 November. The fixes have been public since the coordinated Vox Pupuli and Puppet Enterprise releases two weeks ago. What is new is CISA’s judgement that CVE-2026-115731 is being exploited, and the 1 December due date that judgement creates for federal civilian executive-branch agencies. CISA’s short description is also the most precise public account of the condition: a client that already holds any CA-signed agent certificate, or that can obtain one if certificate requests are signed automatically without strong checks. The catalogue does not say who has used that condition, how many servers are involved, or whether ransomware operators are among them. “Unknown” on the ransomware field is an absence of public evidence, not a clearance.

The version list is similarly bounded. OpenVox has published exact package numbers. NVD, citing Perforce, identifies three Puppet Enterprise lines as unaffected once those fixes are installed. Neither source, in the material available for this report, offers a census of how many production servers remain on earlier builds. The KEV add is a reason to treat remaining unpatched servers as urgent. It is not, on its own, a measure of the campaign behind the listing.

Sources

Related stories

CISA Adds Check Point Gaia Zero-Day to Its KEV List is the closest recent TSN account of a CISA KEV addition, and is the next read.

Follow @tsnmediahub on X for breaking AI news as it happens.

Follow on X

Share this story

Latest stories

  1. Johns Hopkins Warns of US Transformer Shortages from 2027
    Data Centres & Energy

More in this category

Latest stories

  1. Johns Hopkins Warns of US Transformer Shortages from 2027
    Data Centres & Energy

Explore the TSN Atlas: Every topic we cover, mapped. Click a bubble to dive in.