CVERadar

CVE-2026-115731: Perforce Puppet Enterprise flaw exploited in the wild, what we know

CVE REPORT · EXPLOITED IN THE WILDCVE-2026-115731Perforce Puppet EnterpriseCRITICALCVSS 9.4cveradar.org

CVE-2026-115731 affects Perforce Puppet Enterprise; exploited in the wild. What happened, who is affected, how far exploitation has gone and where the patch stands.

CVE-2026-115731 at a glance

CVE-2026-115731 is a critical-severity Deserialization vulnerability in Perforce Puppet Enterprise, with a CVSS 4.0 base score of 9.4. NVD published it on 2026-11-04 and classifies the weakness as CWE-94 and CWE-502. CISA added it to the Known Exploited Vulnerabilities catalog on 2026-11-17; the federal remediation due date is 2026-12-01. FIRST EPSS puts the probability of exploitation activity in the next 30 days at 0.69% (percentile 53.5, scored 2026-11-18). NVD configuration data lists a fixed release for 4 products, for example puppet puppet 8.22.2. CVERadar maps 3 MITRE ATT&CK techniques across Initial Access and Execution, inferred from the CWE and the description. Its CVERadar threat level is 62/100.

Full CVE-2026-115731 record: exploitation evidence, ATT&CK chain and every source.

What it is

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.

  • Severity: CRITICAL (CVSS 4.0 9.4, vector 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).
  • Weakness: CWE-94, CWE-502.
  • NVD published 2026-11-03, status Analyzed.

Who's affected

Anyone running Perforce Puppet Enterprise in the version ranges below. Internet-facing instances are the priority.

  • puppet puppet: from 8.0.0 up to (not including) 8.22.2.
  • puppet puppet: from 9.0.0 up to (not including) 9.1.3.
  • puppet puppet enterprise: from 2023.8.0 up to (not including) 2023.8.13.
  • puppet puppet enterprise: from 2025.0.0 up to (not including) 2025.12.1.

Version ranges come from the NVD CPE configuration. Confirm against the vendor advisory before you rely on them.

Exploitation status

What this means for a small business

CISA added CVE-2026-115731 to its Known Exploited Vulnerabilities catalog on 2026-11-17. A KEV listing means CISA has evidence that attackers are using the flaw against real systems, not just that it could be used.

If your business runs Perforce Puppet Enterprise, put this at the top of the patch list. CISA gave US federal agencies until 2026-12-01 to deal with it, and that is a sensible deadline for a small business too.

  • Patch. Update to a fixed release: puppet puppet 8.22.2 or later; puppet puppet 9.1.3 or later; puppet puppet enterprise 2023.8.13 or later. These versions come from NVD's configuration data, so confirm them against the advisory from Perforce.
  • If you cannot patch yet. Follow CISA's required action: 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.
  • Check your exposure. Find out whether Perforce Puppet Enterprise can be reached from the internet, for example a VPN portal, an admin login page or a file-transfer site. Your firewall's port-forwarding rules and your IT provider's list of public-facing systems are the quickest places to look. Exposed copies come first.
  • When to call IT support. Call your IT support provider now if you run Perforce Puppet Enterprise and cannot confirm it is updated, if it was reachable from the internet before you patched it, or if you notice accounts, sign-ins or files you do not recognise. The last two can mean the system was already hit, and checking that properly takes someone who can read the logs.

Risk

  • EPSS (probability of exploitation activity in the next 30 days): 0.37%, higher than 31% of all scored CVEs (as of 2026-11-17).
  • CVERadar threat level: 62/100 (see methodology).
  • Likely ATT&CK techniques: T1190 Exploit Public-Facing Application (inferred); T1059 Command and Scripting Interpreter (inferred); T1203 Exploitation for Client Execution (inferred).

Remediation steps

  1. Find every instance. List where Perforce Puppet Enterprise runs, including test, DR and forgotten internet-facing systems, and record the installed version.
  2. Upgrade to a fixed release. puppet puppet: 8.22.2 or later; puppet puppet: 9.1.3 or later; puppet puppet enterprise: 2023.8.13 or later; puppet puppet enterprise: 2025.12.1 or later. Get the build from the vendor advisory.
  3. If you can't patch today, follow CISA's required action: 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.
  4. Verify the fix. Re-run the version check on every instance and confirm it reports the fixed build (8.22.2 or later). Re-scan from outside if the service is exposed.
  5. Hunt for signs of earlier compromise. If the system was exposed before you patched, assume it may have been hit and check the items below.
  6. Rotate credentials stored on or used by the affected system if you cannot rule out compromise, and keep the logs you reviewed.

Detection hints

  • T1190 Exploit Public-Facing Application: Review WAF, reverse-proxy and application logs for unusual requests to Puppet Enterprise (odd paths, oversized or encoded payloads, bursts of errors), going back to at least 2026-11-03.
  • T1059 Command and Scripting Interpreter: Watch for the service process spawning shells or script interpreters.
  • T1203 Exploitation for Client Execution: Exploitation of client or server software usually shows as crashes of the affected process followed by unexpected child processes; check EDR alerts for both.

Detection commands are generic starting points, not CVE-specific signatures. Use the indicators from the vendor advisory when it publishes them.

Sources

← Back to blog
Keep reading

Related articles

Track every exploited CVE

Full record for CVE-2026-115731, with the ATT&CK chain and every source. Browse what attackers are using right now, and who is affected.

Exploited in the wildHow we score