A critical Puppet Server RCE is now under active attack
CISA adds CVE-2026-115731 to its Known Exploited Vulnerabilities catalogue, confirming in-the-wild attacks on a flaw Perforce patched two weeks ago, with a 1 December deadline for federal agencies.
CISA added CVE-2026-115731 to its Known Exploited Vulnerabilities catalogue on 17 November, confirming active attacks on a critical Puppet Server flaw and giving federal civilian agencies until 1 December to patch.
The bug, CVSS 9.4, is a deserialisation of untrusted data in Puppet Server’s report-processing code. Any client holding a CA-signed agent certificate can submit a crafted rich-data type in a report PUT request and run arbitrary code as the server’s service user. Where a certificate authority autosigns requests without strong verification, an unauthenticated attacker can obtain that certificate directly, removing the one precondition. Perforce, which owns Puppet, disclosed the flaw in early November alongside a second bug, CVE-2026-115732 (CVSS 9.0), fixing both in Puppet Enterprise 2023.8.13, 2025.12.1 and 2026.0.1, bundling puppet-agent 8.22.2 or 9.1.3.
Why it matters: Puppet Server sits at the centre of your configuration management, so code execution there means code execution across every node it manages. The patch has been available for two weeks. If you haven’t upgraded and restarted puppet server, CISA’s confirmation of in-the-wild exploitation is the signal to stop treating this as a backlog item.
The caveat: check your CA’s autosigning policy too. A loosely configured autosigner is what turns this from “needs a valid certificate” into “needs nothing at all.”