Puppet Server RCE CVE-2026-115731 exploited by hackers
The U.S. Cybersecurity and Infrastructure Security Agency (CISA) on Tuesday added a critical security flaw impacting Perforce Puppet, an enterprise infrastructure-as-code (IaC) and configuration manag
What to do
Review the technical details in this article, check if your organization is affected, and apply the recommended security measures. Monitor official vendor advisories for patches and updates.
- Fix and exposure details: CVE-2026-115731 advisory
What Happened
CISA on Tuesday added CVE-2026-115731, a critical remote code execution flaw in Perforce Puppet, to its Known Exploited Vulnerabilities catalog, confirming that attackers are actively exploiting the bug against enterprise management servers. Puppet is an infrastructure-as-code and configuration management platform widely deployed to orchestrate thousands of nodes across large corporate and government networks. The KEV listing follows public reporting of in-the-wild attacks, which means exploitation is no longer theoretical for organizations running exposed Puppet infrastructure.
Why It Matters
Puppet servers are high-value targets precisely because of what they do: they hold the credentials, certificates, and manifests that control the configuration of every managed node in an estate. A successful compromise does not just yield one host - it can hand an attacker the automation pipeline that provisions and updates the entire fleet. That creates a direct path to lateral movement at scale and to pushing malicious configuration changes to thousands of endpoints at once. For defenders, an exploited Puppet master is closer to a domain-controller compromise than a routine web app bug.
Technical Details
The vulnerability is a remote code execution issue in the Puppet management server component, and CISA’s KEV addition indicates confirmed exploitation rather than proof-of-concept activity. Reports describing the attacks point to unauthenticated or low-privilege access paths that allow an attacker to execute code on the Puppet server itself. Because Puppet agents trust the master and pull configuration from it, code execution on the server can be translated into signed catalog payloads delivered to managed nodes. Organizations should treat any Puppet server reachable from untrusted networks as an exposed attack surface until patched, and should scrutinize server logs for unexpected code execution, new administrative users, or anomalous manifest pushes. Indicators tied to the campaign are catalogued in Yazoul’s advisory on this CVE.
Immediate Risk
Severity is critical and urgency is high. The KEV listing typically triggers a binding remediation deadline for U.S. federal agencies, and private-sector defenders should treat that timeline as the floor, not the ceiling. Any organization with a Puppet master exposed to the internet - or to a network segment an attacker has already reached - is in scope. Audit for internet-facing Puppet services now, apply the vendor patch, and rotate credentials and certificates stored on or issued by the Puppet server if exposure is suspected or confirmed. Review agent catalogs for unauthorized changes.
Security Insight
The non-obvious lesson here is a supply-chain inversion: Puppet is designed to be the trusted source of truth, so an exploited master weaponizes trust rather than breaking it. This mirrors the 2020 SolarWinds pattern, where attackers abused a trusted update pipeline instead of exploiting perimeter defenses. Defenders who patch the server but skip catalog and certificate review leave the attacker’s most valuable artifact - malicious configuration already pushed to agents - fully intact. Rotate the master’s signing material, not just its OS patches.
Further Reading
Related
- PHP2Shell exploits hit Palo Alto firewalls via PHP bugsNov 19, 2026
- LiteLLM and Starlette RCE bugs scanned in the wildNov 16, 2026
- UnrealIRCd CVE-2026-114713 exploited, added to CISA KEVNov 14, 2026
- GPUStack auth bypass CVE-2026-102895 exploitedNov 12, 2026
- Puppet Server RCE actively exploited (CVE-2026-115731)Nov 3, 2026