When the Server Managing Your Systems Becomes the Target
A critical vulnerability in Perforce Puppet shows how compromising one central management server can create security risks across the systems it controls.

Organisations use configuration-management platforms to keep thousands of servers consistent. They automate software installation, apply security settings and distribute configuration changes across their infrastructure.
That central role also makes these platforms attractive targets.
On 17 November 2026, the US Cybersecurity and Infrastructure Security Agency (CISA) added CVE-2026-115731 to its Known Exploited Vulnerabilities (KEV) catalogue, citing evidence of active exploitation. The vulnerability affects Perforce Puppet Enterprise and Puppet Core and can allow remote code execution on a vulnerable Puppet Server. [1][2]
The flaw is caused by improper deserialization of untrusted data in Puppet's report-processing functionality. In practical terms, a specially crafted report submitted by a client holding a certificate signed by the Puppet certificate authority can trigger code execution on the server, under the privileges of the Puppet service account. [2][3]
The certificate requirement matters. An attacker generally needs a valid agent certificate. However, Neodyme's technical analysis explains that environments configured to automatically sign certificate requests without strong verification can make it possible for an attacker to obtain one without proper authorisation. [3]
The consequences can extend beyond the management server itself.
Perforce warned that successful exploitation could expose the server's certificate-signing key. An attacker could then issue trusted certificates and potentially alter software or configuration delivered to managed systems during subsequent Puppet runs. The exact impact depends on the environment's configuration and security controls. [2]
This is why central management infrastructure deserves the same attention as internet-facing applications and critical identity systems. A weakness in a system that distributes software and configuration can have a much wider operational impact than a vulnerability affecting one isolated server.
The vulnerability was patched on 3 November 2026. Fixed releases include Puppet Enterprise 2026.0.1, 2025.12.1 and 2023.8.13, as well as Puppet Core 9.1.3 and 8.22.2. Administrators should also disable automatic certificate signing unless requests are subject to strong verification. [2]
Organisations should take several steps:
-
Identify every Puppet Server and check its version against the affected releases.
-
Upgrade to the relevant fixed version and confirm the service is running the updated build.
-
Review certificate authority settings, especially automatic signing and agent enrolment.
-
Inspect logs for unexpected certificate requests and unusual report submissions.
-
Review the Puppet service account's permissions and access to signing keys.
-
Assess whether any managed systems received unauthorised software or configuration changes before remediation.
A patch closes the known vulnerability, but it does not establish whether an attacker already accessed the environment. Organisations with exposed or potentially compromised systems should investigate historical activity and assess the wider management infrastructure.
Authorised penetration testing can help security teams assess supported digital environments, identify weaknesses in exposed services and examine access paths that could lead to broader compromise.
Bronyx AI, ITSEC's AI-assisted autonomous penetration testing platform, supports authorised security assessments within its confirmed technical scope. It can form part of an application and infrastructure security programme alongside patch management, configuration reviews and continuous monitoring.
Explore Bronyx AI at https://bronyx.ai/.
References
-
CISA, “CISA Adds One Known Exploited Vulnerability to Catalog,” 17 November 2026. https://content.govdelivery.com/accounts/USDHSCISA/bulletins/4332383
-
SecurityWeek, “Critical Perforce Puppet RCE Exploited in Attacks,” 18 November 2026. https://www.securityweek.com/critical-perforce-puppet-rce-exploited-in-attacks/
-
Neodyme, “Pulling the right strings for RCE on a Puppet,” 3 November 2026. https://neodyme.io/blog/puppet_rce/
.png)


