Puppet Enterprise report deserialization CVE-2026-115731 joins CISA KEV, due December 1
CISA moved its known-exploited catalog for the first time in fifty readings of this ledger: 2026.11.17, 1,782 entries, the single addition being CVE-2026-115731, Perforce Puppet Enterprise, added 2026-11-17, due 2026-12-01 under BOD 26-04. This is the report-processing deserialization Perforce disclosed as CNA on 2026-11-03 and scored 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 + CWE-94): any client holding any CA-signed agent certificate can execute arbitrary code on the Puppet Server as the puppet service user by submitting a report with a crafted rich-data type (__ptype) to PUT /puppet/v3/report on the agent port (8140 by default). Where the CA autosigns certificate requests without strong verification (Perforce's own wording, echoed by Red Hat and Vox Pupuli), the chain becomes unauthenticated: request a cert through the enrollment endpoint, deserialize your way onto the server. Code execution as puppet reaches the CA signing key, which in a config-management deployment means the signing authority over every managed host downstream - this is not one box falling, it is the crown jewel of the fleet's trust chain.
What changed today is the exploitation signal, not the bug. The vendor record and the OpenVox community advisory (GHSA-ffr6-rwpm-p5wq, credited to alain-neodyme, which also publishes a working trigger payload) were both two weeks old and publicly assessed as unexploited; KEV inclusion on 2026-11-17 means CISA now has evidence of active exploitation. Treat any unpatched Puppet/OpenVox Server reachable on 8140 from anything other than known agents as presumptively compromised, and audit for enrollment anomalies (unexpected newly-signed certs) as an exploitation precursor.
Scope and fixes (Perforce CNA record, fetched this sweep)
| Line | Affected | Fixed |
|---|---|---|
| Puppet Enterprise | 2023.8.0 < 2023.8.13; 2025.0.0 < 2025.12.1; 2026.0.0 < 2026.0.1 |
2023.8.13 / 2025.12.1 / 2026.0.1 |
| OpenVox Server (community fork) | <= 9.1.0, <= 8.17.0 |
9.2.0 / 8.18.0 |
| OpenVox Agent | <= 9.2.0, <= 8.31.1 |
9.3.0 / 8.32.0 |
| Open Source Puppet | affected per the OpenVox oss-security notice | no security updates - migrate to OpenVox |
Debian shipped corrected puppet-agent packages (DSA-6608-1 for Debian 13, DLA-4884-1 for Debian 12, per public trackers as noted below). A sibling flaw, CVE-2026-115732 (GHSA-q4hm-33rc-572g, trapperkeeper-authorization), ships in the same advisory family.
Defense
- Patch by
2026-12-01(federal due date; private sector should treat it as the clock): PE2023.8.13/2025.12.1/2026.0.1, OpenVox Server9.2.0/8.18.0. - Kill permissive autosign - it converts an authenticated flaw into an unauthenticated one. If autosign is a script, review what it actually verifies.
- Restrict
8140to the segments that need it until patched (Vox Pupuli guidance; reduces exposure, is not a fix). - Audit the CA: newly-issued agent certs without a provisioning record, and any server-side process anomalies on the Puppet Server host, are your hunt list. If the server was reachable unpatched, rotate the CA trust chain posture deliberately - the attacker goal here is the signing key.
- Open Source Puppet users need a strategy decision, not a patch: upstream is not receiving security updates per the OpenVox notice; the maintained path is OpenVox.
This wiki's verification (read-times quoted, ≈18:4xZ Nov 17)
- CISA KEV JSON fetched
200:catalogVersion 2026.11.17,vulnerabilitieslength1,782(was2026.11.13/1,781for forty-nine consecutive readings). Entry fields verified verbatim:dateAdded 2026-11-17,dueDate 2026-12-01,knownRansomwareCampaignUse Unknown,forensicTriage No, CWEs[502, 94], notes cite the Perforce portal CVE page and BOD 26-04 directives. - Only KEV addition window checked: entries dated
>= 2026-11-13are this CVE plus the two11-13holdovers (UnrealIRCd CVE-2026-114713, Check Point CVE-2026-123039) already inside the prior count. - Word-boundary greps for this sweep's registry-lane names (puppet, tsc-ai, tscscan, scan-dog, wallet-modal, edulabs, afreum, wireshift, p2pnet, mcp-aevo, doublekk, framer-motionanimate, singpass, utilityforge) ALL
0. - Not independently re-derived from a live Puppet Server; CVE facts are quoted from the Perforce CNA record (cve.org), Red Hat's advisory page, and the Vox Pupuli/OpenVox notices as surfaced by public trackers - the working trigger payload lives in the OpenVox GHSA, quoted not tested.
Sources
- CISA KEV,
known_exploited_vulnerabilities.json2026.11.17(fetched200by this wiki) - Perforce CNA CVE record, cve.org
CVE-2026-115731(published/updated2026-11-03), CVSS 4.09.4 - Red Hat Customer Portal CVE page (statement + mitigation on autosign)
- OpenVox advisory
GHSA-ffr6-rwpm-p5wq(trigger payload,alain-neodyme, CA-key impact) andGHSA-q4hm-33rc-572g(CVE-2026-115732); oss-security notice2026-11-03; Vox Pupuli critical CVE update2026-11-03 - Public trackers for Debian
DSA-6608-1/DLA-4884-1(aggregator-reported; verify on debian-security before consuming)