# Puppet report deserialization (CVE-2026-115731) and certname authorization bypass (CVE-2026-115732): detection pack

Pack 1.0.0, 17 Nov 2026. CybaVerse threat hunt.

A client that holds any CA-signed agent certificate can PUT a crafted report to Puppet Server and run code on the
server as its service user. Where the certificate authority autosigns requests without strong verification, an
unauthenticated network attacker can get such a certificate first. Perforce (the CNA) scores it **CVSS 4.0 9.4
Critical**. CISA added it to the Known Exploited Vulnerabilities (KEV) catalogue on 17 Nov 2026.

Patch now regardless of KEV status. The KQL in this pack has NOT been run against a live tenant. Neither Perforce,
OpenVox nor CISA publishes indicators of compromise, so every hunt and rule here is OUR PATTERN. Research is credited
to security researchers only.

## Verified facts

| Item | Value | Source |
| --- | --- | --- |
| CVE-2026-115731 | Report Deserialization Code Execution; CWE-502, CWE-94 | CVE record (Perforce CNA), Perforce advisory |
| Severity | **CVSS 4.0 9.4 Critical** (Perforce CNA), `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` | CVE record, Perforce advisory |
| Published | 3 Nov 2026, 20:40 UTC (CVE record); NVD published 3 Nov 2026, 21:17 UTC | cve.org, NVD |
| NVD status | CVE-2026-115731: Awaiting Analysis; CVE-2026-115732: Awaiting Analysis (CNA scores only, no NVD score) | NVD |
| KEV | Added 17 Nov 2026 (catalogue 2026.11.17, released 17:53 UTC); due 1 Dec 2026; known ransomware use: Unknown | CISA KEV |
| KEV due date | Applies to US federal agencies only, under BOD 26-04 | CISA KEV |
| CISA ADP on the CVE record | SSVC Exploitation "none", dated 6 Nov 2026, before the KEV listing | CVE record |
| Companion CVE-2026-115732 | Certificate Name Authorization Bypass; CWE-863, CWE-697; **CVSS 4.0 9.0 Critical** (Perforce CNA); not in KEV | CVE record, Perforce advisory |
| Fix for both | The same releases: Puppet Enterprise 2023.8.13, 2025.12.1, 2026.0.1; Puppet Core 8.22.2, 9.1.3 | Perforce advisories for both CVEs |

Perforce's fix statement (CVE record, solution): "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."

### Affected and fixed versions (published ranges only)

| Product | Affected | Fixed in | Source |
| --- | --- | --- | --- |
| Puppet Enterprise 2023.8 | 2023.8.0 before 2023.8.13 | 2023.8.13 (bundles Puppet Core 8.22.2) | CVE record, Perforce advisory |
| Puppet Enterprise 2025 | 2025.0.0 before 2025.12.1 | 2025.12.1 (bundles Puppet Core 8.22.2) | CVE record, Perforce advisory |
| Puppet Enterprise 2026 | 2026.0.0 before 2026.0.1 | 2026.0.1 (bundles Puppet Core 9.1.3) | CVE record, Perforce advisory |
| Puppet Core 8 | 8.x before 8.22.2 | 8.22.2 (Puppet Server 8.9.13) | Perforce advisory, Puppet Server release notes |
| Puppet Core 9 | 9.0.0 before 9.1.3 | 9.1.3 (Puppet Server 9.0.24.1) | Perforce advisory, Puppet Server release notes |
| OpenVox Server | 8.17.0 and earlier; 9.1.0 and earlier | 8.18.0; 9.2.0 | OpenVox announcement and release notes |
| OpenVox Agent (openvox gem the server runs) | 8.31.1 and earlier; 9.2.0 and earlier | 8.32.0; 9.3.0 | OpenVox announcement and release notes |

The CVE record lists Puppet Enterprise only and sets the default status to affected, so Puppet Enterprise versions
outside the listed ranges are not shown as safe. The Perforce advisory adds the two Puppet Core lines. OpenVox, the
community fork, published its own advisories on 3 Nov 2026 (GHSA-ffr6-rwpm-p5wq for the report flaw, rated CVSS 4.0
9.4; GHSA-q4hm-33rc-572g for the certname flaw, rated 9.5) and states that the same issues in Puppet Enterprise are
CVE-2026-115731 and CVE-2026-115732. OpenVox Server 8.18.0 and 9.2.0 require the fixed agent and restart the
service on install; OpenVox says agent-only hosts are not exposed by the report flaw. Puppet Server versions 8.9.12
and 9.0.18 to 9.0.24 were never released (Puppet Server release notes).

### What CVE-2026-115732 adds

Perforce: certificate-name matching "allows a client that holds a CA-signed certificate whose name extends or
shortens an authorized hostname to be authorized as that host", enabling impersonation of other nodes and, in Puppet
Enterprise, CA administration and remote command execution on managed nodes. Exploitation needs a certificate with a
colliding name, issued by approval or autosign. OpenVox: after upgrading, check custom `auth.conf` rules, because a
rule that relied on the old partial match now rejects names it used to accept. The checker flags certnames that
extend or shorten an allowlisted name.

### Timeline (UTC)

| When | Event |
| --- | --- |
| 3 Nov 2026, 20:38 and 20:40 | CVE-2026-115732 and CVE-2026-115731 published by Perforce; OpenVox advisories and announcement the same day |
| 3 Nov 2026, 21:17 | NVD publishes both (Awaiting Analysis) |
| 6 Nov 2026 | CISA ADP adds SSVC to the CVE record (Exploitation: none) |
| 9 Nov 2026 | Puppet Core 8.22.2 and 9.1.3 release notes last published |
| 17 Nov 2026, 17:53 | CISA KEV catalogue 2026.11.17 adds CVE-2026-115731; due 1 Dec 2026 |

## Corrections to the flag we were given

1. Puppet Core 8 fix is **8.22.2**, not 8.22.1. The Perforce advisory, the CVE record's fix statement and the Puppet
   Server release notes (Puppet Server 8.9.13 "shipped with Puppet Core 8.22.2") all say 8.22.2. Puppet's Puppet
   Enterprise what's new page still headed the update "Puppet Core 9.1.3 & 8.22.1" when we checked on 17 Nov 2026.
   We follow the advisory and release notes and treat 8.22.1 as affected.
2. Puppet Core 9.1.3 is confirmed (Puppet Server 9.0.24.1).
3. OpenVox fixed versions are confirmed from OpenVox's own announcement and release notes: OpenVox Server 8.18.0 and
   9.2.0 (as flagged) and OpenVox Agent 8.32.0 and 9.3.0 (not in the flag).
4. CVE-2026-115732 is confirmed fixed by the same releases (Perforce advisory and CVE record). Its CNA score is CVSS
   4.0 9.0 Critical, lower than CVE-2026-115731's 9.4, and it is not in KEV.
5. Published 3 Nov 2026 at 20:40 UTC per the CVE record.
6. KEV facts confirmed against catalogue 2026.11.17: added 17 Nov, due 1 Dec 2026, BOD 26-04, ransomware Unknown.
   CISA's own ADP entry on the CVE record still says Exploitation "none" (6 Nov), which predates the listing.
7. Public technical detail of the report flaw exists in OpenVox's advisory. We do not link or reproduce it, and we
   make no claim about attack tooling. No source describes the attacks behind the KEV listing.

## Unverified items

* [UNVERIFIED] Open source Puppet (the community releases before Puppet Core): OpenVox states "All known Puppet
  implementations are vulnerable" and that open source Puppet gets no more updates. Perforce does not list those
  releases, so they stay out of the table. OUR ADVICE: treat them as affected and move to Puppet Core or OpenVox.
* [UNVERIFIED] Puppet Enterprise and Puppet Core file paths, jar name, service user name (`pe-puppet` is documented
  by OpenVox as the Puppet Enterprise default) and log lines. The names used in the hunts come from OpenVox
  documentation and source.
* [UNVERIFIED] Whether your proxies, load balancers or Syslog collection carry the request path and certname (Q3).
* OUR ASSUMPTION: the server JVM has no routine reason to start shells, curl or wget, or to write cron files.

## Advice

**Vendor advice (credited to Perforce and OpenVox):** upgrade to a fixed release above and restart the Puppet or
OpenVox server so the fixed code is loaded. Upgrade primary servers and compilers first (OpenVox). If you cannot
upgrade yet, OpenVox advises limiting which networks can reach the server and disabling or tightening autosign;
OpenVox's autosign documentation says of naive autosigning (`autosign = true`) "Never do this in a production
deployment", and calls basic `autosign.conf` allowlists "essentially insecure" because any host can provide any
certname.

**OUR ADVICE (CybaVerse, not from Perforce or OpenVox):**

1. Find every Puppet Enterprise, Puppet Core and OpenVox server, including ones clients run (Q1, Q2, the checker).
2. Patch now. Then restart the server service and confirm the version.
3. Until patched: set `autosign = false` in the `[server]` section of the CA server's `puppet.conf`, or use
   policy-based autosigning with a policy executable that checks a unique per-node pre-shared secret embedded in the
   CSR. Keep port 8140 reachable only from known agent networks and never from the internet.
4. Review `puppetserver ca list --all` against your inventory. Revoke and clean certificates you cannot account for,
   especially names that extend or shorten a real certname (the CVE-2026-115732 pattern).
5. If a server may be compromised: isolate it and keep its logs (`/var/log/puppetlabs/puppetserver/` on OpenVox).
   OpenVox says code run as the service user can reach the CA signing key, so plan to rebuild the server from
   known-good media, replace the CA and reissue agent certificates. Rotate Hiera eyaml keys, deploy keys and any
   secret the server can read, and check managed nodes for catalog changes you did not make.
6. With `reports = store`, stored reports sit in your `reportdir` (`puppet config print reportdir --section server`).
   OpenVox's fix note says a crafted `__ptype` value in report event data ran the code. OUR PATTERN: a read-only
   search such as `grep -rl '__ptype' "$(puppet config print reportdir --section server)"` lists reports to review;
   legitimate rich data can also carry this key.
7. KEV due dates apply to US federal agencies only (BOD 26-04). Everyone else should patch now regardless.

## Hunts (KQL, Microsoft Sentinel and Microsoft Defender XDR)

File: `kql/puppet-report-deserialization-hunting.kql`. Start date 3 Nov 2026 (OUR choice); widen as retention allows.
The KQL in this pack has NOT been run against a live tenant; it parses cleanly against modelled schemas only.

| Hunt | Label | Looks for | Tables |
| --- | --- | --- | --- |
| Q1 | OUR PATTERN | Hosts listening on 8140 and public sources reaching 8140 (inventory) | DeviceNetworkEvents |
| Q2 | OUR PATTERN | Puppet, Puppet Enterprise and OpenVox packages and versions (inventory) | DeviceTvmSoftwareInventory |
| Q3 | OUR PATTERN [UNVERIFIED fields] | PUTs to `/puppet/v3/report` by certname, compared with your allowlist | CommonSecurityLog, Syslog |
| Q4 | OUR PATTERN | The server JVM (`puppet-server-release.jar`, `puppetserver`) starting sh, bash, dash, zsh, curl or wget | DeviceProcessEvents |
| Q5 | OUR PATTERN | Files or cron entries written by `puppet` or `pe-puppet` outside Puppet's folders; crontab by those users | DeviceFileEvents, DeviceProcessEvents |
| Q6 | OUR PATTERN | Changes to code, environments and server config; new files in the CA `signed/` folder; "Signed CSR for" log lines | DeviceFileEvents, Syslog |

## Sigma rules

| Rule | Label | Level | ATT&CK |
| --- | --- | --- | --- |
| `proc_creation_lnx_puppetserver_jvm_child_shell.yml` | OUR PATTERN | high | T1059.004, T1190 |
| `proc_creation_lnx_puppet_service_user_crontab.yml` | OUR PATTERN | high | T1053.003 |
| `file_event_lnx_puppetserver_jvm_cron_write.yml` | OUR PATTERN | high | T1053.003 |
| `file_event_lnx_puppet_code_change_by_jvm.yml` | OUR PATTERN | medium | T1072 |
| `file_event_lnx_puppet_ca_signed_cert.yml` | OUR PATTERN | low | T1649 |
| `proxy_puppet_report_put.yml` | OUR PATTERN | informational | T1190 |

### Sigma conversion (sigma-cli, pySigma Kusto backend)

`sigma/converted/` holds Kusto conversions for five pipelines (no pipeline, microsoft_xdr, microsoft_365_defender,
sentinel_asim, azure_monitor). Four conversions fail and are recorded as `// CONVERSION FAILED` lines: pipelines that
have no mapping for a log source or field. Use the KQL hunts there instead. Not run against live data.

## Checker (offline, read-only)

`scripts/check-puppet.sh` (bash) and `scripts/Check-Puppet.ps1` (PowerShell 7) give identical output and exit codes.
They open no sockets, write no files and run no other program. They read only the files you name, plus
`/opt/puppetlabs/puppet/VERSION` when you give no version for `core` or `openvox-agent`. They never read
`csr_attributes.yaml`, eyaml keys, private keys or policy executables, never print challengePassword or other CSR
attributes, and never print fingerprints, alt names or extensions from the certificate list.

```
check-puppet.sh --flavour pe|core|openvox-server|openvox-agent [--version V | --version-file FILE]
                [--puppet-conf FILE] [--autosign-conf FILE] [--ca-list FILE] [--allowlist FILE]
pwsh Check-Puppet.ps1 -Flavour pe -Version 2025.12.0 -PuppetConf /etc/puppetlabs/puppet/puppet.conf
```

* `--flavour`: `pe` for the Puppet Enterprise version, `core` for the Puppet Core (puppet-agent) version, or the
  OpenVox package you are checking. Only the published ranges in the table above are used.
* `--puppet-conf`: only the `autosign` setting is read, from `[server]`, then `[master]`, then `[main]` (OUR READING of
  the documented section order). `true` is naive autosign; a path is checked with `--autosign-conf`.
* `--autosign-conf`: an executable file is reported as a policy executable (contents not read; the PowerShell port
  uses any Unix execute bit). Otherwise lines are counted as an allowlist and glob entries (with `*`) are listed.
* `--ca-list`: saved text output of `puppetserver ca list --all`. Requested and signed certnames are compared with
  `--allowlist` (one certname per line, `#` starts a comment); revoked and missing entries are ignored.

| Exit | Meaning |
| --- | --- |
| 0 | OK: version at or above a fixed release, and no autosign or certificate findings |
| 1 | not used (reserved for unexpected runtime errors) |
| 2 | AFFECTED: version inside a range published by Perforce or OpenVox |
| 3 | UNKNOWN: no version, or a version outside the published ranges, and no other findings |
| 4 | REVIEW: not shown as affected, but naive or basic autosign is on, or certificates are outside your allowlist |
| 5 | USAGE OR READ ERROR |

## Contents

* `README.md`: this file
* `kql/puppet-report-deserialization-hunting.kql`: six hunts (Q1 to Q6)
* `sigma/*.yml`: six rules; `sigma/converted/`: Kusto conversions for five pipelines
* `scripts/check-puppet.sh`, `scripts/Check-Puppet.ps1`: offline checkers
* `tests/`: bash and Pester tests, static gates, negative gates, KQL parse check, Sigma conversion, `run_all.sh`
* `tests/fixtures/`: example files marked FIXTURE_ONLY (example.com and example.net names only). The tests copy
  `autosign_policy.sh` and set its execute bit at run time, because some copies of the pack drop file modes.

## Testing

`bash tests/run_all.sh` runs shellcheck, PSScriptAnalyzer, the bash tests, the Pester parity tests, the static gates,
the KQL parse check (Kusto.Language), sandboxed runs of both checkers with no network and a read-only filesystem
(sha256 of the pack compared before and after), `sigma check`, a comparison with `sigma/converted/`, and the negative
gates (faults planted in a copy, each one must be caught). Parsing proves syntax only, not results.

## ATT&CK mapping (MITRE)

* T1190 Exploit Public-Facing Application
* T1059.004 Command and Scripting Interpreter: Unix Shell
* T1053.003 Scheduled Task/Job: Cron
* T1649 Steal or Forge Authentication Certificates
* T1072 Software Deployment Tools

## Sources

* CVE-2026-115731 (cve.org): https://www.cve.org/CVERecord?id=CVE-2026-115731
* CVE-2026-115731 (NVD): https://nvd.nist.gov/vuln/detail/CVE-2026-115731
* CVE-2026-115732 (cve.org): https://www.cve.org/CVERecord?id=CVE-2026-115732
* CVE-2026-115732 (NVD): https://nvd.nist.gov/vuln/detail/CVE-2026-115732
* Perforce advisory, CVE-2026-115731: https://portal.perforce.com/s/cve/a91Qi000003IaHpIAK/report-deserialization-code-execution
* Perforce advisory, CVE-2026-115732: https://portal.perforce.com/s/cve/a91Qi000003IaJRIA0/certificate-name-authorization-bypass
* Puppet Server release notes (Puppet Core): https://help.puppet.com/core/current/Content/PuppetCore/server/release_notes.htm
* Puppet Enterprise what's new (cited only for the 8.22.1 heading): https://www.puppet.com/products/puppet-enterprise/whats-new
* OpenVox announcement, 3 Nov 2026: https://voxpupuli.org/blog/2026/11/03/critical-cve-updates/
* OpenVox Server release notes: https://docs.openvoxproject.org/openvox-server/latest/release_notes.html
* OpenVox release notes: https://docs.openvoxproject.org/openvox/8.x/release_notes.html , https://docs.openvoxproject.org/openvox/9.x/release_notes.html
* OpenVox autosigning: https://docs.openvoxproject.org/openvox/latest/ssl_autosign.html
* OpenVox Server ports, paths and service user: https://docs.openvoxproject.org/openvox-server/latest/install_pre.html , https://docs.openvoxproject.org/openvox-server/latest/install_what_and_where.html , https://docs.openvoxproject.org/openvox/latest/dirs_ssldir.html
* CISA KEV catalogue: https://www.cisa.gov/known-exploited-vulnerabilities-catalog
* MITRE ATT&CK: https://attack.mitre.org/techniques/T1190/ , https://attack.mitre.org/techniques/T1059/004/ , https://attack.mitre.org/techniques/T1053/003/ , https://attack.mitre.org/techniques/T1649/ , https://attack.mitre.org/techniques/T1072/

## Changelog

* 1.0.0 (17 Nov 2026): first release.
