CVE-2026-115731: How to Protect Puppet and OpenVox Servers

CVE-2026-115731: How to Protect Puppet and OpenVox Servers

CVE-2026-115731 is already being exploited to execute code on vulnerable Perforce Puppet servers, and it also affects OpenVox. The flaw affects Puppet Enterprise, Puppet Core, and OpenVox deployments; first check the server version and update it to a patched version. If you cannot do so immediately, restrict network access and review certificate autosigning.

Who should check their servers

The risk affects those who administer a Puppet Enterprise, Puppet Core, or OpenVox server, not just agent machines. The flaw is in report processing: a client with an agent certificate signed by the Puppet certificate authority (CA) can send manipulated data and execute code on the server with the service user's permissions.

The risk increases if the CA automatically signs requests without robust validation. According to CISA, in that scenario an unauthenticated network attacker could obtain a valid certificate and exploit the flaw. The CVE-2026-115732 vulnerability, also fixed in the same Puppet versions, additionally allows certificate-name authorization to be bypassed and a managed machine to be impersonated.

To find out whether you are affected, identify the version installed on the management server and compare it with the table. SecurityWeek reports that the flaw has been listed as exploited since November 4; CISA added it to its catalog of exploited vulnerabilities on November 17.

ProductAffected versions listedPatched version
Puppet Enterprise2026.0.0 before 2026.0.12026.0.1
Puppet Enterprise2025.0.0 before 2025.12.12025.12.1
Puppet Enterprise2023.8.0 before 2023.8.132023.8.13
Puppet Core9.0.0 before 9.1.39.1.3
Puppet Core8.x before 8.22.28.22.2
OpenVox AgentAffected version not specified8.32.0 or 9.3.0
OpenVox ServerAffected version not specified8.18.0 or 9.2.0

What to do, step by step

  1. Find the server and agent versions. Check your software inventory or package manager to identify Puppet Enterprise, Puppet Core, OpenVox Server, and OpenVox Agent. Do not assume the server is protected just because the agents are up to date: the main flaw is executed on the server. If the deployment comes from a distribution, also verify which product version its package includes.

  2. Compare each version with the fixes. For Puppet, install the patched version corresponding to the branch in the table. For OpenVox, Vox Pupuli lists OpenVox Agent 8.32.0 or 9.3.0 and OpenVox Server 8.18.0 or 9.2.0 as the minimum versions. If your installation uses a package maintained by a distribution, confirm that it contains the fix before considering the update complete.

  3. Update vulnerable servers first. Perforce published the fixes on November 3. Vox Pupuli recommends updating OpenVox immediately and warns that all Puppet deployments it knew of were affected. Follow the update procedure for your installation; do not replace system files or blindly switch to a major version.

  4. Harden certificate issuance. If you cannot update yet, disable autosign or limit its use, and apply strict validation before approving certificates. Perforce recommends avoiding automatic signing without robust verification; Vox Pupuli also advises restricting it. This reduces the likelihood of a network attacker obtaining a certificate, but it does not replace the patch.

  5. Limit who can reach the server. While preparing the update, restrict network access to the segments that actually need to communicate with the OpenVox server, as Vox Pupuli recommends. Do not expose the server interface to networks that do not need access.

  6. Review custom rules after updating. If you have custom authentication rules in OpenVox, check that they still work as expected. Vox Pupuli warns that some may depend on the faulty behavior that was fixed. Perform this validation after patching, and do not keep permissive rules just because they worked before.

  7. Escalate your response if the server may have been exposed. Code execution can provide access to the CA signing key and allow trusted certificates to be issued or other machines to be impersonated. If the server was still vulnerable and accessible, treat the possibility of compromise as a security incident and assess the exposure of that key and the managed systems. Neodyme notes that the subsequent impact depends on the configuration and the active orchestration protocols.

“Independent of the configuration, an attacker with RCE on a Puppet server can grab the CA signing keys and impersonate other hosts.”

— Neodyme

Mistakes to avoid

Do not confuse having a certificate with being safe. CVE-2026-115731 is described as an authenticated vulnerability because it requires a signed agent certificate, but weak autosign configuration may allow one to be obtained without manual approval. Checking only user accounts does not address this access path.

Do not stop at patching an agent. Remote code execution occurs on the server that processes the report; updating only the managed machines does not fix that component. Also check OpenVox servers and their agent versions, and update both where applicable.

Do not mistake a mitigation for a permanent fix. Filtering network access and hardening autosign reduce exposure, but Vox Pupuli warns that these measures do not necessarily eliminate the risk. Also, do not apply manual patches to older versions without understanding their requirements: the project warns that they may not fit properly.

U.S. civilian federal agencies were instructed to apply the fixes by December 1, 2026. For other administrators, the practical priority is to check the server version now and upgrade it to a patched version.

Sources: SecurityWeek, The Hacker News, Neodyme, GitHub, Vox Pupuli