// 2 CVE · 2 EXPLOIT IN THE LAST 24H→
CISA added CVE-2026-115731 to the KEV catalog on November 17, 2026, a critical RCE in Puppet Enterprise with CVSS 9.4. Patches arrived November 3, but active exploitation demands a full CA rebuild.

CISA added CVE-2026-115731 to the Known Exploited Vulnerabilities catalog on November 17, 2026. The vulnerability, an untrusted data deserialization in Puppet Server's report processing code, enables remote code execution with a CVSS 9.4 score. The exploit leverages a configuration treated as operational convenience — the certificate authority's autosigning — to turn the security system itself into a vehicle for total fleet compromise.

Key Takeaways
  • CVE-2026-115731 carries CVSS 9.4 and is actively exploited in the wild per CISA, with a federal deadline of December 1, 2026 under BOD 26-04
  • The attack vector requires a CA-signed agent certificate and a crafted report delivered via PUT request on port 8140
  • With autosigning enabled — a common configuration in enterprise deployments — the chain becomes completely unauthenticated
  • CA compromise lets the attacker issue arbitrary certificates, enabling potential lateral movement across the entire managed infrastructure

How the Attack Works: From PUT Request to CA Signing

The vulnerability sits in the Puppet Server component that ingests reports agents return after every configuration run. A client holding any CA-signed agent certificate can send a report containing a crafted rich-data type via PUT request, executing arbitrary code with the service user's privileges.

Puppet Server listens on port 8140 by default. When CA autosigning is active — a scenario the OpenVox maintainers describe as "common for enterprise deployments" — an unauthenticated attacker on the network obtains a valid certificate simply by requesting it from the client enrollment endpoint. The authentication barrier collapses. The malicious report gets processed, and remote code executes.

The real paradigm shift isn't the initial RCE. It's the post-exploitation. Execution as the puppet user grants access to the CA signing key. From that moment, the attacker is no longer an intruder: they are an issuer.

"Code execution as puppet gives access to the CA signing key. This allows the attacker to sign certificates with EKU critical, serverAuth, clientAuth, which could enable direct command execution on other hosts if certain kinds of orchestration is configured" — OpenVox project maintainers

The Trust Architecture Path: From Single Server to Compromised Fleet

Puppet Enterprise isn't just any endpoint. It's the system that defines how every other system is configured. Its compromise isn't an isolated breach: it's an internal supply-chain catastrophe with potential for large-scale ransomware deployment, mass exfiltration, and indefinite persistence.

Neodyme AG, the security firm that coordinated the research, articulated this clearly. The discovery is credited to Alain Rödel, with AI assistance in the analysis process. The same source identified CVE-2026-115732, a certificate name authorization bypass with CVSS 9.0, from the same researcher. Only CVE-2026-115731 appears in CISA's KEV catalog, however.

A Reddit post by user transdimensia, dated November 4, 2026, reported active exploitation post-disclosure: "traced the actions backwards on a [CVE-2026-]115731 intrusion." This element is not independently verified as an authentic incident, but it coexists with CISA's official confirmation of active exploitation.

Affected versions, per HelpNetSecurity, include: Puppet Enterprise 2023.8.0 before 2023.8.13, 2025.0.0 before 2025.12.1, 2026.0.0 before 2026.0.1; Puppet Core 8.x before 8.22.2, 9.0.0 before 9.1.3; OpenVox Agent before 9.3.0/8.32.0, OpenVox Server before 9.2.0/8.18.0. Perforce released patches on November 3, 2026.

What to Do Now

  • Immediately apply the patches Perforce released on November 3, 2026 for affected Puppet Enterprise, Core, and OpenVox versions
  • Verify whether CA autosigning is enabled; if so, evaluate disabling it even post-patch as an attack surface reduction measure
  • If Puppet Server compromise is suspected, rebuild the certificate authority: patching does not remove arbitrary certificates the attacker issued
  • Hunt for compromise indicators in port 8140 access logs and in suspicious agent reports with anomalous rich-data types

The Autosigning Paradox: Convenience That Erases the Boundary

CVE-2026-115731 isn't just a deserialization vulnerability. It's the manifestation of a recurring pattern in enterprise infrastructure: the preference for operational convenience over explicit verification. Autosigning removes friction from node onboarding, but it also removes the moment when an administrator asks "should this client really be part of my trust domain?"

The consequence is that the system designed to guarantee identity — the CA — becomes the mechanism that dissolves it. The attacker doesn't need to steal keys from the outside: they obtain them from the inside, as the prize of the first compromise. For CISOs managing Puppet fleets, the question is no longer whether to patch, but whether their CA has already signed certificates that shouldn't exist.

Frequently Asked Questions

Why isn't patching enough if the server is compromised?

The patch fixes the deserialization vulnerability but does not revoke already-issued certificates. If the attacker gained access to the CA signing key, they may have issued arbitrary certificates that remain valid even after the update. CA reconstruction is necessary to invalidate these artifacts.

Is CVE-2026-115732 also actively exploited?

It does not appear in CISA's KEV catalog as of November 17, 2026. HelpNetSecurity cites it as related with CVSS 9.0, but no confirmations of active exploitation parallel to CVE-2026-115731 have emerged.

How much time do US federal agencies have to apply the patch?

US civilian federal agencies have a deadline of December 1, 2026 under Binding Operational Directive 26-04, roughly two weeks from KEV catalog inclusion.

Sources


Sources and references
  1. helpnetsecurity.com
  2. thehackernews.com
  3. cisa.gov