Threat level Guarded
Submit a tip

Major threats, straight to your inbox

Only the threats that matter: actively exploited flaws, big breaches and attacks that need action. No spam, unsubscribe any time.

CVE-2026-115731: Puppet RCE Flaw Now Exploited in Attacks

CVE-2026-115731 is a critical Puppet RCE flaw (CVSS 9.4) now in CISA's KEV catalog after active exploitation. See affected versions, fixes and what to do now.

CVE-2026-115731: Puppet RCE Flaw Now Exploited in Attacks

Threat card

Status
Actively exploited
Threat type
Vulnerabilities
Disclosed
Nov 3, 2026
Affected
Perforce Puppet Enterprise before 2026.0.1 / 2025.12.1 / 2023.8.13, Puppet Core before 9.1.3 and 8.22.2, OpenVox / Puppet Server remote code execution

The short version

  • CVE-2026-115731 is a CVSS 9.4 deserialization RCE in Puppet Server report processing.
  • CISA added it to the KEV catalog on 17 November 2026 after active exploitation; federal deadline is 1 December 2026.
  • Certificate auto-signing can make the flaw reachable without any prior credentials.
  • A compromised Puppet Server can expose CA signing keys and push code to the whole fleet.

Last updated: 18 November 2026, 17:58 IST

Summary: CVE-2026-115731 is a critical deserialization flaw (CVSS 9.4) in Perforce Puppet that lets a client with any CA-signed agent certificate run code on the Puppet Server. CISA added it to the Known Exploited Vulnerabilities (KEV) catalog on 17 November 2026, citing active exploitation. Because Puppet controls entire server fleets, a single exploited Puppet Server can hand attackers the whole estate.

CVE-2026-115731 affects Puppet Enterprise, Puppet Core and the open-source fork OpenVox. Perforce fixed it on 3 November 2026, but the flaw is now being exploited, and the U.S. Cybersecurity and Infrastructure Security Agency has ordered federal civilian agencies to patch by 1 December 2026, as reported by The Hacker News on the Puppet KEV listing.

What happened with the CVE-2026-115731 exploit

  • 3 Nov 2026: Perforce releases fixed Puppet Enterprise and Puppet Core builds. Vox Pupuli ships fixed OpenVox releases the same day.
  • 4 Nov 2026: A Puppet administrator posts on Reddit that a misconfigured certificate authority in their fleet led them to trace a CVE-2026-115731 intrusion. This report is not independently verified.
  • Nov 2026: Neodyme AG, whose researcher Alain Rödel found the bug with AI assistance, publishes technical details.
  • 17 Nov 2026: CISA adds CVE-2026-115731 to the KEV catalog based on evidence of active exploitation.
  • 1 Dec 2026: Federal remediation deadline under Binding Operational Directive (BOD) 26-04.

Who is behind it

No threat actor has been publicly linked to the attacks, and CISA has not shared how the flaw is being used. There is no public ransomware claim tied to it yet. Treat attribution as unknown and still developing.

Technical details

The flaw

CISA describes CVE-2026-115731 as deserialization of untrusted data (CWE-502) in Puppet’s report-processing code. A client holding any CA-signed agent certificate can send a report containing a crafted rich-data type in a PUT request and execute arbitrary code on the Puppet Server as the service user. The key condition: if the Puppet certificate authority auto-signs certificate requests without strong checks, an unauthenticated network attacker can simply obtain a valid certificate first and then exploit the bug.

Neodyme also found a companion bug, CVE-2026-115732 (CVSS 9.0), a certificate-name authorization bypass in Puppet and OpenVox. In Neodyme’s Puppet RCE research write-up, the researchers warn that an attacker with code execution on a Puppet Server can take the CA signing keys and impersonate other hosts, regardless of configuration.

Affected and fixed versions

  • Puppet Enterprise 2026.0.0 before 2026.0.1 (fixed in 2026.0.1, Puppet Core 9.1.3)
  • Puppet Enterprise 2025.0.0 before 2025.12.1 (fixed in 2025.12.1, Puppet Core 8.22.2)
  • Puppet Enterprise 2023.8.0 before 2023.8.13 (fixed in 2023.8.13, Puppet Core 8.22.2)
  • Puppet Core 9.0.0 before 9.1.3, and Puppet Core 8.x before 8.22.2
  • OpenVox: fixed in OpenVox Agent 9.3.0 and 8.32.0, OpenVox Server 9.2.0 and 8.18.0, per the OpenVox security advisory GHSA-ffr6-rwpm-p5wq

MITRE ATT&CK mapping

  • T1190 Exploit Public-Facing Application
  • T1649 Steal or Forge Authentication Certificates (CA key theft, rogue agent certificates)
  • T1072 Software Deployment Tools (pushing code to managed nodes through Puppet)
  • T1021 Remote Services (lateral movement from the Puppet Server)

No indicators of compromise have been published by CISA, Perforce or Neodyme at the time of writing.

Impact

Puppet Servers sit at the center of infrastructure-as-code: they push configuration, packages and commands to every managed Linux and Windows node. Code execution on the server means an attacker can push malicious manifests fleet-wide, steal secrets stored in Hiera or catalogs, and forge agent identities with the stolen CA key. Neodyme warns this can lead to ransomware deployment, mass data theft and lateral movement across the network. Organizations that enabled certificate auto-signing are at the highest risk, because the flaw becomes reachable without any prior credentials.

What security teams should do now

  1. Upgrade now to Puppet Enterprise 2026.0.1, 2025.12.1 or 2023.8.13, Puppet Core 9.1.3 or 8.22.2, or the fixed OpenVox releases. This also covers CVE-2026-115732.
  2. Disable naive certificate auto-signing, or enforce policy-based autosign with strong verification of each request.
  3. Audit the Puppet CA for unexpected or recently signed agent certificates, and revoke anything you cannot account for.
  4. Review Puppet Server logs for unusual report PUT requests and for processes spawned by the Puppet service user since early November.
  5. If you find signs of compromise, assume the CA signing keys are stolen: rebuild the CA, reissue agent certificates and rotate secrets stored in Puppet data.
  6. Restrict network access to the Puppet Server so only managed nodes can reach the agent and report endpoints.

Threatspedia will update this page if CISA, Perforce or researchers publish exploitation details or indicators.

What to do now

0 of 6 done

Questions readers ask

What is CVE-2026-115731?

A critical (CVSS 9.4) deserialization flaw in Puppet's report-processing code that lets a client with a CA-signed agent certificate run arbitrary code on the Puppet Server.

Is CVE-2026-115731 being exploited?

Yes. CISA added it to the Known Exploited Vulnerabilities catalog on 17 November 2026, citing evidence of active exploitation.

Which Puppet versions fix CVE-2026-115731?

Puppet Enterprise 2026.0.1, 2025.12.1 and 2023.8.13, Puppet Core 9.1.3 and 8.22.2, and OpenVox Agent 9.3.0 / 8.32.0 and OpenVox Server 9.2.0 / 8.18.0.

Can attackers exploit it without credentials?

Yes, if the Puppet certificate authority auto-signs requests without strong verification, because an attacker can obtain a valid agent certificate first.

Sources

  1. The Hacker News: Hackers Exploiting Critical Puppet RCE Flaw Affecting Enterprise Management Serversthehackernews.com
  2. Neodyme: Puppet RCE researchneodyme.io
  3. OpenVox: Security advisory GHSA-ffr6-rwpm-p5wqgithub.com
  4. CISA: CISA Adds One Known Exploited Vulnerability to Catalogcisa.gov
Share this story
Get the next major threat first

One short email when something serious breaks.

Threatspedia Desk

Threatspedia covers major cyber threats only, verified against primary sources. Read our editorial policy, or report a correction.

Threat alerts

Be first to know when a major threat breaks.

One short email when something serious happens, plus a weekly roundup. Free, no noise.