Are your Puppet Enterprise, Puppet Server or OpenVox installs exposed to CVE-2026-115731?
CISA added CVE-2026-115731 to its Known Exploited Vulnerabilities catalogue on 17 November 2026. The official CVE record, assigned by Perforce, describes a deserialization flaw in Puppet's report-processing code, as used by Puppet Server. A client that holds any CA-signed agent certificate can execute arbitrary code on the Puppet Server as its service user. Where the CA autosigns requests without strong verification, an unauthenticated attacker can obtain such a certificate first. Perforce, as the CNA, scores it CVSS 4.0 9.4 Critical. Upgrade Puppet Enterprise to 2026.0.1, 2025.12.1 or 2023.8.13, and restart Puppet Server. Official OpenVox release notes and the project's 3 November 2026 announcement give OpenVox Server 8.18.0 or 9.2.0, and OpenVox Agent 8.32.0 or 9.3.0.
Critical (CVSS 4.0 9.4). In CISA KEV, added 17 November 2026. Due 1 December 2026
CISA added CVE-2026-115731 to its Known Exploited Vulnerabilities catalogue on 17 November 2026 (catalogue 2026.11.17, released 17:53 GMT on 17 November 2026). The due date is 1 December 2026. Known ransomware campaign use is listed as Unknown. No public attack detail is given in the sources we cite, and we do not claim a public proof of concept. An earlier CISA ADP entry on the CVE.org record, dated 6 November 2026, still lists Exploitation as "none". We treat the 17 November KEV listing as the current official status. Recheck KEV. The first publication of the CVE was on 3 November 2026. We do not link proof-of-concept or exploit code.
By Simon Phillips, CTO. Reviewed by Oliver Legg, Head of SOC and IR. Last updated 18 November 2026, 18:09 GMT.
At a Glance
Based on the official CVE.org and NVD records for CVE-2026-115731, the CVE.org record for CVE-2026-115732, CISA KEV catalogue 2026.11.17, official Puppet Server release notes for the 9.x and 8.x lines, and official OpenVox notices, checked at 18:36 GMT and rechecked later on 17 November 2026. Last updated 18 November 2026, 18:09 GMT.
Critical, CVSS 4.0 9.4
Perforce, as the CNA, scores CVE-2026-115731 CVSS 4.0 9.4 Critical (CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:H/VI:H/VA:H/SC:H/SI:H/SA:H, CWE-502 and CWE-94). NVD's copy was in Awaiting Analysis when we checked at 18:36 GMT on 17 November 2026, and NVD has not published its own score. Companion CVE-2026-115732 is CVSS 4.0 9.0 Critical by the same CNA, also Awaiting Analysis on NVD.
In CISA KEV, added 17 November 2026
CISA added CVE-2026-115731 to KEV on 17 November 2026 (catalogue 2026.11.17, released 17:53 GMT on 17 November 2026). The due date is 1 December 2026. Ransomware use is listed as Unknown. Companion CVE-2026-115732 was not in KEV when we checked. An earlier CISA ADP entry on the CVE.org record, dated 6 November 2026, still lists Exploitation as "none". We treat the KEV listing as the current official status. Recheck KEV.
PE 2023.8, 2025 and 2026 lines, plus confirmed Core and OpenVox releases
The CVE record lists Puppet Enterprise 2023.8.0 to before 2023.8.13, 2025.0.0 to before 2025.12.1, and 2026.0.0 to before 2026.0.1. Official Puppet Server release notes also confirm patches in Puppet Server 9.0.24.1 (shipped with Puppet Core 9.1.3) and Puppet Server 8.9.13 (shipped with Puppet Core 8.22.2). OpenVox's own 3 November 2026 announcement and official release notes confirm that OpenVox Server 8.18.0 and 9.2.0, and OpenVox Agent 8.32.0 and 9.3.0, fix the same two flaws. OpenVox also states that all known Puppet implementations are affected, including unmigrated open-source Puppet. Perforce's CVE record does not list those older open-source releases, so that broader claim is unverified.
PE 2026.0.1, 2025.12.1 or 2023.8.13
The official CVE solution is to upgrade to a release that bundles puppet-agent 8.22.2 or 9.1.3 (Puppet Enterprise 2023.8.13, 2025.12.1 or 2026.0.1) and restart Puppet Server so the fixed code is loaded. The same PE releases, and the same Server 9.0.24.1 and 8.9.13 builds, also fix CVE-2026-115732. For open-source Puppet Core, the Server release notes give 9.1.3 and 8.22.2. OpenVox's official notices give OpenVox Server 8.18.0 or 9.2.0, and OpenVox Agent 8.32.0 or 9.3.0. The Server packages require the matching fixed agent and restart the service on install.
CVE-2026-115731 is published on CVE.org at 20:40 GMT and on NVD at 21:17 GMT, scored CVSS 4.0 9.4 Critical by Perforce as the CNA. NVD status is Awaiting Analysis. OpenVox published its announcement and release notes the same day.
Official Puppet Server release notes (last published this date) record patches for CVE-2026-115731 and CVE-2026-115732 in Server 9.0.24.1 (Puppet Core 9.1.3) and Server 8.9.13 (Puppet Core 8.22.2).
CISA adds CVE-2026-115731 to KEV catalogue 2026.11.17, released at 17:53 GMT on 17 November 2026. The due date is 1 December 2026. Ransomware use is listed as Unknown.
Upgrade to a fixed release and restart Puppet Server. Until you have patched, tighten autosign and keep port 8140 off untrusted networks, then hunt the patterns below.
What to Do in the Next 24 Hours
Proactive on the left. Reactive on the right. Vendor steps and our advice are labelled separately.
Upgrade and tighten access
- Vendor advice: upgrade Puppet Enterprise to 2023.8.13, 2025.12.1 or 2026.0.1 (a release that bundles puppet-agent 8.22.2 or 9.1.3) and restart Puppet Server so the fixed code is loaded.
- Vendor advice: for open-source Puppet Core or Puppet Server, upgrade to Puppet Core 9.1.3 (Server 9.0.24.1) or Puppet Core 8.22.2 (Server 8.9.13), as given in the official Server release notes, and restart the server.
- Vendor advice: for OpenVox, upgrade to OpenVox Server 8.18.0 or 9.2.0 and OpenVox Agent 8.32.0 or 9.3.0, as given in OpenVox's 3 November 2026 announcement and official release notes. The Server packages require the matching fixed agent and restart the service on install. If you cannot upgrade yet, OpenVox also advises limiting which networks can reach the server and disabling or tightening autosign, and checking any custom auth.conf rules after you upgrade.
- Our advice: inventory every Puppet Enterprise, Puppet Core or Puppet Server, and OpenVox Server or OpenVox Agent install you or your clients run.
- Our advice: until you have patched, disable autosign or use policy-based autosign with a pre-shared secret, and keep port 8140 restricted to known agent networks and off the internet.
Hunt and contain
- Our advice: the official records we cite do not publish indicators of compromise. The hunts below are our patterns, labelled OUR PATTERN, not vendor IOCs.
- Our advice: look for unrecognised signed certificates (
puppetserver ca list --all), report PUT requests to/puppet/v3/reportfrom unknown certnames, shells or curl/wget spawned by the puppetserver or pe-puppetserver JVM, new files or cron jobs owned by the puppet user, and unexpected code, environment or catalog changes. - Our advice: if you find a compromise, isolate the server, revoke rogue certificates, rebuild from a known-good baseline, rotate Hiera, eyaml and deploy keys, and check managed nodes for malicious catalog changes.
Proactive: Vendor Advice, Then Ours
Official vendor advice first. CybaVerse advice is labelled separately.
Upgrade Puppet Enterprise and restart the server
The official CVE record for CVE-2026-115731 tells users to upgrade to a release that bundles puppet-agent 8.22.2 or 9.1.3 (Puppet Enterprise 2023.8.13, 2025.12.1 or 2026.0.1) and restart Puppet Server so the fixed code is loaded. The same PE releases also fix CVE-2026-115732.
Upgrade open-source Puppet Core or Puppet Server
Official Puppet Server release notes say both CVEs are patched in Puppet Server 9.0.24.1, shipped with Puppet Core 9.1.3, and in Puppet Server 8.9.13, shipped with Puppet Core 8.22.2. A Puppet product page still lists Puppet Core 8.22.1 as a security update. The 8.x Server release notes, last published 9 November 2026, do not mention 8.22.1 and give 8.22.2. We use 8.22.2 from those notes. Restart the server after you upgrade.
Inventory every server, including ones clients run
Find every Puppet Enterprise, Puppet Core or Puppet Server, and OpenVox Server or OpenVox Agent install in your estate and in client environments. Treat an internet-facing server, or a CA that autosigns without strong checks, as urgent.
Until patched, tighten autosign and restrict port 8140
Until you have upgraded, disable autosign or use policy-based autosign with a pre-shared secret. Keep port 8140 restricted to known agent networks and off the internet. Puppet's product page notes that Puppet Server sends configuration to every machine it manages, so treat a compromised server as a threat to the managed estate.
Free Detection Pack
Built by the CybaVerse threat hunt team for businesses, internal IT teams and MSPs. Check exposure offline and hunt for signs of misuse. Everything is read-only. Pack version 1.0.0 is the download on this page. The KQL and Sigma have not been run against live data.
check-puppet.sh
Read-only offline checker, pack version 1.0.0. Unpack the full pack first, so scripts/ stays in place. It opens no sockets, writes no files and runs no other program except tr and wc. It reads only the files you name (and /opt/puppetlabs/puppet/VERSION when no version is given for Puppet Core or OpenVox Agent). It never reads keys, csr_attributes.yaml or policy executables, and never prints fingerprints or extensions. It flags a version inside a published affected range, naive or basic autosign, certificates outside your allowlist, and lookalike certnames (the CVE-2026-115732 pattern).
bash scripts/check-puppet.sh --flavour pe --version 2025.12.0 --puppet-conf /path/to/puppet.conf --ca-list /path/to/ca-list.txt --allowlist /path/to/allowlist.txt
bash scripts/check-puppet.sh --flavour openvox-server --version 9.1.0 --puppet-conf /path/to/puppet.conf --ca-list /path/to/ca-list.txt --allowlist /path/to/allowlist.txtCheck-Puppet.ps1
The same checks in PowerShell 7, with identical output and exit codes. Run it from the unpacked full pack. It is also read-only, opens no sockets and writes no files.
pwsh -File scripts/Check-Puppet.ps1 -Flavour pe -Version 2025.12.0 -PuppetConf /path/to/puppet.conf -CaList /path/to/ca-list.txt -Allowlist /path/to/allowlist.txt
pwsh -File scripts/Check-Puppet.ps1 -Flavour openvox-server -Version 9.1.0 -PuppetConf /path/to/puppet.conf -CaList /path/to/ca-list.txt -Allowlist /path/to/allowlist.txtKQL and Sigma
6 KQL hunts for Microsoft Sentinel and Defender, all OUR PATTERN, looking back from 3 November 2026 (our start date). Q1 inventories hosts listening on 8140. Q2 inventories Puppet, Puppet Enterprise and OpenVox packages. Q3 looks for PUTs to /puppet/v3/report (field availability unverified). Q4 looks for the server JVM starting a shell, curl or wget. Q5 looks for files or cron entries written by the puppet or pe-puppet user. Q6 looks for code, environment or CA changes. 6 Sigma rules, all OUR PATTERN, with Kusto conversions included. Neither Perforce, OpenVox nor CISA publishes indicators of compromise, so every hunt is OUR PATTERN, not a vendor IOC. The KQL and Sigma have not been run against live data. A hunt hit is a lead to investigate, not proof that code ran.
Verdicts
- OKVersion at or above a fixed release, and no autosign or certificate findings (exit 0).
- AFFECTEDVersion inside a range published by Perforce or OpenVox (exit 2).
- UNKNOWNNo version, or a version outside the published ranges, and no other findings (exit 3).
- REVIEWNot shown as affected, but naive or basic autosign is on, or certificates are outside your allowlist, including lookalike certnames (exit 4).
Exit codes
| Code | Meaning |
|---|---|
| 0 | OK |
| 1 | Not used |
| 2 | AFFECTED |
| 3 | UNKNOWN |
| 4 | REVIEW |
| 5 | Usage or read error |
The full pack zip contains 37 files (pack version 1.0.0). The checker never fetches anything and never prints file contents beyond version numbers, the autosign setting, autosign.conf glob entries and certnames.
Know the limits
- Both checkers are read-only and offline. They open no sockets, write no files and contain no exploit payloads. Use
--flavour pe,core,openvox-serveroropenvox-agent. - The official records we cite publish no indicators of compromise. Every hunt and Sigma rule in this pack is OUR PATTERN, not a vendor IOC.
- A hunt hit is a lead to investigate. It does not prove that code ran.
- The hunts look back from 3 November 2026. That start date is our choice.
- None of the KQL or Sigma has been run against live data. Q3 depends on whether your logs carry the request path and certname, which is unverified.
- Prefer the hand-written KQL. Some Sigma pipeline conversions fail, as the pack README explains.
What is in the pack
| File | What it does |
|---|---|
| scripts/check-puppet.sh | Offline version, autosign and certificate-list checker for Linux and macOS (bash) |
| scripts/Check-Puppet.ps1 | The same checker in PowerShell 7 |
| KQL (6 hunts) | Microsoft Sentinel and Defender hunts Q1 to Q6, all OUR PATTERN, from 3 November 2026 |
| Sigma (6 rules) | All OUR PATTERN, plus Kusto conversions |
| tests/ | Fixtures, bash and Pester tests and a sandboxed no-network run |
| README.md | Verified facts, vendor vs our advice, checker usage, limits and sources |
Reactive: How to Hunt (Our Advice)
The official records we cite do not publish indicators of compromise. The hunts below are CybaVerse advice, labelled OUR PATTERN, not vendor IOCs. CybaOps can run them across your estate. A hunt hit is a lead to investigate, not proof that code ran.
Unrecognised signed certificates
Review puppetserver ca list --all for signed certificates you do not recognise. This is our pattern, not a vendor IOC.
Report PUT requests from unknown certnames
Look for PUT requests to /puppet/v3/report from unknown certnames. This is our pattern, not a vendor IOC.
Shells or download tools from the server JVM
Look for the puppetserver or pe-puppetserver JVM spawning a shell, or curl or wget. This is our pattern, not a vendor IOC.
New files, cron jobs, or unexpected catalog changes
Look for new files or cron jobs owned by the puppet user, and for unexpected code, environment or catalog changes. If you find a compromise, isolate the server, revoke rogue certificates, rebuild from a known-good baseline, rotate Hiera, eyaml and deploy keys, and check managed nodes for malicious catalog changes.
Puppet Enterprise CVE-2026-115731 FAQ
Short answers based on the official CVE and NVD records, CISA KEV, Puppet Server release notes, and official OpenVox notices, rechecked later on 17 November 2026.
What is CVE-2026-115731?
The official CVE record, assigned by Perforce, describes deserialization of untrusted data in the report-processing code of Puppet, as used by Puppet Server. A client that holds any CA-signed agent certificate can execute arbitrary code on the Puppet Server as its service user by submitting a report containing a crafted rich-data type via a PUT request. Where the certificate authority autosigns requests without strong verification, an unauthenticated network attacker can obtain such a certificate. We do not describe the attack beyond that advisory wording, and we do not link proof-of-concept or exploit code.
How severe is it?
Perforce, as the CNA, scores CVE-2026-115731 CVSS 4.0 9.4 Critical, vector CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:H/VI:H/VA:H/SC:H/SI:H/SA:H, with CWE-502 and CWE-94. NVD's copy was in Awaiting Analysis status when we checked at 18:36 GMT on 17 November 2026, and NVD has not published its own score. Companion CVE-2026-115732, a certificate-name authorization bypass, is scored CVSS 4.0 9.0 Critical by the same CNA. NVD's copy of that record was also in Awaiting Analysis when we checked.
Is CVE-2026-115731 in CISA KEV, and has exploitation been reported?
Yes. CISA added CVE-2026-115731 to its Known Exploited Vulnerabilities catalogue on 17 November 2026 (catalogue 2026.11.17, released 17:53 GMT on 17 November 2026). The due date is 1 December 2026. Known ransomware campaign use is listed as Unknown. CISA's short description matches the official CVE record. No public attack detail is given in the sources we cite, and we do not claim a public proof of concept. Companion CVE-2026-115732 was not in KEV when we checked. An earlier CISA ADP entry on the CVE.org record for CVE-2026-115731, dated 6 November 2026, still lists Exploitation as "none". We treat the 17 November KEV listing as the current official status.
Which versions are affected, and what is the fix?
The official CVE record for CVE-2026-115731 lists Puppet Enterprise 2023.8.0 to before 2023.8.13, 2025.0.0 to before 2025.12.1, and 2026.0.0 to before 2026.0.1. The fixed PE releases are 2023.8.13, 2025.12.1 and 2026.0.1. The CVE solution also says to upgrade to a release that bundles puppet-agent 8.22.2 or 9.1.3, and to restart Puppet Server so the fixed code is loaded. Official Puppet Server release notes confirm the same two CVEs are patched in Puppet Server 9.0.24.1, shipped with Puppet Core 9.1.3, and in Puppet Server 8.9.13, shipped with Puppet Core 8.22.2. A Puppet product page still lists Puppet Core 8.22.1 as a security update; the 8.x Server release notes (last published 9 November 2026) do not mention 8.22.1 and give 8.22.2. We use 8.22.2 from those notes. OpenVox's 3 November 2026 announcement and official release notes confirm fixed versions of OpenVox Server 8.18.0 and 9.2.0, and OpenVox Agent 8.32.0 and 9.3.0, for the same two flaws. OpenVox also states that all known Puppet implementations are affected, including unmigrated open-source Puppet. Perforce's CVE record does not list those older open-source releases, so that broader claim is unverified.
What is CVE-2026-115732, and is it fixed in the same releases?
CVE-2026-115732 is a certificate-name authorization bypass in trapperkeeper-authorization, as used by Puppet Server. The official record says a client with a CA-signed certificate whose name extends or shortens an authorized hostname can be authorized as that host, which enables impersonation of other nodes and, in Puppet Enterprise, access to certificate-authority administration and remote command execution on managed nodes. The official CVE-2026-115732 record lists the same Puppet Enterprise fixed releases (2023.8.13, 2025.12.1 and 2026.0.1). Official Puppet Server release notes also say both CVEs were patched in the same Server releases (9.0.24.1 and 8.9.13). Puppet's product what's-new page says the same PE releases fix both vulnerabilities. OpenVox's official Server release notes say the same issue in Puppet Enterprise is CVE-2026-115732, and it is fixed in OpenVox Server 8.18.0 and 9.2.0. CVE-2026-115732 was not in CISA KEV when we checked. Its Perforce CNA score is CVSS 4.0 9.0 Critical, not 9.4.
What is the vendor's official advice?
Vendor advice: Perforce's official CVE record for CVE-2026-115731 tells users to upgrade to a release that bundles puppet-agent 8.22.2 or 9.1.3 (Puppet Enterprise 2023.8.13, 2025.12.1 or 2026.0.1) and restart Puppet Server so the fixed code is loaded. The CVE-2026-115732 record tells users to upgrade to those same PE releases. Official Puppet Server release notes give Puppet Core 9.1.3 (Server 9.0.24.1) and Puppet Core 8.22.2 (Server 8.9.13) as the open-source releases that include the patches. OpenVox's official announcement and release notes tell users to upgrade to OpenVox Server 8.18.0 or 9.2.0 and OpenVox Agent 8.32.0 or 9.3.0. The Server packages require the matching fixed agent and restart the service on install. If you cannot upgrade yet, OpenVox also advises limiting which networks can reach the server and disabling or tightening autosign, and checking any custom auth.conf rules after you upgrade.
What is CybaVerse's advice?
Our advice: inventory every Puppet Enterprise, Puppet Core or Puppet Server, and OpenVox Server or OpenVox Agent install you or your clients run, and upgrade to a fixed release. Until you have patched, disable autosign or use policy-based autosign with a pre-shared secret, and keep port 8140 restricted to known agent networks and off the internet. If you find signs of compromise, isolate the server, revoke rogue certificates, rebuild from a known-good baseline, rotate Hiera, eyaml and deploy keys, and check managed nodes for malicious catalog changes. The hunt patterns on this page are our patterns, not vendor indicators.
Who is this relevant to?
Organisations and MSPs that run Puppet Enterprise, Puppet Server or OpenVox, including servers that clients operate, especially any certificate authority that autosigns without strong checks, and any server whose port 8140 is reachable from untrusted networks.
Where do we get official updates?
Watch the Perforce advisory for CVE-2026-115731, the NVD record and CVE.org record, CISA KEV, and Puppet's Server release notes for the 9.x and 8.x lines. For OpenVox, watch the 3 November 2026 announcement, the official Server and agent release notes, and the project security advisories page. Recheck KEV.
Need help finding Puppet servers across the estates you manage?
CybaOps monitors your servers, endpoints and cloud workloads, whether that's your own business or your clients'. UK-based analysts monitor alerts 24/7, run these threat hunts and act on pre-approved response actions. The CybaOps Remediation Engine is live: it can fix security issues automatically, so gaps get closed rather than just reported. CybaRemediate, our remediation product line built on the Remediation Engine, is live. Book a CybaOps demo and see the Remediation Engine close a gap.
Sources
- Perforce advisory: Report Deserialization Code Execution (CVE-2026-115731). The public portal page is a sign-in shell; facts on this page come from the official CVE record that cites this URL, plus the other sources below.
- CVE.org: CVE-2026-115731 (CNA: Perforce; CVSS 4.0 9.4 Critical, CWE-502 and CWE-94; published 3 November 2026, 20:40 GMT)
- NVD: CVE-2026-115731 (CNA: Perforce / security@puppet.com; CVSS 4.0 9.4 Critical; published 3 November 2026, 21:17 GMT; status Awaiting Analysis when checked at 18:36 GMT on 17 November 2026)
- CISA Known Exploited Vulnerabilities catalogue 2026.11.17 (released 17:53 GMT on 17 November 2026; CVE-2026-115731 added 17 November 2026, due 1 December 2026, ransomware use Unknown)
- Puppet Server release notes, Puppet Core 9.x current (last published 9 November 2026): Server 9.0.24.1 shipped with Puppet Core 9.1.3, patched for CVE-2026-115731 and CVE-2026-115732
- Puppet Server release notes, Puppet Core 8.x (last published 9 November 2026): Server 8.9.13 shipped with Puppet Core 8.22.2, patched for both CVEs
- CVE.org: CVE-2026-115732 (CNA: Perforce; CVSS 4.0 9.0 Critical; same Puppet Enterprise fixed releases)
- Puppet Enterprise what's-new page: PE 2026.0.1, 2025.12.1 and 2023.8.13 fix both CVEs. This page still lists Puppet Core 8.22.1; we use 8.22.2 from the Server release notes.
- OpenVox announcement, 3 November 2026: Critical CVE Updates in all known versions of Puppet and OpenVox. Fixed versions: OpenVox Server 8.18.0 and 9.2.0, OpenVox Agent 8.32.0 and 9.3.0. The broader claim that all known Puppet implementations, including unmigrated open-source Puppet, are affected is unverified against the Perforce CVE record, which lists Puppet Enterprise only.
- OpenVox Server release notes, 9.x: Server 9.2.0 (3 November 2026) requires Agent 9.3.0, restarts the service, and records the same two flaws as CVE-2026-115731 and CVE-2026-115732
- OpenVox Server release notes, 8.x: Server 8.18.0 (3 November 2026) requires Agent 8.32.0, restarts the service, and records the same two flaws
- OpenVox Agent release notes, 9.x: Agent 9.3.0 (3 November 2026) fixes the report flaw, the same issue in Puppet Enterprise being CVE-2026-115731
- OpenVox Agent release notes, 8.x: Agent 8.32.0 (3 November 2026) fixes the same report flaw
- OpenVox project security advisories (3 November 2026 entries for the report deserialization and certname flaws). We cite this official index only, not individual technical-detail or proof-of-concept links.