RC RANDOM CHAOS

CISA flags exploited Puppet bug enabling CA key theft

CISA added CVE-2026-115731, a 9.4 Puppet deserialization RCE, to its KEV catalog amid active exploitation. Patch, and consider rotating the CA key.

· 3 min read
CISA flags exploited Puppet bug enabling CA key theft

CISA added CVE-2026-115731 to its Known Exploited Vulnerabilities catalog on Tuesday, citing reports of active exploitation. The flaw rates 9.4 on CVSS and sits in Perforce Puppet, a configuration management platform that often has full access to a fleet of systems.

The bug is a deserialization of untrusted data in Puppet’s report-processing code. CISA’s writeup describes the path precisely: a client holding any CA-signed agent certificate can submit a report with a crafted rich-data type through a PUT request and execute arbitrary code on the Puppet Server as the service user. The certificate requirement reads like a barrier until you consider how Puppet CAs are usually run. If the CA automatically signs requests without strong verification, an unauthenticated attacker on the network can obtain a valid certificate and then reach the vulnerable code. Autosigning is common in fleets that provision hosts dynamically, which turns a client-authenticated bug into an unauthenticated one.

What makes this worth dropping everything for is where the code runs. Neodyme AG, whose researcher Alain Rödel reported the flaw, put the consequence plainly: “an attacker with RCE on a Puppet server can grab the CA signing keys and impersonate other hosts.” The exact blast radius depends on the server configuration and which orchestration protocols are enabled, but the CA key theft holds regardless. Puppet typically runs with full access to a fleet of systems, so code execution on the server opens the door to ransomware deployment, mass data exfiltration, and lateral movement, in Neodyme’s framing.

Affected versions:

  • Puppet Enterprise 2026.0.0 before 2026.0.1
  • Puppet Enterprise 2025.0.0 before 2025.12.1
  • Puppet Enterprise 2023.8.0 before 2023.8.13
  • Puppet Core 9.0.0 before 9.1.3
  • Puppet Core 8.x before 8.22.2

Perforce shipped fixes on November 3 in Puppet Enterprise 2026.0.1 (Puppet Core 9.1.3), 2025.12.1 and 2023.8.13 (both Puppet Core 8.22.2), and standalone Puppet Core 9.1.3 and 8.22.2. OpenVox, the open-source Puppet implementation, is affected too and is fixed in OpenVox Agent 9.3.0 and 8.32.0, and OpenVox Server 9.2.0 and 8.18.0.

Rödel also reported CVE-2026-115732, a certificate-name authorization bypass rated 9.0 that affects both Puppet and OpenVox. Neodyme says both issues were found with AI assistance and precise steering. If you are patching one, patch both.

Patching the server binary is the obvious step, and the one FCEB agencies are bound to under BOD 26-04, with a deadline of December 1. Two things deserve attention beyond the version bump. First, the autosign configuration: a CA that signs certificate requests without strong verification is one way an unauthenticated attacker can obtain a valid certificate and reach this bug, and it is worth auditing whether or not you have patched. Second, if you have reason to think a server was hit, patching does not undo a stolen CA key. The researchers’ own warning is that RCE lets an attacker walk off with the CA signing material and impersonate other hosts, so incident response has to consider rotating the CA, not just updating the package.

There are no public details yet on how the flaw is being used in the wild. The signal that it is comes from a Reddit user, transdimensia, who wrote on November 4 that they traced a 115731 intrusion backward after finding a severely misconfigured CA in their fleet.

Share

Keep Reading

Latest on the Wire

Full wire →

New signal daily · RSS

Stay in the loop

New writing delivered when it's ready. No schedule, no spam.