For: infrastructure and operations teams that run Puppet Enterprise (PE) or Puppet Server. This article is based on the CVE record, CISA KEV and press reports; it does not cover attack steps.
続報待ち:この記事は公式発表に合わせて更新します
- Who is affected
infrastructure and operations teams that run Puppet Enterprise (PE) or Puppet Server.
- Confirmed so farSee the table ↓
- The flaw
- Affected and fixed versions
- Exploitation
- Not yet confirmed
- How the attacks work and how far they reached (CISA KEV and SSVC indicate exploitation; no detail in official sources)
- The full text of the Perforce advisory (the page did not render for us; checked against the CVE record and NVD)
- Treatment of products other than PE, such as Puppet Core (press reports name fixed versions; not confirmed against the advisory text)
- What to do nowSee the steps ↓
- Check your Puppet Enterprise version
- Update to a fixed release and restart puppet server
- Review CA autosigning
1 more
- Look for unfamiliar certificates and odd reports
- Where to verify (source)All sources ↓
- Perforce
- Last checked
- as of November 19, 2026
Follow-up plans and what we checked
CISA added the flaw to KEV on November 17 and its SSVC entry for the same day lists Exploitation as active. Who is attacking, how many victims, and how, are not in official sources, so this site does not state them.
What to do today
Check your Puppet Enterprise version
Look up the PE version in the console or on the server. Affected: 2023.8.0 up to but not including 2023.8.13, 2025.0.0 up to but not including 2025.12.1, 2026.0.0 up to but not including 2026.0.1. If you run several lines, list every primary server and compiler (asset inventory checklist).
Update to a fixed release and restart puppet server
Perforce's stated solution is to upgrade to a release that bundles puppet-agent 8.22.2 or 9.1.3 (PE 2023.8.13, 2025.12.1 or 2026.0.1) and restart puppet server. An update without a restart leaves the old code running. The KEV due date is 1 December.
Review CA autosigning
The CVE record says that where the CA autosigns without strong verification, an unauthenticated network attacker can obtain a certificate. Check the autosign setting in puppet.conf; if it signs everything, switch it off and use verification such as pre-shared keys. The Perforce advisory as quoted in press reports also lists disabling autosigning and strong verification before issuing certificates.
Look for unfamiliar certificates and odd reports
Review the signed certificate list for node names you do not recognize. Also check Puppet Server logs, child processes of the service user and unexpected configuration changes. If anything looks wrong, inspect the CA key and the configuration the server distributes, and assess the managed nodes (how to check for intrusion).
What kind of flaw this is
- CVE
- CVE-2026-115731 (code execution in Puppet report processing)
- Severity
- CVSS v4.0 9.4 (critical; AV:N/AC:L/AT:N/PR:L/UI:N; assigned by Perforce). NVD scores CVSS v3.1 at 9.9
- Type
- Deserialization of untrusted data (CWE-502), code injection (CWE-94)
- Impact
- A client with a CA-signed agent certificate can run arbitrary code on Puppet Server as its service user
- Affected
- Puppet Enterprise 2023.8.0 to before 2023.8.13, 2025.0.0 to before 2025.12.1, 2026.0.0 to before 2026.0.1
- Fix
- PE 2023.8.13 / 2025.12.1 / 2026.0.1 (bundling puppet-agent 8.22.2 or 9.1.3). Restart puppet server afterwards
- Published
- CVE published November 3, 2026 (last updated November 18)
- Exploitation
- Added to CISA KEV November 17 (due December 1). Ransomware use Unknown, Forensic Triage No
- In short: Puppet Server processes reports sent by agents. While restoring the received data it does not safely handle a crafted type, so code runs on the server. Neither the official sources nor this site give the request details (the pattern is described in insecure deserialization).
- The starting point is the side that holds a certificate, so environments with loose certificate issuance have the weakest footing.
What is known and what is not
| Item | Content | Status |
|---|---|---|
| The flaw | Code execution through a deserialization defect in report processing (CVE record, NVD) | Confirmed (Perforce) |
| Affected and fixed versions | As above; restart required | Confirmed (Perforce) |
| Exploitation | Added to KEV; SSVC: exploitation active, automatable no, technical impact total | Exploitation confirmed (CISA) |
| Attack method and victims | Not in official sources | Not stated |
| Impact on non-PE products (such as OpenVox) | Mentioned in press; not confirmed by us against the advisory text | Under investigation |
Sources
- Perforce — Report Deserialization Code Execution (vendor advisory; the body did not render for us, so we cross-checked the same content in the CVE record)
- CVE.org — CVE-2026-115731 (published November 3, 2026; affected and fixed versions, solution)
- NVD — CVE-2026-115731
- CISA KEV — Known Exploited Vulnerabilities Catalog (added November 17, due December 1)
- SecurityWeek — Critical Perforce Puppet RCE Exploited in Attacks (press; quotes the advisory's mitigation and fixed versions; cross-checked with primary sources)
No attack steps are included. Last verified: November 19, 2026.
Update history
2026-11-19: First report. Based on the CVE record, NVD and CISA KEV; the fact that the vendor advisory body could not be retrieved is listed as unconfirmed.
Read next
- The pattern: What insecure deserialization is
- Practice: Vulnerability remediation playbook / Asset inventory checklist
- Prioritizing: Deciding fix order with CVSS, EPSS and KEV
- Term: What RCE (remote code execution) is