CISA added a Puppet Server bug to its Known Exploited Vulnerabilities catalog yesterday, November 17. Federal agencies have until December 1. Everyone else should move faster than that, because of what a Puppet server is: the thing that tells every other server what to be.
What We Know
- The bug: CVE-2026-115731, unsafe deserialization in how Puppet Server processes the report an agent sends after each run. A client with a CA-signed agent certificate can send a crafted report and run code as the Puppet service user.
- Severity: CVSS 3.1 of 9.9 per NVD and Red Hat. Red Hat rates it Critical.
- The autosign problem: if your CA autosigns new machines, an attacker can get a certificate first and then exploit the bug. No password needed.
- Affected and fixed: Puppet Enterprise 2023.8 before 2023.8.13, 2025 before 2025.12.1, and 2026.0.0 (fixed in 2026.0.1). OpenVox Server 8.18.0 and 9.2.0 fix it, with openvox-agent 8.32.0 or 9.3.0 on the server. For open-source Puppet, reports disagree on fix availability, so check with your distribution.
- Timeline: Perforce, OpenVox and Neodyme (whose researcher reported it) disclosed on November 3. The OpenVox advisory included a working proof-of-concept report that runs a shell command. Fourteen days later, it's on KEV.
- What we don't know: who's exploiting it or against whom. CISA hasn't said, and no indicators have been published.
Credit where it's due: Neodyme reported it, and Perforce and the OpenVox maintainers coordinated fixes and disclosure on the same day. That's the system working. The two weeks since are the part on us.
Why This One Matters
The code runs as the puppet user, not root. That sounds reassuring until you remember what the Puppet server holds: the CA signing key and the configuration it pushes to every managed node. Own the server and you can, in principle, sign your own certificates and change what your fleet runs. It's a supply chain attack on your own infrastructure.
Same theme as a lot of this month's posts: management planes are targets because they're trusted by everything downstream.
What To Do
- Patch the primary server first, then compilers and replicas.
- Check autosign:
puppet config print autosign --section server. If it saystrue, fix that today. Use policy-based signing with real verification. - Restrict who can reach the server, especially the report endpoint (
PUT /puppet/v3/report). Only managed nodes should be able to talk to it. - Review custom
auth.confrules after upgrading. - Hunt: unexpected signed certificates (
puppetserver ca list --all), the Puppet Server Java process spawning shells, and odd activity by thepuppetuser. - If you find compromise, assume the CA key is gone. Rebuild the CA, reissue agent certificates and rotate secrets. Patching while keeping the old CA leaves the attacker a way back in.
Bottom Line
A public PoC on November 3 and KEV on November 17 is the modern timeline. If your Puppet server is still on an old build with autosign on, treat it as a priority incident, not a ticket.
Sources: Cybersecurity News, Red Hat, Ciphers Security, SecurityOnline, HOL, CISA KEV alert