CISA Adds Critical Puppet Enterprise Deserialization Flaw CVE-2026-115731 to Its Known Exploited Vulnerabilities Catalog
CISA says attackers are exploiting a critical deserialization flaw in Puppet Enterprise and open-source Puppet Core; a researcher also reported a second, unexploited certificate-impersonation bug.
Editor's Note ·
- Correction:
- The article states that CVE-2026-115732's CVSS v4.0 score of 9.0 is a score "NVD scores." NVD's own CVE API (services.nvd.nist.gov) shows this score's source is [email protected] (type: Secondary) -- it is Puppet's own vendor-submitted score, merely hosted on NVD's page. NVD has not yet completed an independent (Primary) analysis of this CVE; its status is "Awaiting Analysis."
Overview
The U.S. Cybersecurity and Infrastructure Security Agency added a critical flaw in Perforce’s Puppet Enterprise configuration-management software to its Known Exploited Vulnerabilities (KEV) catalog on November 17, 2026, citing reports of active exploitation, according to CISA’s KEV catalog. The vulnerability, tracked as CVE-2026-115731, lets a client that holds any certificate-authority-signed Puppet agent certificate execute arbitrary code on the Puppet Server, CISA says.
What We Know
CISA’s catalog entry describes the flaw as a “deserialization of untrusted data vulnerability in Puppet’s report-processing code that 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,” and adds that “if the certificate authority automatically signs requests without strong verification, an unauthenticated network attacker can obtain a valid certificate and exploit the vulnerability,” according to CISA.
The bug carries different severity scores depending on the standard used: Puppet’s own submission to the National Vulnerability Database rates it 9.4 under CVSS version 4.0, the figure also cited by The Hacker News, while NVD’s own primary scoring under the older CVSS version 3.1 rates the flaw higher, at 9.9.
The flaw affects Puppet Enterprise 2026.0.0 before 2026.0.1, 2025.0.0 before 2025.12.1, and 2023.8.0 before 2023.8.13, as well as the open-source Puppet Core engine versions 9.0.0 before 9.1.3 and 8.x before 8.22.2, according to The Hacker News, which reports that Perforce Software addressed the issue on November 3, 2026. The same report-deserialization flaw also affects OpenVox, a community-maintained open-source fork of Puppet, and was fixed in OpenVox Agent 9.3.0 and 8.32.0 and OpenVox Server 9.2.0 and 8.18.0, according to both The Hacker News and OpenVox’s own security advisory, which rates the bug “Critical” and lists OpenVox Agent versions up to 9.2.0 and 8.31.1, and OpenVox Server versions up to 9.1.0 and 8.17.0, as affected.
The vulnerability was discovered and reported by Alain Rödel, a security researcher at the German cybersecurity firm Neodyme AG, who also found a second, related flaw, CVE-2026-115732, a certificate-name authorization bypass affecting both Puppet and OpenVox that NVD scores at 9.0 under CVSS 4.0 — a score The Hacker News also cites. Unlike CVE-2026-115731, CVE-2026-115732 does not appear in CISA’s KEV catalog, and NVD’s own exploitation-status assessment for that CVE lists it as not currently exploited. According to The Hacker News, the two flaws were discovered with artificial-intelligence assistance and precise steering, Neodyme told the outlet, which also quoted the firm saying “the impact highly depends on the Puppet server configuration and the orchestration protocols used, if any are enabled at all,” and adding that “independent of the configuration, an attacker with RCE on a Puppet server can grab the CA signing keys and impersonate other hosts.” Neodyme also warned that “Puppet is a powerful software, often with full access to a fleet of systems in a corporate network,” and that remote code execution on such a system “can lead to worst-case scenarios: Deployment of ransomware, mass data exfiltration, and potentially lateral movement to other parts of the network,” The Hacker News reports.
The Hacker News reports that a Reddit user named transdimensia posted on November 4 that the flaw was already being exploited, writing: “After finding a severely misconfigured CA in my fleet, I traced the actions backwards on a [CVE-2026-]115731 intrusion.” Federal civilian agencies are required to apply the fix by December 1, 2026, under Binding Operational Directive 26-04, according to CISA.
What We Don’t Know
CISA’s catalog lists the vulnerability’s use in ransomware campaigns as “Unknown.” The Hacker News states that, as of its reporting, there were no details on how the vulnerability is being weaponized in the wild beyond the single Reddit account of a compromise traced to a misconfigured certificate authority. None of the cited sources state how many organizations have been affected or whether the exploitation CISA cites is widespread or limited to isolated incidents.