News · eGov

A deserialization vulnerability in Perforce Puppet Enterprise carrying a CVSS 4.0 score of 9.4 has been added to CISA's Known Exploited Vulnerabilities catalogue, giving US federal civilian agencies until 1 December 2026 to patch.
✦ AI SUMMARY 30-second read

- CVE-2026-115731 allows an attacker with a CA-signed agent certificate to execute arbitrary code on the Puppet Server.
- CISA added the flaw on 17 November 2026; the remediation deadline for federal civilian agencies is 1 December 2026.
- Fixed releases are available across three active Puppet Enterprise lines; autosigning configuration determines how easily the flaw can be exploited.
Why it matters: A compromised Puppet Server gives an attacker a privileged channel into every node the server manages across a potentially large enterprise fleet.

This summary was generated by AI. Editors may review and update it.
CISA added CVE-2026-115731 to its Known Exploited Vulnerabilities catalogue on 17 November 2026. The flaw affects Perforce Puppet Enterprise and carries a CVSS 4.0 score of 9.4. US federal civilian agencies have until 1 December 2026 to remediate it.

The vulnerability is classified as a deserialization of untrusted data weakness. It allows a client that holds a Puppet-CA-signed agent certificate to execute code on the Puppet Server, the central machine responsible for distributing configuration instructions to every node it manages.
CISA lists flaws only when it has evidence of active exploitation. The 17 November addition was the sole entry that day, and no attacker identity, victim count or indicators of compromise have been published alongside the listing.
How the vulnerability works
Puppet agents send a report to the server after each configuration run. The server parses that report, and a crafted submission using a rich-data type delivered through a PUT request causes the server to deserialise untrusted data. Successful exploitation results in arbitrary code execution running as the Puppet Server service user.
The CVSS 4.0 vector reflects network reachability, low attack complexity, low privileges required, no user interaction needed, and high impact on confidentiality, integrity and availability for both the vulnerable system and systems downstream of it. Some third-party databases also show a CVSS 3.x score of 9.9, but the official record lists 9.4 under CVSS 4.0.
The low-privileges requirement means the attacker needs a CA-signed agent certificate rather than an administrator account. In a tightly managed deployment that is a meaningful barrier; in environments where certificate autosigning is open, that barrier may effectively not exist.
Affected and fixed versions
Three active Puppet Enterprise release lines are affected, each with a corresponding fixed release. Primary servers running anything older than 2026.0.1, 2025.12.1 or 2023.8.13 in their respective lines remain exposed. Puppet Core versions 9.1.3 and 8.22.2 also carry the fix.
Upgrading the package alone is insufficient. Puppet Server must be restarted after the upgrade so that the patched code replaces the running process. A second flaw fixed in the same releases, CVE-2026-115732, is an authorisation bypass involving partial certificate name matching; because the fixes arrived together, patching one addresses the other.
Puppet Core 7.x reached end of life in April 2025. Servers still on the 7.x line fall outside all the fixes listed above and require a migration rather than a patch.
What administrators should do before 1 December
Vendor guidance places the autosigning review first because it is quick and immediately reduces exposure. Administrators should disable autosigning or enforce strong validation in autosigning scripts on every Puppet Server, then proceed with the version upgrade.
After restarting the server, the guidance recommends auditing all signed certificates and revoking any that cannot be accounted for. Server activity and report submissions should also be reviewed for signs of abuse.
The December 1 deadline binds only US federal civilian agencies, but a KEV listing is widely regarded as a strong signal that exploitation is already under way. Organisations outside the federal government should treat the deadline as an indicator of urgency rather than a formal obligation.