Threat feed

CVE-2026-115731 — Puppet Enterprise (Puppet Server) report-processing flaw lets one signed certificate run code on the server, exploited in the wild: explainer and fix (listed in KEV, due 1 December)

CVE-2026-115731: Puppet Server report flaw giving code execution (CVSS v4.0 9.4). In KEV since 17 November. Fixed in PE 2026.0.1, 2025.12.1, 2023.8.13.

Published 2026-11-19 Updated 2026-11-19 Last verified 2026-11-19 5 min read
On this page

For: infrastructure and operations teams that run Puppet Enterprise (PE) or Puppet Server. This article is based on the CVE record, CISA KEV and press reports; it does not cover attack steps.

続報待ち:この記事は公式発表に合わせて更新します

Who is affected

infrastructure and operations teams that run Puppet Enterprise (PE) or Puppet Server.

Confirmed so farSee the table ↓
  • The flaw
  • Affected and fixed versions
  • Exploitation
Not yet confirmed
  • How the attacks work and how far they reached (CISA KEV and SSVC indicate exploitation; no detail in official sources)
  • The full text of the Perforce advisory (the page did not render for us; checked against the CVE record and NVD)
  • Treatment of products other than PE, such as Puppet Core (press reports name fixed versions; not confirmed against the advisory text)
What to do nowSee the steps ↓
  1. Check your Puppet Enterprise version
  2. Update to a fixed release and restart puppet server
  3. Review CA autosigning
1 more
  1. Look for unfamiliar certificates and odd reports
Where to verify (source)All sources ↓
Perforce
Last checked
as of November 19, 2026
Follow-up plans and what we checked

CISA added the flaw to KEV on November 17 and its SSVC entry for the same day lists Exploitation as active. Who is attacking, how many victims, and how, are not in official sources, so this site does not state them.

What to do today

1

Check your Puppet Enterprise version

Look up the PE version in the console or on the server. Affected: 2023.8.0 up to but not including 2023.8.13, 2025.0.0 up to but not including 2025.12.1, 2026.0.0 up to but not including 2026.0.1. If you run several lines, list every primary server and compiler (asset inventory checklist).

2

Update to a fixed release and restart puppet server

Perforce's stated solution is to upgrade to a release that bundles puppet-agent 8.22.2 or 9.1.3 (PE 2023.8.13, 2025.12.1 or 2026.0.1) and restart puppet server. An update without a restart leaves the old code running. The KEV due date is 1 December.

3

Review CA autosigning

The CVE record says that where the CA autosigns without strong verification, an unauthenticated network attacker can obtain a certificate. Check the autosign setting in puppet.conf; if it signs everything, switch it off and use verification such as pre-shared keys. The Perforce advisory as quoted in press reports also lists disabling autosigning and strong verification before issuing certificates.

4

Look for unfamiliar certificates and odd reports

Review the signed certificate list for node names you do not recognize. Also check Puppet Server logs, child processes of the service user and unexpected configuration changes. If anything looks wrong, inspect the CA key and the configuration the server distributes, and assess the managed nodes (how to check for intrusion).

What kind of flaw this is

Advisory summary — ADVISORY / KEV
CVE
CVE-2026-115731 (code execution in Puppet report processing)
Severity
CVSS v4.0 9.4 (critical; AV:N/AC:L/AT:N/PR:L/UI:N; assigned by Perforce). NVD scores CVSS v3.1 at 9.9
Type
Deserialization of untrusted data (CWE-502), code injection (CWE-94)
Impact
A client with a CA-signed agent certificate can run arbitrary code on Puppet Server as its service user
Affected
Puppet Enterprise 2023.8.0 to before 2023.8.13, 2025.0.0 to before 2025.12.1, 2026.0.0 to before 2026.0.1
Fix
PE 2023.8.13 / 2025.12.1 / 2026.0.1 (bundling puppet-agent 8.22.2 or 9.1.3). Restart puppet server afterwards
Published
CVE published November 3, 2026 (last updated November 18)
Exploitation
Added to CISA KEV November 17 (due December 1). Ransomware use Unknown, Forensic Triage No
9.4
CVSS v4.0 (Perforce)
Dec 1
KEV due date
1 cert
Prerequisite (obtainable where autosign is lax)
Restart
Required for the fix to take effect
  • In short: Puppet Server processes reports sent by agents. While restoring the received data it does not safely handle a crafted type, so code runs on the server. Neither the official sources nor this site give the request details (the pattern is described in insecure deserialization).
  • The starting point is the side that holds a certificate, so environments with loose certificate issuance have the weakest footing.

What is known and what is not

ItemContentStatus
The flawCode execution through a deserialization defect in report processing (CVE record, NVD)Confirmed (Perforce)
Affected and fixed versionsAs above; restart requiredConfirmed (Perforce)
ExploitationAdded to KEV; SSVC: exploitation active, automatable no, technical impact totalExploitation confirmed (CISA)
Attack method and victimsNot in official sourcesNot stated
Impact on non-PE products (such as OpenVox)Mentioned in press; not confirmed by us against the advisory textUnder investigation

Sources

No attack steps are included. Last verified: November 19, 2026.

Update history

2026-11-19: First report. Based on the CVE record, NVD and CISA KEV; the fact that the vendor advisory body could not be retrieved is listed as unconfirmed.

Latest breaking reports

All breaking reports →

FAQ

QWhat is CVE-2026-115731?
A

A deserialization of untrusted data flaw (CWE-502) in the report-processing code of Puppet, as shipped in Perforce Puppet Enterprise. Per the CVE record, a client holding a CA-signed agent certificate can submit a report with a crafted rich-data type by PUT and execute arbitrary code on Puppet Server as its service user. CVSS v4.0 is 9.4 (critical).

QWhich versions are affected and what is the fix?
A

The CVE record lists Puppet Enterprise 2023.8.0 up to but not including 2023.8.13, 2025.0.0 up to but not including 2025.12.1, and 2026.0.0 up to but not including 2026.0.1. Fixed releases are 2023.8.13, 2025.12.1 and 2026.0.1, which bundle puppet-agent 8.22.2 or 9.1.3. Restart puppet server after the update so the fixed code is loaded.

QCan it be attacked without authentication?
A

Normally a valid CA-signed agent certificate is required. However the CVE record says that where the CA autosigns requests without strong verification, an unauthenticated attacker on the network can obtain such a certificate. Check your autosign settings first.

QIs it being exploited?
A

CISA added it to the KEV catalog on 17 November 2026, with a due date of 1 December. KEV lists ransomware use as Unknown and Forensic Triage as No. The official sources we could read give no detail about the attacks.

QIs there a mitigation if I cannot update yet?
A

As quoted by press reports of the Perforce advisory, disable certificate autosigning on the CA and require strong verification before issuing certificates (per SecurityWeek; we could not render the advisory page itself). This narrows the entry point and is not a substitute for the fix.