DE EN IT

~/exploited / cve-2026-115731

CVE-2026-115731: Perforce Puppet Enterprise

According to CISA this vulnerability is already used in attacks (added on 17 November 2026).

Key facts

CVECVE-2026-115731
VendorPerforce — Puppet Enterprise
VulnerabilityPerforce Puppet Enterprise Deserialization of Untrusted Data Vulnerability
Added17 November 2026
Deadline (US agencies)1 December 2026
Ransomware campaignsunknown

Technical data (NVD, FIRST EPSS)

CVSS base score9.4 (critical) · CVSS 4.0
CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:H/VI:H/VA:H/SC:H/SI:H/SA:H/E:X/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:X
Attack over the network, complexity: low, privileges: low needed, user interaction: none
EPSS (exploitation probability)Probability of exploitation in the next 30 days: 0.37%. Higher than 30.9% of all scored vulnerabilities (as of 17 November 2026). A low value is no all-clear: CISA already lists this flaw as exploited in attacks.
Weakness type (CWE)CWE-94 — Code Injection
CWE-502 — Deserialization of Untrusted Data

Description (NVD)

Deserialization of untrusted data in the report-processing code of Puppet, as used by Puppet Server, in the affected releases, allows a client that holds any CA-signed agent certificate to execute arbitrary code on the Puppet Server as its service user by submitting a report containing a crafted rich-data type via PUT request. Where the certificate authority autosigns requests without strong verification, an unauthenticated network attacker can obtain such a certificate.

Description (CISA)

Perforce Puppet Enterprise contains a deserialization of untrusted data vulnerability in Puppet’s report-processing code that allows a client with any CA-signed agent certificate to execute arbitrary code on the Puppet Server as the service user by submitting a report containing a crafted rich-data type through a PUT request. If the certificate authority automatically signs requests without strong verification, an unauthenticated network attacker can obtain a valid certificate and exploit the vulnerability.

Required action (CISA)

Apply mitigations in accordance with vendor instructions, ensuring compliance with CISA’s BOD 26-04 Prioritizing Security Updates Based on Risk (see URL in Notes) guidance and CISA’s “Forensics Triage Requirements” (see URL in Notes). Follow applicable BOD 26-04 guidance for cloud services or discontinue use of the product if mitigations are unavailable. Stakeholders are responsible for evaluating each asset's internet exposure and ensuring adherence to BOD 26-04 patching guidelines.

What admins should do now

  1. Affected? Check whether Perforce Puppet Enterprise is in use and which version runs (package manager, admin UI, --version).
  2. Apply the vendor patch or workaround as soon as it exists. If that is not possible right away: restrict outside access (firewall, VPN, reverse proxy).
  3. Review logs back to 17 November 2026: unusual logins, new files, unexpected processes, outbound connections.
  4. If you suspect a compromise: isolate the system, rotate credentials, check the last backup from before the incident.

The deadline applies to US federal agencies. It is still a useful yardstick for everyone: when a flaw is attacked in the wild, waiting is not an option.

Sources

New articles by e-mail

One e-mail per new article. No tracking, unsubscribe any time. As a thank-you after confirming: my “Server operations & patching” checklist (PDF).