Puppet Server Flaw CVE-2026-115731 Is Being Exploited: Who Is Affected and How to Patch
CISA says critical Puppet flaw CVE-2026-115731 (CVSS 9.4) is being exploited. Affected Puppet and OpenVox versions, fixes, and interim mitigations.
Table of contents
A critical remote code execution flaw in Puppet's server-side report processing is now being exploited in the wild. The U.S. Cybersecurity and Infrastructure Security Agency (CISA) added CVE-2026-115731 to its Known Exploited Vulnerabilities (KEV) catalog on November 17, 2026. Fixes have been available since November 3.
If your organisation uses Puppet Enterprise, Puppet Core (open source Puppet) or OpenVox for configuration management, treat this as an urgent patch. Here is what is confirmed, what versions are affected, and what to do.
What happened
- November 3, 2026: Perforce (Puppet's owner) and the Vox Pupuli community behind the OpenVox fork shipped fixes for a set of critical vulnerabilities, including CVE-2026-115731 and a related certificate-name authorization bypass, CVE-2026-115732.
- Early November: according to reporting by The Hacker News, community members reported exploitation shortly after public disclosure.
- November 17, 2026: CISA added CVE-2026-115731 to the KEV catalog, citing evidence of active exploitation. U.S. federal civilian agencies must apply fixes by December 1, 2026 under Binding Operational Directive 26-04.
CISA and the vendor have not published details of who is being targeted or how. What follows is based on the vendor and project advisories.
The vulnerability in plain terms
Puppet agents regularly send reports back to the Puppet Server describing what changed on each managed machine. CVE-2026-115731 is a deserialization of untrusted data bug in the code that processes those reports. A specially crafted report can cause the server to execute attacker-supplied code, running as the Puppet Server's service user. The flaw is rated CVSS 9.4.
The OpenVox project's advisory notice describes the same class of issue: a malicious serialized Ruby object placed in a report's event data can execute code when the report is deserialized on the server.
Why the "needs a certificate" caveat is weaker than it sounds
Exploitation requires a client certificate signed by the Puppet certificate authority (CA) — normally something only legitimate agents have. That sounds like a strong precondition, but it depends entirely on how your CA signs certificates:
- If any compromised managed node can talk to the server, the attacker already has a valid certificate.
- If your CA uses autosigning without strong verification, an attacker who can reach the server over the network may be able to request and receive a valid certificate, then exploit the flaw.
The consequence of a compromised Puppet Server is severe. Puppet servers push configuration to every managed machine and hold the CA's signing keys. Researchers who reported the flaws warn that an attacker with code execution on a Puppet server can obtain those keys and impersonate other hosts.
Affected and fixed versions
Based on the vendor advisories as summarised in public reporting:
| Product | Affected | Fixed in |
|---|---|---|
| Puppet Enterprise 2026.x | 2026.0.0 | 2026.0.1 (Puppet Core 9.1.3) |
| Puppet Enterprise 2025.x | 2025.0.0 to before 2025.12.1 | 2025.12.1 (Puppet Core 8.22.2) |
| Puppet Enterprise 2023.8 LTS | 2023.8.0 to before 2023.8.13 | 2023.8.13 (Puppet Core 8.22.2) |
| Puppet Core 9.x | 9.0.0 to before 9.1.3 | 9.1.3 |
| Puppet Core 8.x | before 8.22.2 | 8.22.2 |
| OpenVox Server | earlier 8.x / 9.x | 8.18.0 / 9.2.0 |
| OpenVox Agent | earlier 8.x / 9.x | 8.32.0 / 9.3.0 |
| OpenVoxDB | earlier 8.x / 9.x | 8.18.0 / 9.2.0 |
Always confirm against the Perforce advisory for your exact release line before upgrading.
What to do now
1. Find every Puppet server you run
Include primary servers, compile servers, replicas and any forgotten test instances. On each, check the installed version:
# Puppet Enterprise / Puppet Core
puppetserver --version
puppet --version
# OpenVox (Debian/Ubuntu)
dpkg -l | grep -E 'openvox|puppetserver'
# OpenVox (RHEL family)
rpm -qa | grep -E 'openvox|puppetserver'
2. Upgrade to a fixed release
Upgrade servers first, then agents, using your normal package or Puppet Enterprise installer process. For OpenVox, the project's instruction is to upgrade through your system package manager to the versions in the table above (or later); the OpenVoxDB container should use tag 8.18.0 or later.
After upgrading, the OpenVox project advises validating any custom authorization rules (for example in auth.conf), because some configurations may have depended on the buggy certificate-name matching fixed alongside this flaw.
3. If you cannot patch today, reduce exposure
The OpenVox advisory lists interim mitigations for the server-side flaws, which require network access and a valid signed certificate:
- Restrict network reachability of Puppet servers to only the subnets that need it. A Puppet Server should never be reachable from the internet.
- Disable or tighten autosigning. Use policy-based autosigning that verifies a pre-shared secret or cloud instance identity rather than accepting every request.
- Review recently signed certificates and revoke any you cannot account for:
puppetserver ca list --all
puppetserver ca revoke --certname <unexpected-host>
These steps reduce risk; they do not remove the vulnerability.
4. Look for signs of compromise
Because exploitation has been confirmed, patching alone is not enough if a server was exposed. Review:
- Unexpected certificate signing requests or newly signed certificates.
- Unusual processes spawned by the Puppet Server service user.
- Unexpected changes to Puppet code, Hiera data or the CA directory.
- Outbound connections from the Puppet Server to unfamiliar hosts.
If you find evidence of compromise, assume the CA keys may be exposed. Rebuilding the CA and re-issuing agent certificates is disruptive but may be necessary; follow your incident response process.
A note on open source Puppet
The Vox Pupuli advisory states that open source Puppet will receive no further updates from the community project and recommends migrating to OpenVox. Perforce continues to ship Puppet Core and Puppet Enterprise. If you run unmaintained open source Puppet builds, this incident is a good prompt to decide on a supported path.
The bigger lesson: configuration management is tier-zero infrastructure
Systems that can push changes to every server — Puppet, Ansible controllers, Chef servers, CI/CD runners — deserve the same protection as domain controllers. Keep them off broad networks, patch them first, and monitor them closely. Strong authentication matters too: our explainer on phishing-resistant passkeys covers one way to protect the admin accounts that manage this infrastructure, and our SSH key guide explains how to set up key-based access properly.
We will update this article if CISA or Perforce publish further detail about the attacks.
Frequently asked questions
+Is CVE-2026-115731 being exploited?
Yes. CISA added it to its Known Exploited Vulnerabilities catalog on November 17, 2026, based on evidence of active exploitation. Public details of the attacks have not been released.
+Can an unauthenticated attacker exploit the Puppet flaw?
Exploitation requires a certificate signed by the Puppet certificate authority. However, if your CA signs certificate requests automatically without strong verification (for example, naive autosigning), an attacker on the network may be able to obtain a valid certificate and then exploit the flaw.
+Which version fixes CVE-2026-115731?
Puppet Enterprise 2026.0.1, 2025.12.1 and 2023.8.13; Puppet Core 9.1.3 and 8.22.2; OpenVox Server 9.2.0 and 8.18.0 with OpenVox Agent 9.3.0 and 8.32.0.
+What should I do if I can't patch immediately?
Restrict network access to Puppet servers to the segments that need it, disable or tighten certificate autosigning, and review signed certificates. These reduce risk but are not a substitute for upgrading.
Sources & references
- CISA — CISA Adds One Known Exploited Vulnerability to Catalog (Nov 17, 2026)
- Perforce — CVE-2026-115731 advisory: report deserialization code execution
- Perforce — CVE-2026-115732 advisory: certificate-name authorization bypass
- Vox Pupuli — Critical CVE updates for OpenVox (Nov 3, 2026)
- OpenVox security advisory GHSA-ffr6-rwpm-p5wq
- The Hacker News — Hackers Exploiting Critical Puppet RCE Flaw (Nov 18, 2026)
Spotted an error? See our Corrections Policy.
- #puppet
- #openvox
- #cve
- #vulnerability
- #devops
- #cisa-kev
The KernelBrief editorial desk researches, writes and fact-checks every article published on this site. Every article is checked against primary sources (official documentation, vendor announcements, standards bodies and original research) before publication. Every factual claim is linked to its source, and corrections are handled under our published Corrections Policy.
Related articles
VMware vCenter Zero-Day CVE-2026-123890 Was Exploited for Months: Who Is Affected and How to Patch
VMSA-2026-0009 fixes vCenter auth bypass CVE-2026-123890, exploited since September per Mandiant. Fixed builds, no workaround, and what to check.
· 6 min read
LiteLLM Flaw CVE-2026-40217 Is Being Exploited in LLMjacking Attacks: Who Is Affected and How to Patch
CISA added LiteLLM flaw CVE-2026-40217 to its exploited list. Affected versions, why it matters for LLMjacking, and how to patch and rotate keys.
· 7 min read
F5 BIG-IP Buffer Overflow Flaws: Six Critical CVEs, Who Is Affected and How to Patch
F5 disclosed six critical BIG-IP stack buffer overflows (CVSS 9.8) that crash TMM without login. Affected versions, risky configs and hotfixes.
· 4 min read