Executive Summary
In November 2026, CISA added CVE-2026-115731 (CVSS 9.4) to its Known Exploited Vulnerabilities catalog following confirmed active exploitation of a critical deserialization remote code execution flaw in Perforce Puppet Enterprise and Puppet Core. Attackers can submit a crafted report via a PUT request using any CA-signed agent certificate to execute arbitrary code as the Puppet service user. Where certificate authority auto-signing is misconfigured, unauthenticated network attackers can obtain a valid certificate and immediately exploit the vulnerability. Puppet's privileged access to entire server fleets makes successful exploitation a worst-case scenario: ransomware deployment, mass data exfiltration, CA key theft, and lateral movement across the enterprise. Patches were released by Perforce on November 3, 2026, with FCEB agencies mandated to remediate by December 1, 2026.
This incident underscores the escalating threat to infrastructure-as-code and configuration management platforms, which sit at the apex of enterprise privilege hierarchies. As attackers increasingly target orchestration and automation layers rather than individual endpoints, organizations that have not enforced zero trust segmentation around management planes and applied egress controls remain acutely exposed to rapid, fleet-wide compromise.
Why This Matters Now
Puppet servers hold privileged access to every managed host in an enterprise fleet, making a single RCE the equivalent of a master key. Active exploitation was confirmed within 24 hours of public disclosure, CISA issued an emergency KEV directive for federal agencies, and the companion certificate-bypass CVE-2026-115732 means even non-default configurations are at risk — creating immediate pressure for all enterprises running Puppet Enterprise or OpenVox to patch and audit CA signing policies now.
Attack Path Analysis
Attackers exploited CVE-2026-115731, a critical deserialization RCE flaw in Puppet Enterprise, by first obtaining a CA-signed agent certificate through a misconfigured auto-signing certificate authority, then submitting a crafted PUT request to the Puppet Server to execute arbitrary code as the service user. With server-level RCE achieved, attackers stole CA signing keys to impersonate hosts, escalated to full infrastructure control, moved laterally across the managed fleet, established persistent command-and-control channels, exfiltrated sensitive configuration and credential data, and ultimately deployed ransomware or conducted mass data exfiltration across the enterprise.
Kill Chain Progression
This analysis maps confirmed threat intelligence to the full cloud kill chain to show where defensive gaps would emerge as an attack progresses.
Initial Compromise
Description
Attackers identified an internet-exposed or network-accessible Puppet Enterprise server running a vulnerable version (pre-2026.0.1, pre-2025.12.1, pre-2023.8.13). Leveraging a misconfigured certificate authority that auto-signed agent certificate requests without strong verification, the attacker obtained a valid CA-signed certificate without authentication. Using this certificate, the attacker submitted a crafted PUT request containing a malicious rich-data type in the report body, triggering deserialization of untrusted data (CVE-2026-115731) and achieving remote code execution as the Puppet service user on the server. The Cloud Native Security Fabric (CNSF) inline IPS capability with Suricata signatures covering known deserialization exploit patterns could have detected and blocked the malicious PUT request payload at the network layer before it reached the vulnerable service.
Related CVEs
CVE-2026-115731
CVSS 9.9Perforce Puppet Enterprise contains a deserialization of untrusted data vulnerability in Puppet's report-processing code that allows a client with any CA-signed agent certificate to execute arbitrary code on the Puppet Server as the service user by submitting a crafted rich-data type via a PUT request; if the CA auto-signs certificates without strong verification, an unauthenticated network attacker can obtain a valid certificate and exploit this flaw.
Affected Products:
Perforce Software Puppet Enterprise – 2026.0.0 before 2026.0.1, 2025.0.0 before 2025.12.1, 2023.8.0 before 2023.8.13
Perforce Software Puppet Core – 9.0.0 before 9.1.3, 8.x before 8.22.2
Vox Pupuli OpenVox Agent – before 9.3.0, before 8.32.0
Vox Pupuli OpenVox Server – before 9.2.0, before 8.18.0
Exploit Status:
exploited in the wildReferences:
https://portal.perforce.com/s/cve/a91Qi000003IaHpIAK/report-deserialization-code-executionhttps://www.cisa.gov/known-exploited-vulnerabilities-cataloghttps://github.com/OpenVoxProject/openvox/security/advisories/GHSA-ffr6-rwpm-p5wqhttps://neodyme.io/en/blog/puppet_rce/https://voxpupuli.org/blog/2026/11/03/critical-cve-updates/CVE-2026-115732
CVSS 9Perforce Puppet Enterprise and OpenVox contain a critical certificate-name authorization bypass vulnerability that allows an attacker to circumvent certificate-based access controls, potentially enabling unauthorized access to managed infrastructure.
Affected Products:
Perforce Software Puppet Enterprise – 2026.0.0 before 2026.0.1, 2025.0.0 before 2025.12.1, 2023.8.0 before 2023.8.13
Perforce Software Puppet Core – 9.0.0 before 9.1.3, 8.x before 8.22.2
Vox Pupuli OpenVox trapperkeeper-authorization – affected versions prior to patch
Exploit Status:
exploited in the wild
MITRE ATT&CK® Techniques
Exploit Public-Facing Application
Command and Scripting Interpreter
Exploitation for Client Execution
Unsecured Credentials: Private Keys
Subvert Trust Controls: Install Root Certificate
Lateral Tool Transfer
Data Encrypted for Impact
Automated Collection
Potential Compliance Exposure
Mapping incident impact across multiple compliance frameworks.
NIST SP 800-53 Rev 5 – Flaw Remediation
Control ID: SI-2
PCI DSS 4.0 – Timely Installation of Security Patches and Updates
Control ID: Requirement 6.3.3
CISA Zero Trust Maturity Model 2.0 – Least-Privilege Network Access and Segmentation
Control ID: Network Pillar — Micro-Segmentation (Advanced)
NIS2 Directive – Supply Chain Security and Vulnerability Handling
Control ID: Article 21(2)(e)
DORA (EU) 2022/2554 – ICT Vulnerability Management and Patching
Control ID: Article 10 — ICT Vulnerability and Patch Management
NYDFS 23 NYCRR 500 – Privileged Access Controls and Anomalous Activity Monitoring
Control ID: Section 500.7 — Access Privileges and Section 500.14 — Monitoring
Sector Implications
Industry-specific impact of the vulnerabilities, including operational, regulatory, and cloud security risks.
Information Technology/IT
Puppet RCE flaw (CVE-2026-115731, CVSS 9.4) directly threatens IT infrastructure teams managing enterprise IaC platforms, enabling ransomware deployment, mass exfiltration, and lateral movement across managed server fleets.
Government Administration
CISA KEV listing and BOD 26-04 mandate compel Federal Civilian Executive Branch agencies to patch by December 1, 2026, as unauthenticated RCE on Puppet servers risks full fleet compromise and data exfiltration.
Computer/Network Security
Deserialization RCE enabling CA key theft and host impersonation exposes security operations to supply-chain compromise, undermining zero-trust segmentation, east-west traffic controls, and egress enforcement across managed environments.
Financial Services
PCI 4.0 compliance obligations and high-value data assets make financial institutions prime ransomware and exfiltration targets if Puppet Enterprise servers remain unpatched, with lateral movement threatening core banking infrastructure.
Sources
- Hackers Exploiting Critical Puppet RCE Flaw Affecting Enterprise Management Servershttps://thehackernews.com/2026/11/hackers-exploiting-critical-puppet-rce.htmlVerified
- CISA Adds One Known Exploited Vulnerability to Catalog - Puppet Deserialization RCEhttps://www.cisa.gov/news-events/alerts/2026/11/17/cisa-adds-one-known-exploited-vulnerability-catalogVerified
- Perforce Puppet Enterprise - Report Deserialization Code Execution (CVE-2026-115731)https://portal.perforce.com/s/cve/a91Qi000003IaHpIAK/report-deserialization-code-executionVerified
- Perforce Puppet Enterprise - Certificate Name Authorization Bypass (CVE-2026-115732)https://portal.perforce.com/s/cve/a91Qi000003IaJRIA0/certificate-name-authorization-bypassVerified
- Neodyme AG - Puppet RCE Research Blog: CVE-2026-115731 and CVE-2026-115732https://neodyme.io/en/blog/puppet_rce/Verified
- OpenVox Critical CVE Updates - Vox Pupuli Bloghttps://voxpupuli.org/blog/2026/11/03/critical-cve-updates/Verified
- OpenVox GitHub Security Advisory GHSA-ffr6-rwpm-p5wqhttps://github.com/OpenVoxProject/openvox/security/advisories/GHSA-ffr6-rwpm-p5wqVerified
- OpenVox trapperkeeper-authorization GitHub Security Advisory GHSA-q4hm-33rc-572ghttps://github.com/OpenVoxProject/trapperkeeper-authorization/security/advisories/GHSA-q4hm-33rc-572gVerified
- CISA Known Exploited Vulnerabilities Cataloghttps://www.cisa.gov/known-exploited-vulnerabilities-catalogVerified
Frequently Asked Questions
Cloud Native Security Fabric Mitigations and ControlsCNSF
Based on the attack progression modeled above, these are the defensive controls that would constrain each stage.
Aviatrix Zero Trust CNSF is directly relevant because this attack chain depended on unimpeded network reachability to a vulnerable Puppet Enterprise server, uncontrolled east-west propagation across a managed fleet, and unrestricted outbound egress for data exfiltration. By enforcing inline inspection, micro-segmented workload boundaries, and controlled egress policies, CNSF would likely have constrained the attacker's ability to reach the vulnerable service, pivot laterally at scale, and exfiltrate data undetected.
Control: Cloud Native Security Fabric (CNSF)
Mitigation: Inline deep packet inspection applied at the network perimeter would likely have flagged and blocked the malicious PUT request payload carrying the crafted deserialization content before it reached the Puppet Server process, reducing the attacker's ability to trigger the RCE condition in the first place.
Control: Zero Trust Segmentation
Mitigation: Identity-aware segmentation policies enforcing least-privilege workload boundaries would likely have limited which processes and network identities could reach the CA key store, reducing the scope of what the compromised Puppet service user could access even after the initial RCE was achieved.
Control: East-West Traffic Security
Mitigation: East-west traffic controls monitoring and restricting workload-to-workload communication paths would likely have surfaced anomalous inter-node connection patterns inconsistent with normal Puppet configuration management baselines, constraining the attacker's ability to propagate freely across the managed fleet at scale.
Control: Multicloud Visibility & Control
Mitigation: Centralized traffic observability across hybrid and multi-cloud environments would likely have identified suspicious automation patterns, repeated anomalous outbound connection sequences, and control-plane deviations that are characteristic of attacker-controlled orchestration activity, reducing the attacker's ability to operate undetected over sustained periods.
Control: Egress Security & Policy Enforcement
Mitigation: Outbound egress controls with FQDN-based filtering and policy-driven traffic restrictions would likely have blocked or flagged unauthorized outbound data transfers destined for attacker-controlled infrastructure, reducing the volume and scope of sensitive data the attacker could successfully move outside the environment.
Had prior CNSF controls constrained lateral movement and egress paths in earlier stages, the attacker's ability to retrieve ransomware binaries from external staging infrastructure and distribute payloads across the fleet would likely have been reduced, limiting the number of Puppet-managed nodes reachable for simultaneous payload deployment.
Impact at a Glance
Affected Business Functions
- Enterprise Infrastructure Configuration Management and Automation
- IT Operations and Server Fleet Orchestration
- Certificate Authority and PKI Trust Infrastructure
- DevOps and Continuous Delivery Pipelines
Estimated downtime: 14 days
Estimated loss: N/A
Exploitation of CVE-2026-115731 grants arbitrary code execution on the Puppet Server as the service user, enabling attackers to harvest the CA signing keys and impersonate any managed host in the fleet. Sensitive data at risk includes infrastructure secrets and credentials stored in Puppet catalogs, configuration data for all managed nodes, CA private key material allowing full PKI compromise, and any plaintext or encrypted secrets managed via Hiera or Puppet Vault integrations. For enterprise environments, this translates to potential mass data exfiltration across all Puppet-managed systems, ransomware deployment to the entire managed fleet, and lateral movement into adjacent network segments. Federal Civilian Executive Branch agencies are specifically at risk given the CISA KEV listing and BOD 26-04 remediation mandate with a December 1, 2026 deadline.
Recommended Actions
Key Takeaways & Next Steps
- • Apply Puppet Enterprise and Puppet Core patches immediately (PE 2026.0.1, PE 2025.12.1, PE 2023.8.13, Core 9.1.3, Core 8.22.2) and audit certificate authority configurations to disable auto-signing of agent certificates without strong identity verification, closing the unauthenticated initial access vector exploited via CVE-2026-115731.
- • Deploy Inline IPS (Suricata) with signatures covering deserialization exploit patterns and malicious PUT request payloads targeting Puppet report-processing endpoints to detect and block initial compromise attempts at the network layer before they reach vulnerable services.
- • Enforce Zero Trust Segmentation with identity-based microsegmentation policies restricting Puppet server access to only authorized management workloads, limiting lateral movement enabled by CA key theft and forged certificate-based fleet propagation, and applying least-privilege namespace controls to prevent the Puppet service user from accessing CA signing key materials.
- • Implement Egress Security and Policy Enforcement with FQDN-based outbound filtering and Cloud Firewall (ACF) egress controls on all Puppet-managed nodes to block unauthorized outbound data transfers to attacker-controlled destinations and prevent ransomware binary retrieval, directly mitigating exfiltration and impact stages.
- • Enable Multicloud Visibility and Control with centralized traffic observability and anomaly detection across the hybrid environment to identify suspicious automation patterns, anomalous Puppet orchestration activity, and east-west lateral movement deviations from legitimate configuration management baselines, enabling rapid incident response before attacker objectives are achieved.



