Puppet: verify the restart and certificate trust
Adding CVE-2026-115731 to the KEV catalog increases the priority of patching Puppet Server. Acceptance needs to verify the loaded version and control over agent certificates.
Leggi in portogheseBy Pentesty
Prioritize using the correct access requirement
CISA added CVE-2026-115731 to its Known Exploited Vulnerabilities catalog on November 17, 2026. The Perforce record describes unsafe deserialization in report processing, allowing code execution on Puppet Server with its service user’s privileges.
The condition matters: a client needs an agent certificate signed by the certificate authority, or CA. An unauthenticated attacker can obtain that certificate where the CA automatically signs requests without strong verification. Exposure therefore involves the version, network reachability and certificate issuance. This condition should not be reduced to unrestricted access by anyone to every installation.
Prove that the fixed code is loaded
Perforce’s published solution identifies releases bundling puppet-agent 8.22.2 or 9.1.3: Puppet Enterprise 2023.8.13, 2025.12.1 or 2026.0.1, as appropriate for the release line. It requires restarting Puppet Server to load the fixed code. Recording only package installation leaves that step unverified.
For each server, retain the product release line, installed components, change time and evidence of the authorized restart. Compare the active process and startup records with the change performed. The service owner should confirm operation after maintenance. The analysis of SAP patches and active configuration complements this criterion: acceptance must reach the code and configuration actually serving requests.
Review how agent identities are issued
Identify who approves certificates, which automatic-signing rules are enabled and what evidence links each request to an authorized device. Treat broad rules or rules without an owner as security actions to resolve. Changes to that workflow should preserve an approved path for enrolling and recovering legitimate agents.
In a controlled environment, verify that a request lacking required approval is refused and authorized enrollment still works. Record the applied rule, owner and result using test identities. For certificates already issued, investigate ownership and suspicious events before deciding on containment. The approach to verifiable access revocation supports requiring evidence that previous authority has ended; the specific mechanism must be defined for your Puppet environment.
Assign an owner to each acceptance record
Run a harmless management task agreed in advance through an authorized test node. Ask the owner to check the expected result and records produced on the server. Resolve compatibility or enrollment failures before resuming service. Preserve the approved recovery path for the change as well, so urgent remediation does not depend on a permanent access exception.
Combine the update, restart, service-operation check and certificate-issuance review in a change record. Assign owners to outstanding actions and define follow-up. Authorized tests should validate expected behavior and access refusals without reproducing exploitation in production. Closure must distinguish an applied fix from an investigation that remains open.
Frequently asked questions
Which certificate does CVE-2026-115731 require?
The record requires an agent certificate signed by the CA. Automatic signing without strong verification may let an attacker obtain that identity.
Is installing the fixed release sufficient?
Perforce’s solution also requires restarting Puppet Server to load the fix. Validate the active process and service after the change.
Is CVE-2026-115732 also confirmed as exploited?
The KEV evidence consulted concerns 115731. Do not extend it to the certificate-name matching flaw, which has its own prerequisite.
Does the flaw prove the CA key was stolen?
No. An execution capability does not establish which actions occurred. That conclusion requires investigation and evidence from the specific environment.
Sources and references
- Perforce CNA: CVE-2026-115731, prerequisites and solution
- Perforce CNA: CVE-2026-115732, certificate-name authorization
- CISA: KEV catalog, CVE-2026-115731 entry
- SecurityWeek: Puppet coverage on November 18
- Security Affairs: November18 coverage of the KEV addition
Original Pentesty analysis, published November 18, 2026. The proposed scenarios are editorial guidance, with scope and validation to be defined for each environment.