
A trusted agent certificate should not become a route to code execution on the configuration server.
What is new — November 17, 2026: CISA added CVE-2026-115731 to its Known Exploited Vulnerabilities catalog. The underlying Perforce notice was published November 3. This new exploitation signal warrants a fresh applicability check for MSP and customer configuration-management infrastructure; it does not establish that any particular customer uses Puppet.
Verified Puppet Enterprise ranges: 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. Perforce’s CNA record marks 2023.8.13, 2025.12.1 and 2026.0.1 unaffected. Other releases are not cleared by this list. The vendor’s Trust Center also names Puppet Enterprise Advanced and Puppet Core; confirm the exact product and supported branch rather than infer identical lower bounds.
The report-processing flaw allows a client holding any CA-signed agent certificate to run code as the Puppet Server service user. Weak certificate autosigning can let an unauthenticated network attacker obtain such a certificate. Restricting autosign alone does not eliminate the risk from an already authorized or compromised agent.
Fix: upgrade to a supported release bundling puppet-agent 8.22.2 or 9.1.3—Perforce maps these to Puppet Enterprise 2023.8.13, 2025.12.1 or 2026.0.1—and restart Puppet Server so the fixed code is loaded. Perforce’s Trust Center lists Puppet Core 8.22.2 or 9.1.3. Exact installer availability and deployment eligibility were not independently checked. Perforce advises reviewing autosign configuration and authorization rules as a temporary measure if immediate upgrade is unavailable; these controls are not a complete fix.
Vendor severity: Critical, CVSS 4.0 base 9.4. Exploitation: CISA’s November 17 KEV addition and its CNA enrichment identify active exploitation. Perforce’s older November 3 Trust Center statement said it was unaware of active exploitation; that statement predates CISA’s new evidence. KEV ransomware use is Unknown and forensicTriage is No. The December 1, 2026 due date is a federal deadline, not a deadline imposed on Brian or customers.
Suggested MSP priority: urgent where an affected server is present. Inventory the exact Enterprise/Advanced/Core release, bundled agent version, server restart state, report-service reachability and certificate enrollment policy. Restrict unneeded access and permissive enrollment where warranted, preserving required management paths. Stage the supported upgrade, restart the server, then verify the running version and loaded fixed code plus legitimate agent enrollment, reporting and configuration runs. If compromise is suspected, preserve evidence and use the established incident-response process; patching does not prove the environment was never compromised. No blanket credential rotation or mandatory forensic procedure was verified in the accessible Perforce material.
Source limits: the detailed Perforce portal returned a loading/CSS error. The affected/fixed matrix and restart requirement were verified in Perforce’s vendor-authored CNA record; mitigation and additional product coverage came from its official Trust Center. CISA’s official repository and Pages JSON/CSV were checked directly; search-rendered raw JSON lagged the current payload. Last verified November 17, 2026.
Perforce CNA record and CISA enrichment · Perforce advisory · Perforce Trust Center · Official CISA KEV JSON