
Top-Secured cyber watch: independent analysis based on the sources listed below. Top-Secured is not affiliated with the companies mentioned and will never ask you for your bank details or passwords.
CISA added CVE-2026-115731, a code execution flaw in Puppet Server’s report processing, to its catalogue of actively exploited vulnerabilities on 17 November. Any machine with a signed agent certificate can run code on the Puppet server, and certificate autosigning can make the attack possible without any credentials.
What happened
On 17 November 2026, the US agency CISA added CVE-2026-115731 to its Known Exploited Vulnerabilities catalogue, which means it has evidence of attacks in the wild. The flaw was disclosed by Perforce, the publisher of Puppet, on 3 November and is rated 9.4 out of 10 (CVSS 4.0). CISA gives no detail on the attacks or their authors; US federal agencies must fix it by 1 December.
Who is affected and how the attack works
Puppet agents send a report to the Puppet server after each run. The code that reads these reports trusts type information supplied by the client and can be made to build and run arbitrary Ruby code. Any client holding a certificate signed by the Puppet CA can therefore execute commands on the server as its service account. According to Perforce, if the CA signs requests automatically without strong checks, an attacker who can reach the server needs no prior access at all. The OpenVox project, the community fork of Puppet, adds that the service account can read the CA signing key, which opens the way to every managed machine.
Affected: Puppet Enterprise before 2023.8.13, 2025.x before 2025.12.1 and 2026.0.0. OpenVox is also affected: OpenVox Server before 8.18.0 and 9.2.0, and OpenVox Agent before 8.32.0 and 9.3.0.
What to do now
- Check the version:
cat /opt/puppetlabs/server/pe_version. - Upgrade to Puppet Enterprise 2023.8.13, 2025.12.1 or 2026.0.1, then restart the server (
systemctl restart pe-puppetserver) so the fixed code is loaded. On OpenVox, install Server 8.18.0 or 9.2.0 and Agent 8.32.0 or 9.3.0 on the server. - Review autosigning:
puppet config print autosign --section server. If it returnstrueor a broad wildcard list, switch to manual signing or policy-based autosigning with a shared secret. - Make sure port 8140 is reachable only from your managed machines, never from the Internet.
- List signed certificates (
puppetserver ca list --all) and revoke any unknown node. If you find signs of compromise, treat the CA as stolen: rebuild it and reissue every certificate.
Our take
A configuration management server controls every machine it manages: compromising it is like holding the root password of the whole fleet. It deserves the same care as a domain controller, with a short patch delay, a closed network perimeter and no autosigning left on by default.
Sources
- CISA — Known Exploited Vulnerabilities Catalog: CVE-2026-115731
- CVE Program — CVE-2026-115731 record published by Perforce (Report Deserialization Code Execution)
- OpenVox Project — GHSA-ffr6-rwpm-p5wq: Authenticated RCE on OpenVox server via Event Deserialization
How we choose, verify and write our analyses →
Is your own server exposed? Run a free check — public information only, no intrusion:
Worried your servers are exposed? Our team audits, patches and monitors Linux and cloud infrastructure 24/7.
Talk to an expert Our managed server services →

