Skip to content
Blog

Perforce · Puppet · Puppet Enterprise

Puppet Enterprise CVE-2026-115731: one agent report to run code on Puppet Server, now in CISA KEV

CVE-2026-115731 (CVSS 9.9): unsafe deserialization in Puppet report processing lets an agent run code on Puppet Server. Added to CISA KEV on Nov 17, 2026.

4 min readCVE-2026-115731

On November 17, 2026, CISA added CVE-2026-115731 to its Known Exploited Vulnerabilities catalog, which means it is being exploited in the wild. US federal agencies have until December 1, 2026 to remediate. The CVE itself has been in NVD since November 3. It sits in Puppet's report-processing code as used by Puppet Server, and therefore affects Perforce's Puppet Enterprise.

What makes it serious is the target. A Puppet Server pushes configuration to every machine it manages. Code execution on that server is potentially a foothold on the whole fleet that trusts it.


The vulnerability

FieldValue
CVECVE-2026-115731
ProductsPuppet (via Puppet Server), Puppet Enterprise
TypeDeserialization of untrusted data (CWE-502), code injection (CWE-94)
CVSS 3.19.9 (CRITICAL), source NVD: CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:H/I:H/A:H
CVSS 4.09.4 (CRITICAL), source Puppet (security@puppet.com)
NVD statusAnalyzed
NVD publicationNovember 3, 2026
CISA KEVadded November 17, 2026, due December 1, 2026
Ransomware useunknown, per CISA

How it works

After each run, a Puppet agent sends the server a report describing what it applied. That report goes up as a PUT request. According to NVD, the code handling those reports deserializes a crafted "rich data" type without checking it, which lets the sender execute arbitrary code on Puppet Server as its service user.

The access requirement explains the PR:L in the vector: the attacker needs any agent certificate signed by the Puppet CA. Put differently, any managed node that gets compromised becomes a stepping stone to the server. The description then adds the worse case: where the CA autosigns certificate requests without strong verification, an unauthenticated network attacker can simply obtain such a certificate.

At that point there is no barrier left. Autosigning is common wherever machines are created and destroyed all day long (autoscaling groups, CI runners, cloud fleets), precisely because it removes a manual step.

The S:C in the NVD vector reflects what a Puppet Server is: the impact reaches beyond the vulnerable component. Our reading is that control of the server opens the door to pushing configuration to agents; the CVE itself describes code execution on the server.


Affected versions

CPE configurations published by NVD:

ProductAffected range (NVD)
Puppetfrom 8.0.0 up to, but excluding, 8.22.2
Puppetfrom 9.0.0 up to, but excluding, 9.1.3
Puppet Enterprisefrom 2023.8.0 up to, but excluding, 2023.8.13
Puppet Enterprisefrom 2025.0.0 up to, but excluding, 2025.12.1
Puppet Enterprise2026.0.0

⚠️ These are range boundaries. The excluded bound is the first version outside the range, not necessarily the release Perforce recommends for your branch. NVD gives no fixed boundary for 2026.0.0. The authoritative source is the Perforce advisory "Report deserialization code execution", referenced by both NVD and CISA.

# Server and Puppet Enterprise versions
puppetserver --version
cat /opt/puppetlabs/server/pe_version 2>/dev/null

Detection

  • Autosigning: check whether your CA signs automatically (autosign = true in puppet.conf, or an autosign.conf with wildcards). If it does, assume the flaw was reachable without authentication.
  • Certificates: list signed certificates (puppetserver ca list --all) and look for any that match no node in your inventory.
  • Reports: in Puppet Server access logs, PUT requests to the report endpoint (/puppet/v3/report/) from unknown certnames or unusual sources.
  • Processes: unexpected children of the Puppet Server Java process (shells, network tools) running as its service user.
  • KEV obligations: CISA's notes point to directive BOD 26-04 and its forensic triage requirements. Even outside the federal space, a KEV listing means you should hunt for traces, not just patch.

Mitigation

  1. Upgrade Puppet Server and Puppet Enterprise to a release outside the ranges above, following the Perforce advisory for your branch.
  2. Turn off autosigning, or restrict it with strong verification (a policy-based autosign script checking a pre-shared secret), both before and after patching.
  3. Revoke unknown certificates and those of decommissioned nodes.
  4. Restrict network access to the Puppet Server port so only managed nodes can reach it.
  5. If you find signs of exploitation, treat the server as compromised: its manifests, code and CA keys drive the entire fleet and all need checking.

Why continuous monitoring matters for admin tooling

Configuration management tools rarely make it into vulnerability monitoring. They feel like internal plumbing, not exposed software. Yet a Puppet Server, like an Ansible controller or a domain controller, concentrates the trust of the whole estate, and a flaw in it is paid for on every machine it manages.

With cveo.tech, register Puppet Server, Puppet Enterprise and the rest of your admin stack with their versions, and get alerted as soon as a critical CVE or a KEV addition hits them.

Know which CVEs hit the versions you run.

Add the product and its version: cveo.tech lists the CVEs that affect it right away, then alerts you by email when a new one affects it — including before NVD has finished its analysis. Free, an account is all it takes.

Every Monday

The week's critical CVEs, in your inbox

One email a week: the CVSS ≥ 9 vulnerabilities published in the last seven days, plus our latest analyses. Nothing else.

Double opt-in by email. Unsubscribe in one click, any time.