Critical Perforce Puppet RCE Exploited in Attacks
Perforce Puppet RCE vulnerability CVE-2026-115731 is being exploited in attacks.
A critical deserialization vulnerability (CVE-2026-115731) in Perforce Puppet Enterprise and Core is being actively exploited, allowing attackers to execute code on servers. The flaw, with a CVSS score of 9.4, enables clients with CA-signed certificates to send malicious payloads. Perforce has released patches and advised disabling auto-signing and enforcing strong validation.
AI summary of the linked source. Not reviewed by an editor. How this works
Run Perforce?
Get an email when a new story names Perforce, usually within the hour.
Free. Your list stays private and never appears in a subject line. One click stops it. How Vendor Watch worksPrivacy
The lesson from this incident
Full lessonA critical deserialization vulnerability (CVE-2026-115731, CVSS 9.4) in Perforce Puppet Enterprise and Core is being actively exploited, allowing any client holding a CA-signed certificate to send malicious serialized payloads and achieve remote code execution on the server. The root problem combines an unsafe deserialization flaw with an overly permissive certificate auto-signing feature, which together lower the bar for exploitation to any entity that can obtain a valid certificate. This is particularly dangerous in Puppet environments because the Puppet server typically manages configuration across the entire infrastructure, meaning a compromised server can cascade into full environment takeover. Organizations that delayed patching or never reviewed their auto-signing policies are now paying the price.
What helps against this
How we list vendors- Vulnerability scanning and prioritisation
You know which systems are vulnerable, and which ones to fix first.
- Automated patch management
Known holes get closed in days, not months.
- Endpoint detection and response (EDR and XDR)
Malware and hands-on-keyboard attackers on laptops and servers get spotted and stopped.
Indicators of Compromise
Addresses and file hashes are copied from the publisher's page by pattern matching. Names are picked by AI. On stories from before 17 November 2026, some addresses and hashes were picked by AI too. Not reviewed by an editor. How this works
- cve: CVE-2026-115732
- cve: CVE-2026-115731