Puppet RCE CVE-2026-115731 Is Exploited: Patch, Fix CA
CISA added Puppet's CVE-2026-115731 to KEV. Patched builds shipped Nov 3. Here is the patch order and the CA auto-signing check that decides your exposure.

Patch your Puppet servers first, then check whether your certificate authority auto-signs requests. CISA added CVE-2026-115731 to its Known Exploited Vulnerabilities catalog on Tuesday, November 17, and federal agencies have until December 1 to fix it under BOD 26-04. The Hacker News reports a CVSS score of 9.4.
What changed
CVE-2026-115731 is a deserialization of untrusted data flaw in the report-processing code of Puppet Enterprise and Puppet Core. Per CISA’s description, a client holding any CA-signed agent certificate can run code on the Puppet Server as the service user by submitting a crafted report. The details of how it is being used in attacks are not public. SecurityWeek says exploitation was flagged on November 4, and that a proof-of-concept aimed at OpenVox appeared shortly after the patch.
Perforce warns that a successful attack could expose the server’s certificate-signing key, let an attacker issue trusted certificates, and change the software and configuration delivered to managed systems on their next Puppet run. That is why a Puppet server is a high-value target: it sits in front of the whole fleet.
Why the CA setting matters
The flaw needs a valid certificate. If your CA auto-signs requests without strong verification, an unauthenticated network attacker can get one. Perforce’s advice is to turn off auto-signing and enforce strong validation so only trusted systems and authorized users receive certificates. Neodyme, whose researcher Alain Rödel reported the bug, says the impact depends heavily on server configuration and which orchestration protocols are enabled.
What to do, in order
- Patch. Fixes shipped November 3: Puppet Enterprise 2026.0.1, 2025.12.1 and 2023.8.13, and Puppet Core 9.1.3 and 8.22.2. Affected ranges are anything earlier in the 2026.0.x, 2025.x and 2023.8.x Enterprise lines and the 9.0.x and 8.x Core lines.
- OpenVox users: the project is affected too. Fixed versions are OpenVox Server 9.2.0 and 8.18.0, and OpenVox Agent 9.3.0 and 8.32.0.
- Disable CA auto-signing and require real verification of every certificate request. Do this even after patching.
- Review your CA. Look for agent certificates you do not recognize, especially any issued since early November.
- If a server was exposed unpatched, treat the CA signing key as possibly compromised. Neodyme notes that an attacker with code execution on the server can take it and impersonate other hosts. Rotating it is a bigger job than patching, so scope it early.
The same November 3 releases also fix CVE-2026-115732, a critical certificate-name authorization bypass where a certificate with a name extending an approved name could impersonate a managed machine. Neodyme says both issues were found with AI assistance. One patch round covers both.
Priority call
If you run Puppet, this goes above routine patching. Servers that auto-sign certificates or are reachable from untrusted networks come first. Air-gapped, strictly controlled CAs come second, but they still need the update. Everything else on your patch list can wait a day.
Related: see the CVE-2026-115731 record and our CISA KEV hub.
- [ HIGH ]CVE-2026-115731Perforce Puppet Enterprise Deserialization of Untrusted Data Vulnerability
Found this useful? Share it.


