CriticalCVE-2026-115731Remote AttackerSecurityWeek

Hackers Are Hijacking Puppet, the Server That Configures All the Others

Attackers are exploiting CVE-2026-115731, a deserialization bug that lets any client with a CA-signed agent certificate run code on a Puppet server. It's on CISA KEV with a Dec. 1 deadline.

Attackers are exploiting a critical bug in Puppet, the configuration-management platform many companies use to push software and settings to thousands of servers at once. SecurityWeek reports that CVE-2026-115731 was flagged as exploited on Nov. 4, a day after Perforce shipped the fix, and CISA added it to its Known Exploited Vulnerabilities catalog on Nov. 17. A compromised Puppet server is a bad day: it is the machine every managed system trusts for its next set of instructions.

For defenders

What’s broken: a deserialization flaw in Puppet’s report processing. Any client holding a certificate signed by the Puppet CA can submit a report with a crafted payload, and the server runs it as the Puppet service user. Perforce’s advisory warns that a successful attack can expose the server’s certificate-signing key, let the attacker mint trusted certificates and change what managed systems receive on their next Puppet run.

The catch that makes it pre-auth: if your CA auto-signs certificate requests without strong checks, an unauthenticated attacker can simply request a certificate first. Turn auto-signing off or put real validation in front of it.

CVE CVE-2026-115731 (CVSS 4.0 9.4), patched Nov. 3 alongside CVE-2026-115732, a certificate-name authorization bypass
Affected Puppet Enterprise and Puppet Core; the OpenVox fork is also affected
Fixed Puppet Enterprise / Enterprise Advanced 2026.0.1, 2025.12.1, 2023.8.13; Puppet Core 9.1.3 and 8.22.2
Exploitation KNOWN: on CISA KEV since Nov. 17, federal deadline Dec. 1. A public proof-of-concept targeting OpenVox is reported (one GitHub repository in our data). Who is behind the attacks has not been disclosed.

ATT&CK: T1190 (Exploit Public-Facing Application); abuse of the server to push changes to managed hosts would be T1072 (Software Deployment Tools). Because the signing key may be exposed, patching alone may not be enough on a server that was reachable before Nov. 3: review issued certificates and recent catalog changes too.

What it means for you

Puppet is back-office plumbing: you’ll only run it if you manage a fleet of servers. If your IT provider or hosting company does, this is worth a quick question, because whoever controls the Puppet server can quietly change every machine it manages. For everyone else, nothing to do.

Do this now

  1. Upgrade Puppet Enterprise or Puppet Core to one of the fixed versions above today; OpenVox users should apply their project’s fix.
  2. Turn off certificate auto-signing, or require strong verification before any request is signed.
  3. Check the list of signed agent certificates for names you don’t recognize, and revoke them.
  4. If the server was exposed before patching, review recent code and catalog changes and plan for rotating the CA if you find anything odd.

CVE at a glance

CVE-2026-115731CriticalKEVPublic exploitPerforce Puppet Enterprise
CVSS
9.4 Critical (v4.0)
EPSS
0.7% chance of exploitation in the next 30 days (higher than 53.7% of CVEs)
Exploited in the wild
Yes, on CISA’s KEV list since Nov 17, 2026
Public exploit
Yes, reported in 1 GitHub repository

Full CVE details

Data from NVD, FIRST EPSS and CISA KEV, refreshed automatically. We report whether public exploit code exists but never link to it: fake proof-of-concepts that infect researchers are common.

More from the Roundup