CISA added a Puppet Enterprise flaw to its Known Exploited Vulnerabilities catalog on November 17. A machine with any certificate signed by the Puppet certificate authority can send the server a crafted report and run code on it. CISA has not said who is exploiting it or how.
Get the CyberExperts Daily Brief: the day's top security news in 5 minutes. Free.
Puppet Server is the machine that tells every managed server what to install and how to be configured. Code running there reaches the whole fleet. Federal agencies have until December 1 to fix it, and the fix is a Puppet Enterprise upgrade plus a restart of the server.
Puppet Enterprise CVE-2026-115731 is now on CISA’s exploited list. One crafted report from a signed agent runs code on the Puppet Server. Upgrade to 2023.8.13, 2025.12.1 or 2026.0.1, then restart Puppet Server.
The 5-Minute Cyber BriefDon’t Miss the Policy Changes That Affect Security Decisions
Get the key CISA actions, new regulations, guidance, and risk shifts in a quick daily brief.
By subscribing you agree to our Privacy Policy.
Free. Weekday mornings. 5 minutes or less.
CISA says attackers are exploiting the Puppet Server report flaw
CVE-2026-115731 sits in the code that processes the reports agents send after each run. An agent sends its report with a PUT request to /puppet/v3/report. The server rebuilds the report’s objects from the data, and an attacker can name a type of their own that carries Ruby code. The server runs that code as its service user, according to the CVE record.
- Fixed in: Puppet Enterprise 2023.8.13, 2025.12.1 and 2026.0.1. The advisory says to restart Puppet Server after upgrading so the fixed code loads.
- Same release: CVE-2026-115732, a certificate-name flaw that lets one managed machine pose as another.
- OpenVox: the community fork is also affected. Fixed in OpenVox Server 9.2.0 and 8.18.0, and OpenVox Agent 9.3.0 and 8.32.0.
- CISA: added November 17, due December 1. Ransomware use is listed as unknown, and forensic triage is not required.
Who runs Puppet Enterprise and why autosigning matters
The flaw needs a certificate signed by the Puppet CA, which makes it sound like an insider problem. Neodyme, the firm that found it, says most large companies turn on autosigning, where the CA signs enrollment requests with no manual check or only a hostname pattern. In that setup anyone who can reach the server on port 8140 can ask for a certificate, get one, and send the report. The CVE record says the same.
Neodyme’s write-up shows the next step. Code running as the Puppet user can copy the CA signing key, and with that key an attacker can mint certificates that other hosts trust. Its proof of concept used the key to run commands on a managed machine through Puppet Enterprise’s orchestration broker. The bug also dates to 2021 code: Neodyme’s exploit worked on open-source Puppet 6.24.0.
Upgrade Puppet Enterprise, then restart Puppet Server
- Find every Puppet Enterprise server you run, including lab and disaster-recovery copies, and check its version against 2023.8.13, 2025.12.1 and 2026.0.1. Fixes exist for those three lines, so a server on another line needs an upgrade to one of them.
- After the upgrade, restart Puppet Server and confirm the restart happened. A package update with no restart leaves the old code running.
- Check whether autosigning is on. If it is, switch to manual approval or a check that proves who is enrolling, such as a one-time token from your provisioning tool.
- Until you have patched, limit who can reach Puppet Server’s port 8140 and the report endpoint to the networks your agents live on. Red Hat lists both of these as mitigations.
- Treat it as a patch-now item in your queue; our patch priority checklist shows how to rank it against the rest of the week.
Forward this
For whoever runs our server configuration tooling: attackers are now using a flaw in Puppet Enterprise, the software that pushes settings to our servers. If we use it, can someone confirm the server is upgraded to 2023.8.13, 2025.12.1 or 2026.0.1 and restarted, and check that new machines can’t sign themselves up automatically? If we don’t use Puppet, there is nothing to do.
Details
- CVE-2026-115731: deserialization of untrusted data in Puppet Server report processing (CWE-502, CWE-94). Published November 3, 2026. CVSS 4.0: 9.4 (Puppet/Perforce). CVSS 3.1: 9.9 (NVD, AV:N/AC:L/PR:L/UI:N/S:C).
- Affected: Puppet Enterprise releases that use puppet-agent before 8.22.2 or 9.1.3 (NVD). Fixed releases bundle those agents: PE 2023.8.13, 2025.12.1, 2026.0.1.
- CISA KEV: added 2026-11-17, due date 2026-12-01, ransomware use unknown, forensic triage not required.
- Public detail: the OpenVox advisory (GHSA-ffr6-rwpm-p5wq) and Neodyme’s write-up, both from November 3, include the crafted report and a working example.
- Exploitation: CONFIRMED by CISA’s KEV listing. CISA has not published who is exploiting it or how.
Hunt / verify
- List the certificates your CA has signed recently with
puppetserver ca list --alland look for names you didn’t enroll, especially from a time when autosigning was on. - In Puppet Server’s access logs, search for
PUT /puppet/v3/reportrequests from certnames you don’t recognize or from outside your agent networks. - On the server, look for shells, curl or wget started by the Puppet Server Java process, and for new files in the puppet user’s directories.
- If you find a hit, assume the CA key was copied. Rebuilding the CA is a large job, so plan it, and rotate any secrets that Puppet distributes.
Source: CISA KEV alert; Puppet Enterprise release
Sources
- CISA: Adds One Known Exploited Vulnerability to Catalog (November 17, 2026)
- CISA: Known Exploited Vulnerabilities Catalog
- Puppet: Updates and releases for Puppet Enterprise (security update)
- Perforce: CVE-2026-115731 Report Deserialization Code Execution
- NVD: CVE-2026-115731
- Puppet: PE 2023.8.13 release notes
- Puppet: puppet-agent 9.1.3 release notes
- Red Hat: CVE-2026-115731
- Neodyme: Pulling the right strings for RCE on a Puppet
- OpenVox advisory GHSA-ffr6-rwpm-p5wq
Start your morning with the signal that matters.
Get the biggest cybersecurity developments, why they matter, and where to go deeper on CyberExperts.
By subscribing you agree to our Privacy Policy.
Free. Weekdays. Built for operators.