Actively exploited CVSS 9.9 Security news
Exploited Puppet flaw CVE-2026-115731 lets any signed agent run code on Puppet Server
On Tuesday 17 November 2026 CISA added CVE-2026-115731, a flaw in Puppet Enterprise, to its Known Exploited Vulnerabilities catalog. A bug in how Puppet Server processes the reports that agents send lets anyone holding an agent certificate signed by the Puppet CA run their own code on the server. Where the server signs certificates automatically (autosign), an attacker with no credentials can get such a certificate. Fixes for Puppet Enterprise, Puppet and OpenVox were released in a coordinated disclosure on 3 November.
Key points
- Who is affected: organisations that manage servers and workstations with Puppet Enterprise, open-source Puppet or OpenVox, including Red Hat Satellite. Puppet Server is the central point that controls the configuration of hundreds or thousands of machines.
- The bug: when Puppet Server processes a node's report (PUT /puppet/v3/report), it takes object type information from the data and lets it reach code evaluation (CWE-502, CWE-94). The code runs as the Puppet Server service account.
- Precondition: an agent certificate signed by the Puppet CA. If the CA autosigns requests without strong verification, an attacker can request one without logging in.
- Exploitation: CISA added the flaw to KEV on 17 Nov 2026 without publishing attack details. Fixes have been available since 3 Nov 2026.
Vulnerabilities: CVE-2026-115731
What happened
On Tuesday 17 November 2026 CISA added CVE-2026-115731 to its Known Exploited Vulnerabilities (KEV) catalog and gave US federal agencies until 1 December to fix it. CISA did not publish details of the attacks, the attackers or the victims, and lists ransomware use as "unknown".
The flaw affects Puppet Server, the central component of the Puppet configuration management tool used to automate servers and workstations. Fixes were released in a coordinated disclosure on 3 November 2026: Perforce, which makes Puppet Enterprise, published an advisory and the CVE record, while the community OpenVox project (the open-source continuation of Puppet under Vox Pupuli) shipped fixed releases and posted an announcement to oss-security. The bug was reported by Alain of Neodyme. On 5 November Red Hat released fixes for Satellite 6.16, 6.17 and 6.19, which bundle Puppet.
Technical details
This is based on the NVD record, the OpenVox advisory and the CISA catalog. We do not publish exploitation steps.
- Component: Puppet's report-processing code as used by Puppet Server. After each run, agents submit a report to the
PUT /puppet/v3/reportendpoint. - Bug class: deserialization of untrusted data (CWE-502) leading to code injection (CWE-94). The server takes object type information ("rich data") from events in the report, and a crafted value reaches code evaluation.
- Preconditions: the attacker needs an agent certificate signed by the Puppet CA. If the CA autosigns requests without strong verification, an attacker can obtain one through the enrolment endpoint without authentication.
- Impact: the code runs as the Puppet Server service account (
puppet). According to the OpenVox advisory, an attacker may obtain the CA signing key and, in some orchestration setups, issue certificates that let them run commands on other hosts. - Scores: CVSS 3.1 9.9 from NIST (
AV:N/AC:L/PR:L/UI:N/S:C/C:H/I:H/A:H), CVSS 4.0 9.4 from Puppet.
The same releases also fix CVE-2026-115732 (CVSS 4.0 9.0, not in KEV): certificate name matching in trapperkeeper-authorization lets a node with a similar name impersonate another node.
Who is affected
| Product | Vulnerable versions | Fixed versions |
|---|---|---|
| Puppet Enterprise 2023.8 | 2023.8.0–2023.8.12 | 2023.8.13 |
| Puppet Enterprise 2025 | 2025.0.0–2025.12.0 | 2025.12.1 |
| Puppet Enterprise 2026 | 2026.0.0 | 2026.0.1 |
| Puppet (open source) 8 / 9 | 8.0.0–8.22.1, 9.0.0–9.1.2 | 8.22.2, 9.1.3 |
| OpenVox Server 8 / 9 | up to 8.17.0, up to 9.1.0 | 8.18.0, 9.2.0 |
| OpenVox Agent 8 / 9 | up to 8.31.1, up to 9.2.0 | 8.32.0, 9.3.0 |
| Red Hat Satellite 6.16, 6.17, 6.19 | before the 5 Nov 2026 errata | RHSA-2026:95655, 95656, 95652 |
Puppet and Puppet Enterprise versions are taken from the NVD records (we could not load the Perforce advisory), OpenVox versions from the project's advisory and the errata from Red Hat.
How to tell if you were compromised
Perforce, OpenVox and CISA have not published indicators of compromise. What we recommend checking (our own advice, not vendor guidance):
- Signed certificates:
puppetserver ca list --all– look for node names you don't recognise and certificates autosigned in recent weeks. - Autosign settings:
puppet config print autosign --section serverand the contents ofautosign.conf; a value oftrueor wildcards such as*mean anyone gets a certificate. - Puppet Server access log:
PUT /puppet/v3/report/...requests from unknown node names or unexpected IP addresses (/var/log/puppetlabs/puppetserver/puppetserver-access.log). - Processes and files owned by
puppet: unusual child processes (shells,curl,wget), new outbound connections, changes to the CA directory and to environment code.
Break down the CVSS vector in our CVSS calculator.
What to do
- Upgrade Puppet Server to a fixed version from the table and update the agents too. On Red Hat Satellite, install the 5 November 2026 errata.
- Disable or tighten autosigning so that only verified requests are signed (Vox Pupuli suggests a policy with verification, such as its autosign tool).
- Restrict network access to Puppet Server (port 8140) to the segments that host managed machines, and never expose it to the internet.
- If you cannot patch right away: OpenVox provides standalone patches in the
openvox-security-patchesrepository; the project warns they may not apply cleanly to old versions and may not remove all risk. - After patching, review certificates and logs as described above and check custom
auth.confrules (the CVE-2026-115732 fix changes how names are matched). If you suspect compromise, assume the CA key may be exposed.
Timeline
Updates
- 18 Nov 2026 – first version of this article.
FAQ
Why is a Puppet Server flaw so serious?
Puppet Server pushes configuration to every managed machine and runs the certificate authority that nodes trust. The OpenVox advisory warns that code execution on the server can expose the CA signing key, and in some orchestration setups an attacker could then issue certificates and run commands on other hosts. Compromising the server can mean compromising the whole managed estate.
Autosigning is off. Am I safe?
Not entirely. Without autosign an attacker has to obtain a valid certificate some other way, for example from any managed machine they have already compromised, since every node holds its own certificate. The risk is lower, but you still need the fix.
I use open-source Puppet, not Enterprise. Does this affect me?
Yes. NVD lists open-source Puppet 8.0.0 to 8.22.1 and 9.0.0 to 9.1.2 as vulnerable. Vox Pupuli notes that open-source Puppet no longer receives community security updates and recommends moving to OpenVox (fixed server versions 8.18.0 and 9.2.0).
Have indicators of compromise been published?
Not as of 18 Nov 2026. CISA, Perforce and the OpenVox project have not published indicators of compromise. The checks in the section How to tell if you were compromised are our own recommendations, not vendor guidance.
Sources
- NVD – CVE-2026-115731 (CVSS 3.1 9.9 by NIST, CVSS 4.0 9.4 by Puppet, affected versions, KEV)
- CISA – Known Exploited Vulnerabilities Catalog, CVE-2026-115731 (added 17 Nov 2026)
- Perforce – Report Deserialization Code Execution (vendor advisory)
- OpenVox – GHSA-ffr6-rwpm-p5wq: Authenticated RCE on OpenVox Server via Event Deserialization (3 Nov 2026)
- Vox Pupuli – Critical CVE updates (3 Nov 2026)
- oss-security – OpenVox security announcement (Ben Ford, 3 Nov 2026)
- Red Hat – CVE-2026-115731 (Satellite 6, errata 5 Nov 2026)
Spotted a mistake? Let us know and we will correct it openly.