CISA Confirms Exploitation of Puppet Report Deserialization Flaw

P1 — VALIDATE AND UPDATECritical · 9.4 (CVSS v4.0)EXPLOITATION: CISA-CONFIRMED EXPLOITATION

Quick Answer

Prioritize affected Puppet servers, apply the matching Perforce fixed branch, and review certificate enrollment and report-processing evidence.

Confirm Scope And Apply The Supported Remediation

What to do now: Record Puppet Enterprise and Core versions, server roles, trusted agents, CA enrollment rules and external reachability. Match the stated branch ranges and report-processing path. A signed agent certificate is the normal prerequisite; permissive autosigning can expose the path more broadly. Install the supported fixed release and confirm the server loads the corrected code. Tighten certificate enrollment and unnecessary report-endpoint access while scheduling maintenance. Verify running versions and normal agent reporting. Retain certificate requests, issued-certificate inventories, Puppet reports, service logs, process telemetry and change records for incident review.

Open the authoritative advisory

Last verified: 2026-11-18 UTC. Recheck the authoritative advisory and supported distribution channel before changing production.

Scope And Authority

Product scopePerforce Puppet Enterprise and Puppet Core
AdvisoryCVE-2026-115731
CVECVE-2026-115731
Authoritative release date2026-11-17 — CISA KEV addition; catalog released at 17:53:15 UTC. Perforce lists the original resolution date as 2026-11-03.
Authority revision dateNo separate material revision is established for this release.
Affected versionsPuppet Enterprise 2026.0.0 before 2026.0.1; 2025.0.0 before 2025.12.1; 2023.8.0 before 2023.8.13; Puppet Core 9.0.0 before 9.1.3; Puppet Core 8.x before 8.22.2.
Fixed versionPuppet Enterprise 2026.0.1, 2025.12.1 or 2023.8.13; Puppet Core 9.1.3 or 8.22.2 on the corresponding supported branch
CVSS base score9.4 (CVSS v4.0)
CVSS severityCritical
Exploitation statusCISA confirms exploitation through the November 17, 2026 KEV addition; known ransomware campaign use is Unknown.; no exploitation claim is inferred.

What Changed

CISA added the Puppet report-deserialization flaw to KEV, confirming exploitation. A CA-signed agent certificate can enable server-side code execution; weak autosigning can let an unauthenticated attacker obtain that certificate.

What To Validate Now

  1. Inventory. Record Puppet Enterprise and Core versions, server roles, trusted agents, CA enrollment rules and external reachability.
  2. Establish applicability. Match the stated branch ranges and report-processing path. A signed agent certificate is the normal prerequisite; permissive autosigning can expose the path more broadly.
  3. Remediate. Install the supported fixed release and confirm the server loads the corrected code. Tighten certificate enrollment and unnecessary report-endpoint access while scheduling maintenance.
  4. Validate. Verify running versions and normal agent reporting. Retain certificate requests, issued-certificate inventories, Puppet reports, service logs, process telemetry and change records for incident review.
  5. Retain evidence. Preserve asset and owner identifiers, the applicability decision, before-and-after versions, change approval, installation output, validation results, and any exception or rollback record.

Operational Cautions

CISA lists a December 1, 2026 due date; federal teams must also apply the controlling BOD 26-04 exposure-based requirements. Ransomware campaign use is Unknown. KEV confirms exploitation in the wild, not compromise of a particular installation.

Evidence To Retain

  • Exact product, release stream, package or application version, enabled feature, environment, and accountable owner.
  • UTC timestamps, authority revision, approved change record, installer or package-manager output, and resulting version.
  • Relevant logs and monitoring evidence, test results, exceptions, compensating controls, and rollback decisions.

Related TechGeeks Resources

Authoritative References

Correction policy: If the authority changes affected versions, fixed versions, severity, exploitation information, mitigations, or required action, TechGeeks will update this notice and its verification date.