Puppet Enterprise CVE-2026-115731 Exploited, Added to KEV
Security

Puppet Enterprise CVE-2026-115731 Exploited, Added to KEV

CISA added Puppet Enterprise CVE-2026-115731 to KEV on Nov 17. The CVSS 9.4 report flaw gives code execution on Puppet Server. Patch by Dec 1.

puppetcisa kevdeserializationconfiguration managementrce

CISA added Puppet Enterprise CVE-2026-115731 to the Known Exploited Vulnerabilities catalog on 17 November 2026. The CVSS 9.4 flaw sits in Puppet Server's report-processing code: any client holding a CA-signed agent certificate can run code on the server as the Puppet service user. Perforce shipped fixes on 3 November in Puppet Enterprise 2023.8.13, 2025.12.1 and 2026.0.1. Federal agencies have until 1 December. If your Puppet CA autosigns requests, treat this as unauthenticated remote code execution and patch today.

What happened

Perforce published CVE-2026-115731 on 3 November 2026 together with fixed releases of Puppet Enterprise and Puppet Core. The CVE record describes deserialization of untrusted data in the report-processing code that Puppet Server runs when an agent submits its run report. A report containing a crafted rich-data type causes the server to execute attacker-supplied code as its service user. The weakness is tracked as CWE-502 (deserialization of untrusted data) and CWE-94 (code injection). The CVSS 4.0 vector is AV:N/AC:L/AT:N/PR:L/UI:N with high impact on confidentiality, integrity and availability for both the vulnerable system and downstream systems.

The same day, the OpenVox project (the community fork of Puppet) published GitHub advisory GHSA-ffr6-rwpm-p5wq for the identical bug in OpenVox Server and OpenVox Agent, rated critical with the same 9.4 score. Both advisories credit a researcher at Neodyme AG. The Hacker News names the reporter as Alain Rödel and notes that Neodyme found the issues with AI assistance.

Two weeks later, on 17 November, CISA added the CVE to KEV. The catalog entry lists the vendor as Perforce, the product as Puppet Enterprise, ransomware use as "Unknown" and a remediation due date of 1 December 2026 under Binding Operational Directive 26-04. CISA's catalog is reserved for flaws with evidence of active exploitation.

There is a disagreement to note. SecurityAffairs reports that Perforce says it is not aware of attacks exploiting the flaw and has found no evidence of customer data being accessed. The Hacker News points to a Reddit post from 4 November, one day after disclosure, in which a user claimed to have traced an intrusion in their fleet to this bug after finding a badly misconfigured CA. That post is unverified. The KEV listing is the authoritative signal here: CISA does not add entries without exploitation evidence, even when the vendor has not seen it.

Who is affected

The CVE record lists these Puppet Enterprise ranges as vulnerable:

  • 2023.8.0 up to but not including 2023.8.13
  • 2025.0.0 up to but not including 2025.12.1
  • 2026.0.0 up to but not including 2026.0.1

Open-source users are affected too. The Hacker News and Ostorlab report that Puppet Core 8.x before 8.22.2 and 9.0.0 before 9.1.3 carry the bug. The OpenVox advisory lists OpenVox Agent 9.2.0 and earlier and 8.31.1 and earlier, and OpenVox Server 9.1.0 and earlier and 8.17.0 and earlier, as vulnerable.

Exposure depends on who can obtain a certificate from your Puppet CA. The attacker needs a certificate signed by the CA that the Puppet Server trusts. In a fleet where every signing request is approved by a human, that means an attacker must first compromise a managed node or steal its certificate and key. In a fleet where the CA autosigns requests without strong verification, anyone who can reach TCP port 8140 can request a certificate, receive it, and then send the malicious report. The CVE record and the KEV entry both call out this configuration explicitly. If you still rely on an autosign.conf allowlist, Puppet's own documentation says that mode is insecure because any host can claim any certname. Our guide on how to disable Puppet autosign and audit agent certificates covers the fix.

The companion flaw: CVE-2026-115732

Perforce published a second critical bug on the same day. CVE-2026-115732 (CVSS 9.0) is an incorrect-authorization flaw in the certificate-name matching of trapperkeeper-authorization, the library Puppet Server uses to decide which certificate may call which endpoint. A client holding a CA-signed certificate whose name extends or shortens an authorized hostname is treated as that host. In Puppet Enterprise this allows impersonation of other nodes, access to certificate-authority administration, and remote command execution on managed nodes. The weakness types are CWE-863 and CWE-697. The same fixed releases (2023.8.13, 2025.12.1, 2026.0.1) close it. This flaw is not in KEV, but it is the obvious second step for an attacker who has already obtained a certificate, so patch for both at once. For background on this bug class, see what incorrect authorization (CWE-863) means.

Technical analysis

Puppet agents check in with the server over mutual TLS. At the end of each run an agent uploads a report describing every resource it evaluated and every event that occurred. Ostorlab's write-up traces the flaw to the code that rebuilds transaction events from the report hash. Puppet's rich-data format lets a report declare the type of a value using a type tag, and the server trusted that tag enough to construct and evaluate a Ruby class from it. The report endpoint is PUT /puppet/v3/report, which every agent certificate is authorized to call. No user interaction is involved and the request looks like a normal agent check-in.

This is a textbook case of insecure deserialization (CWE-502): a serialization format that can express "construct an object of type X" is handed data from a party that should only be allowed to describe facts. The fix in 8.22.2 and 9.1.3 restricts what the report deserializer will instantiate.

The impact is larger than one server. Neodyme's assessment, quoted by The Hacker News, is that an attacker with code execution on a Puppet server can obtain the CA signing keys and impersonate any other host regardless of configuration. Ostorlab adds that the attacker can read every node's reports and facts and change the catalogs the server hands out. Catalogs are instructions that agents run as root on every managed machine. That is why a Puppet server, like any configuration management server, is a Tier 0 asset.

What to do now

  1. Patch. Upgrade Puppet Enterprise to 2023.8.13, 2025.12.1 or 2026.0.1. Upgrade Puppet Core to 8.22.2 or 9.1.3. Upgrade OpenVox Server to 8.18.0 or 9.2.0 and OpenVox Agent to 8.32.0 or 9.3.0. Ostorlab notes that Puppet Core and puppetserver package version numbers differ, so confirm the fixed version through your distribution channel rather than guessing.
  2. Check your autosign setting. On the CA server, look at the autosign setting in the [server] section of puppet.conf. A value of true signs everything. A path to a non-executable file is a certname allowlist, which Puppet documents as insecure. Set autosign = false or move to a policy executable that verifies a secret embedded in the CSR.
  3. Audit issued certificates. Run puppetserver ca list --all and compare against your inventory. Any certname you do not recognize is a lead.
  4. Search the access log. Ostorlab recommends searching Puppet Server's access log for PUT /puppet/v3/report requests from certificate names you do not manage. A failed attempt may leave only that request behind. A successful one may leave no command output in Puppet's logs at all, so also review processes and recently written files owned by the puppet user.
  5. Restrict port 8140. Limit it to the agents and consoles that need it. This does not fix the bug, but it removes the unauthenticated path when autosign is misconfigured.
  6. If you find an unknown certificate or signs of execution, assume the CA is compromised. Ostorlab's advice is to rebuild the server, rotate the CA and reissue every agent certificate. Rotating the CA is disruptive, which is exactly why attackers target it.

CISA's required action also points to its Forensics Triage Requirements. Preserve the Puppet Server access log, the CA's signed and requested certificate directories and the service user's shell and file history before you rebuild.

What to watch next

Perforce's public position and CISA's catalog currently disagree on exploitation. Expect one of three things: Perforce updates its advisory to acknowledge attacks, an incident response firm publishes indicators, or CISA changes the "Known Ransomware Campaign Use" field. Watch also for CVE-2026-115732 to join KEV, since certificate-name impersonation is the natural follow-on once an attacker holds a certificate. Debian and Red Hat trackers list the open-source puppet-agent package, so distribution updates may lag the upstream fix. Verify the installed Puppet Core version, not just the package name.

Sources