Payments are experiencing issues due to temporary restrictions in Russia. If your payment does not go through, please submit a support request.Our support team is available 24/7 — we are always here to help with hosting and server issues.We are now accepting requests for dedicated server rental and colocation services in our data center.Reminder: we recommend enabling backups for additional data protection.A new VPS/VDS lineup with NVMe storage and improved performance is now available.Maintenance work on some servers has been completed. All services are operating normally.
Article4 min readViews2

Puppet Enterprise Vulnerability Already Being Exploited: What to Check on the Server

CVE-2026-115731 has been added to the catalog of actively exploited vulnerabilities. Which Puppet Enterprise versions are patched and why verifying trust in agents is critical.

Comments 0

A man examines a key next to a closed metal cabinet in a server room
In this article

On November 17, 2026, CISA added CVE-2026-115731 to its Known Exploited Vulnerabilities (KEV) catalog. The Puppet Enterprise flaw was disclosed on November 3, with the new update confirming its active exploitation. If you manage servers via Puppet, verify the version of your management server, the rules for issuing agent certificates, and the availability of the patch. Simply having a standard VPS or a PHP website does not mean this vulnerability affects you.

Why Trust in Agents Matters

Puppet uses agents to interact with the management server. According to the CVE record prepared by Perforce, a report processing flaw allows a client holding an agent certificate signed by the Puppet Certificate Authority to execute arbitrary code on the Puppet Server as the service user. This is a critical vulnerability rated 9.4 by Perforce on the CVSS 4.0 scale.

A certificate is a critical condition for an attack. If a certificate authority automatically signs requests without strict verification, a network attacker without an account can obtain such a certificate first. Therefore, both the server update and the trust rules for new agents must be checked. The Perforce description refers to the rights of a service account, not to unconditional root access.

Which Puppet Enterprise versions to check

The Perforce entry lists the following affected ranges and fixes:

  • Branch 2023.8: from 2023.8.0 up to but not including 2023.8.13. The fixed version is 2023.8.13.
  • Branch 2025: from 2025.0.0 up to but not including 2025.12.1. The fixed version is 2025.12.1.
  • Branch 2026: from 2026.0.0 up to but not including 2026.0.1. The fixed version is 2026.0.1.

Perforce recommends updating to a release that includes the fixed puppet-agent component 8.22.2 or 9.1.3, and then restarting Puppet Server so it loads the corrected code. This component number does not replace the Puppet Enterprise version number: verify the composition of your release. For another distribution or product that includes Puppet, a supported update path from its vendor is required, including backport information.

Safe order of actions

  • Identify the Puppet Server instance and its actual version. Verify which networks have access to it and under what rules new agents receive signed certificates.
  • Before maintenance, save necessary configurations and data, prepare a recovery plan, and define an acceptable downtime window. Select a fix for a supported product branch.
  • Install the update and perform the provider-specified Puppet Server restart. Verify the version and components of the now-running server: an installed package does not prove that the process loaded the new code.
  • Verify normal report submission from the managed agent. Independently assess unexpected certificates, reports, and processes on the Puppet Server; suspicious findings require investigation, not just patching.

If the update is delayed, the administrator should evaluate restrictions on network access and automatic certificate signing according to provider rules. Such measures may affect agent connectivity and do not resolve the underlying error. Do not disable certificate checks to restore connectivity.

Inclusion in KEV confirms known exploitation, but the entry does not report the date of the first attack, the number of affected systems, or the geography. Use in ransomware campaigns is listed as unknown. This is not proof of a server breach. General iT or client infrastructure testing was not conducted for this material.

Information verified on November 18, 2026, at 09:05 MSK. The practical order above is an editorial guideline, not a report on a completed test.

Discussion 0

Share your experience and ask questions. Comments without links appear after editorial review.

No comments yet. Start the discussion.