[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"$fTS0aAKkawQjW4DzqSyGv_eNyhrvBRcbqHAitPOUHZvk":3},{"lesson":4},{"id":5,"slug":6,"article_id":7,"title":8,"body":9,"prevention":10,"framework_refs":11,"framework_notes":17,"status":23,"created_at":24,"published_at":25,"article":26,"tags":30,"podcasts":43,"controls":50},"ce81d601-ce6b-4275-a9c5-689aeaa0c554","critical-puppet-rce-flaw-exploited-via-deserialization-and-certificate-trust","032e3f09-0a78-4958-810f-5044e350a5df","Critical Puppet RCE Flaw Exploited via Deserialization and Certificate Trust","A 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.","**Immediate actions:**\n- Apply Perforce's released patches to all Puppet Enterprise and Core installations without delay\n- Disable certificate auto-signing immediately and enforce manual, policy-based certificate approval\n- Audit all currently issued CA-signed certificates and revoke any that cannot be traced to a known, trusted node\n\n**Long-term improvements:**\n- Implement a formal patch SLA for critical-severity (CVSS ≥ 9.0) vulnerabilities affecting infrastructure management tools\n- Restrict Puppet server network access so only authorised managed nodes can reach the Puppet API and certificate endpoints\n- Enforce strict input validation and safe deserialization practices as part of your secure software supply chain requirements for third-party tools\n\n**Detection measures:**\n- Deploy file integrity monitoring and behavioural detection on Puppet servers to alert on unexpected process spawning or configuration changes\n- Centralise and review Puppet server logs for anomalous certificate requests or unusual payload sizes\n- Subscribe to vendor security advisories and CVE feeds for all infrastructure-as-code and configuration management tools in your environment",[12,13,14,15,16],"CIS Control 7: Continuous Vulnerability Management (v8)","NIST SP 800-53 SI-16: Memory Protection","NIST SP 800-53 IA-5: Authenticator Management","NIST CSF 2.0 RS.AN-03: Analysis of incidents","NIS2 Article 21(2)(e)",{"NIS2 Article 21(2)(e)":18,"NIST SP 800-53 SI-16: Memory Protection":19,"NIST CSF 2.0 RS.AN-03: Analysis of incidents":20,"NIST SP 800-53 IA-5: Authenticator Management":21,"CIS Control 7: Continuous Vulnerability Management (v8)":22},"This point requires security in acquisition, development and maintenance including vulnerability handling; it directly mandates that organisations track and remediate vulnerabilities in tools like Puppet that underpin their infrastructure.","SI-16 addresses protections against unsafe data processing including deserialization; enforcing safe deserialization libraries and input validation on the Puppet server would have prevented the malicious payload from executing.","Active exploitation was already occurring, making rapid detection and analysis critical; this category calls for timely analysis of anomalous events that would surface unusual certificate requests or unexpected code execution on the Puppet server.","IA-5 governs the lifecycle and issuance of authenticators such as certificates; disabling auto-signing and enforcing strict certificate issuance policies directly addresses how attackers leveraged CA-signed certificates to authenticate malicious clients.","This control requires organisations to continuously assess and remediate vulnerabilities; applying the Puppet patch promptly and tracking CVSS 9.4 findings would have closed the exploited flaw before attackers reached production servers.","published","2026-11-18T11:21:19.145917+00:00","2026-11-18T11:21:19.125+00:00",{"id":7,"url":27,"slug":28,"title":29},"https:\u002F\u002Fwww.securityweek.com\u002Fcritical-perforce-puppet-rce-exploited-in-attacks\u002F","critical-perforce-puppet-rce-exploited-in-attacks-e7b109","Critical Perforce Puppet RCE Exploited in Attacks",[31,37],{"id":32,"name":33,"slug":34,"description":35,"color":36},"05757c8d-6b93-4194-b35d-7359e7d33b0e","Vulnerability Management","vulnerability-management","Missing scans, no risk prioritization","#fb923c",{"id":38,"name":39,"slug":40,"description":41,"color":42},"af7fce9e-1ce8-4156-93bc-09dcfbfdf29d","Patch Management","patch-management","Unpatched vulnerabilities, delayed updates","#ef4444",[44],{"id":45,"date":46,"edition":47,"title":48,"audio_url":49},"77cf8b97-7175-4e9a-80b6-02a01b6bdc5b","2026-11-18","afternoon","ThreatNoir Afternoon Brief — November 18","https:\u002F\u002Fcdn.threatnoir.com\u002Fpodcasts\u002F2026-11-18\u002Fthreatnoir-afternoon-brief-2026-11-18.mp3",[51,54,57],{"slug":34,"name":52,"problem":53},"Vulnerability scanning and prioritisation","You know which systems are vulnerable, and which ones to fix first.",{"slug":40,"name":55,"problem":56},"Automated patch management","Known holes get closed in days, not months.",{"slug":58,"name":59,"problem":60},"endpoint-detection-response","Endpoint detection and response (EDR and XDR)","Malware and hands-on-keyboard attackers on laptops and servers get spotted and stopped."]