--- title: "Puppet CVE-2026-115731 in KEV: Patch Puppet Server Now" url: https://playciso.com/blog/puppet-cve-2026-115731-kev updated: 2026-11-19 section: Blog publisher: PlayCISO --- # Puppet CVE-2026-115731 in KEV: Patch Puppet Server Now > CISA added Puppet Server RCE CVE-2026-115731 to KEV (due 1 Dec). Fixed Puppet Enterprise, Puppet Core and OpenVox versions, and autosign checks. Source: https://playciso.com/blog/puppet-cve-2026-115731-kev · Published: 2026-11-19 · Publisher: PlayCISO (https://playciso.com) Primary source: https://www.cisa.gov/known-exploited-vulnerabilities-catalog?field_cve=CVE-2026-115731 --- **CISA says CVE-2026-115731, a critical flaw in Puppet Server, is being exploited, and federal agencies must fix it by 1 December 2026.** CISA added it to the [Known Exploited Vulnerabilities catalog](https://www.cisa.gov/known-exploited-vulnerabilities-catalog?field_cve=CVE-2026-115731) with a date added of **17 November 2026**. Per the [CVE record](https://www.cve.org/CVERecord?id=CVE-2026-115731) Perforce published on 3 November, any client that holds a CA-signed Puppet agent certificate can execute code on the Puppet Server, as the server's service user, by submitting a crafted report; where the certificate authority autosigns requests without strong checks, an unauthenticated attacker can get that certificate. Perforce rates it **CVSS v4.0 9.4**. Fixes shipped on 3 November in Puppet Enterprise, Puppet Core and the community fork OpenVox. CISA has not said who is exploiting it or against whom. **Who this is for:** CISOs, infrastructure and platform leads, and anyone who runs Puppet Enterprise, Puppet Core, open source Puppet or OpenVox. A Puppet Server pushes configuration to every managed machine, so code running on it is a path to all of them. *Based on the CISA KEV catalogue, the CVE.org and NVD records, Perforce's Puppet Core release notes, the OpenVox project's notices and advisories, Neodyme's write-up and the Debian security tracker, all read on 19 November 2026. PlayCISO is not affiliated with Perforce, Vox Pupuli or Neodyme. We publish no exploit details.* Confirmed vs not yet known **Perforce confirms (CVE record, 3 Nov 2026):** deserialization of untrusted data in Puppet's report-processing code lets a client with any CA-signed agent certificate run code on Puppet Server via a crafted report sent by PUT. Affected Puppet Enterprise releases are 2023.8.0 to before 2023.8.13, 2025.0.0 to before 2025.12.1 and 2026.0.0 to before 2026.0.1. **CISA confirms exploitation:** CVE-2026-115731 is in the KEV catalog, date added 17 November 2026, due 1 December 2026. Known ransomware use: "Unknown". Forensic triage flag: "No". **OpenVox confirms:** the flaws affect "all known OpenVox and Puppet versions and implementations"; fixed in OpenVox Server 9.2.0 and 8.18.0 and OpenVox Agent 9.3.0 and 8.32.0. Open source Puppet will not receive security updates. **Not established:** who exploited it, against which organisations, since when, and whether attackers obtained certificates through autosigning or already held one. No public source we read describes the in-the-wild activity. ## Affected and fixed versions | Product | Affected | Fixed | Source | | --- | --- | --- | --- | | Puppet Enterprise 2023.8 (LTS) | 2023.8.0 to before 2023.8.13 | 2023.8.13 | CVE record (Perforce) | | Puppet Enterprise 2025 | 2025.0.0 to before 2025.12.1 | 2025.12.1 | CVE record (Perforce) | | Puppet Enterprise 2026 | 2026.0.0 to before 2026.0.1 | 2026.0.1 | CVE record (Perforce) | | Puppet Core 8 | Earlier releases (Perforce's notes give no range) | 8.22.2 | Puppet Core 8.22.2 release notes | | Puppet Core 9 | Earlier releases (Perforce's notes give no range) | 9.1.3 | Puppet Core 9.1.3 release notes | | OpenVox Server | 9.1.0 and earlier; 8.17.0 and earlier | 9.2.0 and 8.18.0 | GHSA-ffr6-rwpm-p5wq | | OpenVox Agent | 9.2.0 and earlier; 8.31.1 and earlier | 9.3.0 and 8.32.0 | GHSA-ffr6-rwpm-p5wq | | OpenVoxDB | Updated in the same release set | 9.2.0 and 8.18.0 | OpenVox notice | | Open source Puppet | Affected, per OpenVox | No upstream fix: migrate to OpenVox, or use a distribution's patched package | Vox Pupuli, Debian | - Update the server and the agents. The code runs where reports are processed, on the Puppet Server, but the OpenVox advisory lists both its agent and server packages as affected, and Perforce ships the fix in Puppet Core releases. Follow your product's upgrade path for both. - Distribution packages. The [Debian security tracker](https://security-tracker.debian.org/tracker/CVE-2026-115731) lists fixed puppet-agent packages for bookworm (7.23.0-1+deb12u1, DLA-4884-1) and trixie (8.10.0-5+deb13u1, DSA-6608-1). Check your own vendor; a distro package can carry the fix under its own version string. - Dates. Neodyme says the fixes and the Perforce and OpenVox advisories were released together on 3 November 2026 at 17:00 UTC. Perforce's Puppet Core release-notes pages say "Released November 2026". ## What the flaw is, without the exploit After every run, a Puppet or OpenVox agent sends the server a report: a JSON document listing what changed, warnings and failed resources. The [OpenVox project explains](https://www.openwall.com/lists/oss-security/2026/11/03/14) that, with some custom resource types, a report event can carry a serialized Ruby object rather than plain JSON, and the server turns it back into an object when it processes the report. A malicious object can be built so that code runs on the server at that moment. The attacker needs network access to the Puppet Server and a valid signed agent certificate. That second condition is weaker than it sounds. The CVE record warns that where the CA "autosigns requests without strong verification", an unauthenticated network attacker can obtain such a certificate. Any single compromised managed node already has one. [Neodyme](https://neodyme.io/en/blog/puppet_rce), whose researcher Alain reported the issues, says the flaws date back to 2021, that the RCE works against the Puppet server "in a default configuration", and that both were found with AI assistance. Neodyme also says "an environment hardened according to the best practices will mitigate direct impact significantly." Its post contains technical detail; we do not repeat it. ## The second flaw: CVE-2026-115732 The same disclosure fixed [CVE-2026-115732](https://www.cve.org/CVERecord?id=CVE-2026-115732) (CVSS v4.0 9.0), a certificate-name authorization bypass in `trapperkeeper-authorization`, the library that applies the rules in `auth.conf`. Per the CVE record, a client whose certificate name "extends or shortens an authorized hostname" can be authorized as that host; in Puppet Enterprise, Perforce says, that reaches certificate-authority administration and remote command execution on managed nodes. Exploitation needs a certificate with a colliding name, issued "by approval or autosign". The [OpenVox advisory](https://github.com/OpenVoxProject/trapperkeeper-authorization/security/advisories/GHSA-q4hm-33rc-572g) says plain-string rules wrongly behaved like wildcards. It is fixed in the same releases and is **not** in the KEV catalog as of 19 November 2026. After upgrading, OpenVox advises checking custom `auth.conf` rules, because some may have relied on the old behaviour. ## Timeline | Date | Event | Source | | --- | --- | --- | | 3 Nov 2026 | Perforce and OpenVox release fixes and advisories together at 17:00 UTC; Neodyme publishes its write-up | Neodyme, Vox Pupuli | | 3 Nov 2026 | OpenVox posts its notice to oss-security: Server 9.2.0/8.18.0, Agent 9.3.0/8.32.0, OpenVoxDB 9.2.0/8.18.0; open source Puppet gets no updates | oss-security | | 3 Nov 2026 | CVE-2026-115731 and CVE-2026-115732 published by Perforce (CVSS v4.0 9.4 and 9.0) | CVE.org, CVE.org | | Nov 2026 | Puppet Core 8.22.2 and 9.1.3 release notes list fixes for both CVEs (PA-9587, PA-9117) | Perforce, Perforce | | 17 Nov 2026 | CISA adds CVE-2026-115731 to the KEV catalog, due 1 December 2026 | CISA KEV | ## What security leaders should do this week - Find every Puppet Server, compiler and CA you run, and patch it. Puppet Enterprise to 2023.8.13, 2025.12.1 or 2026.0.1; Puppet Core to 8.22.2 or 9.1.3; OpenVox Server to 9.2.0 or 8.18.0, with agents on 9.3.0 or 8.32.0. Include compile servers, lab and disaster-recovery instances, and container images. If you still run open source Puppet, plan the move to OpenVox or a supported product now: it will not get this fix upstream. - Review autosigning. Check whether autosign is set to true in puppet.conf, what autosign.conf allows (basic autosigning trusts any name that matches a pattern, which anyone can claim), and whether a policy-based autosign script really verifies something a stranger cannot forge, such as a pre-shared token in the CSR attributes. Turn autosigning off where you do not need it. - Audit the certificates the CA has already signed. List signed certificates and compare them with your inventory of managed nodes. Revoke and clean any certname you cannot account for, especially names signed automatically since 3 November or names that are close variants of real hostnames (the CVE-2026-115732 pattern). - Check Puppet Server logs for unusual report submissions. Look at the access logs for report uploads from certnames that are new, unknown or not in your inventory, unusually large reports, and report traffic at odd times, and check the server for processes the Puppet service user started that it should not. If anything looks wrong, treat the server as compromised: it can reach every managed node. - Restrict who can reach port 8140. Puppet Server listens on TCP 8140 by default. Allow it only from the networks where managed nodes live, never from the internet, and keep the CA service on the narrowest path you can. - Check custom auth.conf rules after upgrading. OpenVox warns that rules may have relied on the old wildcard behaviour fixed for CVE-2026-115732. - Rotate what the server holds if you find signs of compromise. Hiera secrets, eyaml keys, cloud and database credentials in manifests, and the CA itself. Plan the order with the [Key Rotation Planner](/tools/key-rotation-planner). - Rank and record it. Check it in the [KEV checker](/tools/kev-checker/CVE-2026-115731), set a deadline with the [BOD 26-04 calculator](/tools/bod-26-04-calculator) or the [SSVC calculator](/tools/ssvc-calculator), and log any server you cannot patch this week in your [risk register](/tools/risk-register) with an owner and a date. For other recent KEV additions, see our posts on [ScreenConnect CVE-2026-84869](/blog/cve-2026-84869-screenconnect-rogue-clients) and [PHP2Shell](/blog/php2shell-ai-agent-credential-harvesting). For the vendor's entry, see [Perforce (Puppet) in the Breach Index](/breach-index/perforce). CVE-2026-115731 is a vulnerability in Puppet software, not a breach of Perforce or the OpenVox project. ## Frequently asked questions ### What is CVE-2026-115731? CVE-2026-115731 is a critical flaw in the report-processing code of Puppet, as used by Puppet Server. Per the CVE record Perforce published, a client that holds any CA-signed agent certificate can execute arbitrary code on the Puppet Server, as the server's service user, by submitting a crafted report through a PUT request. Perforce rates it CVSS v4.0 9.4 (CWE-502, deserialization of untrusted data, and CWE-94, code injection). ### Is CVE-2026-115731 in the CISA KEV catalog? Yes. CISA lists it in the Known Exploited Vulnerabilities catalog with a date added of 17 November 2026 and a due date of 1 December 2026. CISA marks known ransomware use as "Unknown" and the forensic-triage flag as "No". A KEV listing means CISA has evidence of exploitation; CISA has not published details of who exploited it or how. ### Which Puppet versions fix CVE-2026-115731? Puppet Enterprise 2023.8.13, 2025.12.1 and 2026.0.1, per the CVE record (affected: 2023.8.0 up to 2023.8.13, 2025.0.0 up to 2025.12.1 and 2026.0.0 up to 2026.0.1). Puppet Core 8.22.2 and 9.1.3, per Perforce's release notes. OpenVox Server 9.2.0 and 8.18.0 and OpenVox Agent 9.3.0 and 8.32.0, per the OpenVox project. ### Is open source Puppet affected, and will it be fixed? The OpenVox project says the two flaws affect "all known OpenVox and Puppet versions and implementations" and that open source Puppet "will not be receiving security updates". It recommends migrating to OpenVox. Some Linux distributions patch their own puppet-agent packages: Debian, for example, lists fixed packages for bookworm and trixie. ### Do attackers need a certificate to exploit CVE-2026-115731? Yes, a CA-signed agent certificate. The CVE record warns that where the certificate authority autosigns requests without strong verification, an unauthenticated network attacker can obtain such a certificate. That makes autosign configuration the first thing to check after patching. ### What is CVE-2026-115732? A second critical flaw found by the same researcher: a certificate-name authorization bypass in trapperkeeper-authorization, used by Puppet Server (CVSS v4.0 9.0). A client with a certificate whose name extends or shortens an authorized hostname can be authorized as that host. Perforce says that in Puppet Enterprise this can reach CA administration and remote command execution on managed nodes. It is fixed in the same releases. It is not in the KEV catalog as of 19 November 2026. ### Who found the Puppet Server vulnerabilities? Alain of Neodyme reported them, according to the OpenVox project and Neodyme. Neodyme says it found them while preparing a red team engagement, that they date back to 2021, and that they were found with AI assistance. Fixes and advisories from Perforce and OpenVox were released together on 3 November 2026 at 17:00 UTC. ### Is there evidence of exploitation in the wild? Only the KEV listing itself. CISA added the flaw on 17 November 2026, which means it has evidence of exploitation, but no public source we read describes the attacks, the victims or an attacker. Treat any exposed Puppet Server that was unpatched after 3 November as worth checking. ### Was Perforce or Puppet hacked? No. Nothing reported shows a breach of Perforce or the OpenVox project. CVE-2026-115731 is a vulnerability in Puppet software; the exposure is to organisations that run an unpatched Puppet Server. ## Sources - [CISA Known Exploited Vulnerabilities catalog: CVE-2026-115731, date added 17 November 2026, due 1 December 2026](https://www.cisa.gov/known-exploited-vulnerabilities-catalog?field_cve=CVE-2026-115731) - [Perforce: Report Deserialization Code Execution (CVE-2026-115731)](https://portal.perforce.com/s/cve/a91Qi000003IaHpIAK/report-deserialization-code-execution) and [Certificate Name Authorization Bypass (CVE-2026-115732)](https://portal.perforce.com/s/cve/a91Qi000003IaJRIA0/certificate-name-authorization-bypass) - [CVE.org: CVE-2026-115731](https://www.cve.org/CVERecord?id=CVE-2026-115731) and [CVE-2026-115732](https://www.cve.org/CVERecord?id=CVE-2026-115732) (CNA Perforce; affected Puppet Enterprise ranges; CVSS v4.0) - [Perforce: Puppet Core 8.22.2 release notes](https://help.puppet.com/core/8/Content/PuppetCore/PuppetReleaseNotes/release_notes_puppet_x-8-22-2.htm) and [Puppet Core 9.1.3 release notes](https://help.puppet.com/core/9/Content/PuppetCore/PuppetReleaseNotes/release_notes_puppet_x-9-1-3.htm) - [OpenVox project: OpenVox Server RCE and client impersonation vulnerabilities (oss-security, 3 November 2026)](https://www.openwall.com/lists/oss-security/2026/11/03/14) - [Vox Pupuli: critical CVE updates (3 November 2026)](https://voxpupuli.org/blog/2026/11/03/critical-cve-updates/) - [OpenVox advisory GHSA-ffr6-rwpm-p5wq](https://github.com/OpenVoxProject/openvox/security/advisories/GHSA-ffr6-rwpm-p5wq) and [trapperkeeper-authorization advisory GHSA-q4hm-33rc-572g](https://github.com/OpenVoxProject/trapperkeeper-authorization/security/advisories/GHSA-q4hm-33rc-572g) - [NVD: CVE-2026-115731](https://nvd.nist.gov/vuln/detail/CVE-2026-115731) - [Neodyme: Pulling the right strings for RCE on a Puppet (3 November 2026)](https://neodyme.io/en/blog/puppet_rce) - [Debian security tracker: CVE-2026-115731](https://security-tracker.debian.org/tracker/CVE-2026-115731)