All CVEs

Puppet Server RCE (CVE-2026-115731): anyone with a signed agent cert can run code on Puppet Server (and reach the CA key). Public exploit, in CISA KEV (due 1 Dec). Upgrade to openvox-server 9.2.0 / 8.18.0, PE 2023.8.13 / 2025.12.1 / 2026.0.1, or Puppet Core 9.1.3 / 8.22.2 (Puppet Server 9.0.24.1 / 8.9.13). Until then: autosign = false. https://tldrcve.com/puppet/

Puppet / OpenVox · CVE-2026-115731

Puppet Server RCE

Patch nowPublic exploit. In CISA KEV, due 1 Dec.

Anyone with a signed Puppet agent certificate can send a crafted report and run code on your Puppet Server, which holds the key that signs every node's certificate. Any compromised agent is enough, and autosigning lets anyone who can reach the server get a certificate.

How scary is it?

updated 20 Nov
  • No: Needs a signed agent certificate first2,4
  • Yes: Public exploit code is out2
  • Yes: Attacks seen in the wild1
  • Yes: On CISA's exploited list (fix by 1 Dec)1

Scare-o-meter

Drop everything

Attackers are already on it.
Patch now.

Are you affected? only if all are true

1Server below a fixed releasecommand

OpenVox Server below 9.2.0 / 8.18.0, Puppet Enterprise before 2023.8.13 / 2025.12.1 / 2026.0.1, and Puppet Core before 9.1.3 / 8.22.2 (Puppet Server 9.0.24.1 / 8.9.13). OpenVox's advisory says up to 9.1.0 / 8.17.0, but 9.1.1 and 8.17.1 shipped before the fix, so count them as affected. Older open-source Puppet gets no fix, though Debian patched its puppet packages (bookworm 7.23.0-1+deb12u1, trixie 8.10.0-5+deb13u1). The command shows the Puppet Server version, not the Puppet Enterprise release.2,3,7,8,9,10,11,13,14

puppetserver --version
2Attacker can get a signed certcommand

Any existing agent's cert works. If autosign prints true, anyone who can reach the server can get one.2

puppet config print autosign --section server
3Report endpoint is reachable

PUT /puppet/v3/report on the server, which agents use normally.2

What to do

1Upgrade the server

OpenVox: server 9.2.0 / 8.18.0, agent 9.3.0 / 8.32.0, openvoxdb 9.2.0 / 8.18.0. Puppet Enterprise: 2023.8.13 / 2025.12.1 / 2026.0.1. Puppet Core: 9.1.3 or 8.22.2 (Puppet Server 9.0.24.1 or 8.9.13). Debian: install the patched packages. Other open-source Puppet: move to OpenVox, Puppet Core or Enterprise.2,3,7,8,10,11,13,14

Latest safe versions checked 20 Nov

OpenVox and Puppet → openvox-server 99.2.0openvox-server 88.18.0openvox agent 99.5.0openvox agent 88.34.0Puppet Core 99.1.4Puppet Core 88.22.3Puppet Enterprise 2026.02026.0.1Puppet Enterprise 2025.122025.12.1Puppet Enterprise 2023.82023.8.13openvoxdb: 9.2.0 / 8.18.0 or later. Debian: bookworm 7.23.0-1+deb12u1, trixie 8.10.0-5+deb13u1.
2Until then: turn off autosigncommand

Set autosign = false in the [server] section of puppet.conf, restart, and confirm with the command below. Also limit network access to the server.4,6

puppet config print autosign --section server
3Also covers CVE-2026-115732

The same releases fix a sibling bug where a cert for evil.target.example.com can act as target.example.com.5

This page shows you how to check. It can't tell you you're safe.

Sources (14) and changelog
  1. CISA KEV: added 17 Nov, due 1 Dec 17 Nov
  2. OpenVox GHSA-ffr6-rwpm-p5wq: versions, exploit 3 Nov
  3. Vox Pupuli: fixed versions
  4. Red Hat: CVE-2026-115731 / 115732
  5. oss-security: disclosure 3 Nov
  6. Puppet docs: disable autosigning
  7. CVE record (Perforce): Puppet Enterprise fixed versions
  8. Debian: patched puppet-agent (DLA-4884-1, DSA-6608-1)
  9. OpenVox Server 9.1.1: shipped 29 Oct, before the fix 29 Oct
  10. Puppet Core 9.1.3 release notes: fixes both CVEs
  11. Puppet Server release notes: 9.0.24.1 patched
  12. OpenVox: releases
  13. Puppet Core 8.22.2 release notes: fixes both CVEs
  14. Puppet Server 8 release notes: 8.9.13 patched