How to tell if your Puppet server was hit: the CVE-2026-115731 flaw

Cybersecurity

Quick answer: On Nov 17, 2026, CISA added CVE-2026-115731 to its Known Exploited Vulnerabilities catalog. It is a flaw in how Puppet Enterprise and Puppet Core process agent reports. Any machine holding a certificate signed by the Puppet certificate authority (CA) can send a crafted report and run code on the Puppet Server. If your CA auto-signs certificate requests without strong checks, an outsider on your network can get such a certificate first. SecurityWeek rates it CVSS 9.4. The fix shipped Nov 3. CISA gave federal agencies until Dec 1 to patch. (CISA KEV entry; SecurityWeek, Nov 18)

Am I affected?

How to check

  1. Version: compare your Puppet Enterprise or Puppet Core version with the fixed releases above. Anything older is exposed. (Puppet)
  2. Auto-signing: find out whether your CA signs certificate requests automatically, and how it verifies them. SecurityWeek says Perforce advises turning auto-signing off and enforcing strong validation. (SecurityWeek, citing Perforce)
  3. Signs of compromise: CISA lists “Forensic triage required per BOD 26-04: No” for this entry, and none of the sources we read publish indicators to search logs for. Perforce warns a successful attack could expose the server’s certificate-signing key, so if you were unpatched and reachable, treat the server as suspect and review which certificates it has signed. (CISA; SecurityWeek, citing Perforce)

What to do

  1. Upgrade to one of the fixed releases listed above. The same releases fix a second critical flaw, CVE-2026-115732, a certificate-name bypass that let one managed machine pose as another. (Puppet)
  2. Turn off auto-signing and enforce strong validation of certificate requests, until you are patched and after. (SecurityWeek, citing Perforce)
  3. If you were exposed, Perforce says a successful attack could let an attacker issue trusted certificates and change software and configuration pushed to managed machines on their next Puppet run. Review recent changes your servers received. (SecurityWeek, citing Perforce)

What is still unknown

How many Puppet servers were hit. CISA lists whether it is used in ransomware campaigns as “Unknown.” SecurityWeek says exploitation was flagged on Nov 4; none of the sources give a count of victims.

FAQ

Was this patched already? Yes. Per SecurityWeek, the fix shipped Nov 3 together with the CVE-2026-115732 fix. CISA’s Nov 17 listing is about confirmed exploitation, not a new bug.

Does this only matter to US federal agencies? No. CISA’s Dec 1 deadline binds federal civilian agencies, but CISA encourages all organizations to prioritize catalog entries.

Which Puppet Core 8.x version fixes it? Puppet’s release page says 8.22.1. SecurityWeek writes 8.22.2. Use the vendor’s list and check Perforce’s advisory for your exact build.

Sources

AltTab Dad