Puppet Enterprise deserialization flaw exploited (CVE-2026-115731)
Update (November 18, 2026)
Update: CISA added CVE-2026-115731 to its Known Exploited Vulnerabilities catalog on November 17, 2026, with a federal remediation due date of December 1, 2026, according to SecurityWeek. Treat any exposed Puppet Server as a patch-within-hours item.
SecurityWeek reports the flaw was flagged as exploited on November 4. The same report says a proof-of-concept exploit targeting OpenVox, the open-source Puppet implementation that is also affected, appeared shortly after the November 3 patch. The Hacker News lists fixed OpenVox releases: Agent 9.3.0 and 8.32.0, Server 9.2.0 and 8.18.0. Some coverage still says Perforce is not aware of attacks, which conflicts with the KEV listing; CISA’s entry takes precedence.
Hunting ideas (analysis): review Puppet Server logs for unexpected PUT requests to the report endpoint, recently issued agent certificates you cannot account for, and unplanned changes to code or configuration pushed to managed nodes. A successful attack could expose the CA signing key, so organisations that find signs of exploitation should consider the CA and issued certificates untrusted.
Update (November 18, 2026)
Update: CISA added CVE-2026-115731 to its Known Exploited Vulnerabilities catalog on November 17, with a federal remediation due date of December 1, 2026, according to The Hacker News. Perforce shipped fixes on November 3, so any Puppet Server still on an older release should be upgraded now.
Fixed releases named in the reporting are Puppet Enterprise 2026.0.1, 2025.12.1 and 2023.8.13, and Puppet Core 9.1.3 and 8.22.2. The open-source OpenVox implementation is also affected and has its own fixed releases. Until you upgrade, Security Affairs advises disabling automatic certificate signing unless requests are strongly verified, since autosigning lets an unauthenticated attacker obtain the agent certificate the exploit needs.
Details of how attackers are using the flaw have not been published. A Reddit user claimed exploitation began on November 4, shortly after disclosure; that account is unverified. Security Affairs reports that Perforce says it is not aware of attacks. Treat the CISA KEV listing as the deciding signal and review Puppet Server CA logs and report submissions for unexpected agent certificates.
At a glance
| Severity | CRITICAL |
|---|---|
| CVSS | CVE-2026-115731: 9.4 |
| EPSS (30-day exploit probability) | CVE-2026-115731: 0.4% |
| In CISA KEV (exploited) | Yes, due 2026-12-01 |
| Vendor | Perforce |
| CVE IDs | CVE-2026-115731 |
Primary-source details
- CVE-2026-115731: CVSS 9.4 (Critical), per NVD; fixed in puppet puppet: 8.22.2, 9.1.3 (NVD); puppet puppet enterprise: 2023.8.13, 2025.12.1 (NVD); added to the CISA KEV catalog on 2026-11-17, remediation due 2026-12-01; vendor advisory (listed by NVD).
CISA added a critical Puppet deserialization flaw, CVE-2026-115731, to its Known Exploited Vulnerabilities catalog on 17 November 2026, confirming it is being exploited. According to the CISA KEV entry, the bug in Perforce Puppet Enterprise lets an attacker run code on the Puppet Server. Federal agencies must act by 1 December 2026, and every other Puppet Server operator should treat that as the outer limit.
What happened
The flaw is a deserialization of untrusted data weakness (CWE-502, also tagged CWE-94, code injection) in the report-processing code of Puppet, which Puppet Server uses. A client holding any certificate signed by the Puppet certificate authority can send a report through a PUT request that contains a crafted rich-data type. The server processes it and runs the attacker’s code as the Puppet Server service user.
The NVD record, published on 3 November 2026, scores it CVSS 9.4 (critical) under CVSS 4.0, with a network attack vector, low attack complexity and low privileges required.
Am I affected?
NVD lists these affected releases:
- Puppet 8.0.0 up to but not including 8.22.2
- Puppet 9.0.0 up to but not including 9.1.3
- Puppet Enterprise 2026.0.0
- Puppet Enterprise 2023.8.0 up to but not including 2023.8.13
- Puppet Enterprise 2025.0.0 up to but not including 2025.12.1
NVD records fixes in Puppet 8.22.2 and 9.1.3, and in Puppet Enterprise 2023.8.13 and 2025.12.1. For the single Puppet Enterprise 2026.0.0 release, the NVD record names no separate upgrade target, so check the vendor advisory for guidance on that release.
Technical details
The attack needs a valid agent certificate, which sounds like a high bar. The description explains why it often is not: where the certificate authority autosigns requests without strong verification, an unauthenticated network attacker can obtain a signed certificate and then exploit the flaw. Autosign settings therefore decide how exposed a server really is.
- Exploitation status: confirmed by the CISA KEV listing.
- KEV date added: 2026-11-17. Due date: 2026-12-01.
- Known ransomware campaign use: listed as Unknown by CISA.
- Vendor advisory: Perforce advisory for the report deserialization flaw.
Which threat actors are exploiting the flaw, and against whom, has not been published.
Why this matters
This section is our analysis, not new reporting. A Puppet Server is a configuration management hub: it holds the catalogs, secrets and trust relationships for every node it manages. Code execution as the service user on that server is a strong foothold for lateral movement and for pushing changes to managed hosts. Because exploitation is confirmed, treat patching as an hours-to-days task, not a routine cycle, especially for servers reachable from untrusted networks or running with autosign enabled.
What to do
- Inventory every Puppet Server and Puppet Enterprise install and compare versions against the affected ranges above.
- Upgrade to a fixed release: Puppet 8.22.2 or 9.1.3, or Puppet Enterprise 2023.8.13 or 2025.12.1. Follow the vendor advisory for Puppet Enterprise 2026.0.0.
- Check the certificate authority configuration. Disable blanket autosign, or require strong verification of signing requests, and review which certificates have been signed recently.
- Restrict network access to the Puppet Server port to known agents and management networks.
- If you cannot apply mitigations, CISA’s required action says to discontinue use of the product until they are available.
Detection and hunting ideas
These ideas follow from the attack description, not from published indicators, because no indicators of compromise have been released.
- Review Puppet Server logs for PUT requests to the report endpoint from unfamiliar nodes or newly signed certificates.
- Look for unexpected child processes spawned by the Puppet Server service user, such as shells or download tools.
- Audit recently signed agent certificates and revoke any you cannot tie to a known host.
- Check for unplanned changes pushed to managed nodes since 3 November 2026, when the CVE was published.
- If you find signs of compromise, follow CISA’s forensics triage requirements referenced in the KEV entry and rotate secrets stored on the server.
The practical priority is simple: patch internet-reachable and autosign-enabled servers first, then tighten certificate signing everywhere.
Related coverage
Sources
- CISA Known Exploited Vulnerabilities catalog: CVE-2026-115731
- NVD: CVE-2026-115731
- Perforce advisory: report deserialization code execution
