CVE-2026-115731
CVE-2026-115731 is a critical-severity vulnerability (CVSS 4.0 CVSS-B score 9.4). 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. CISA added it to the Known Exploited Vulnerabilities catalog on 2026-11-17, with a remediation due date of 2026-12-01 for US federal civilian agencies. As of 2026-11-22, EPSS estimates a 1.2% probability of exploitation in the next 30 days, in the 69th percentile of scored CVEs.
Updated
Perforce Puppet Enterprise Deserialization of Untrusted Data Vulnerability is confirmed as actively exploited and is listed in the CISA KEV catalog.
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.
CISA notes
https://portal.perforce.com/s/cve/a91Qi000003IaHpIAK/report-deserialization-code-execution ; BOD 26-04: https://www.cisa.gov/news-events/directives/bod-26-04-prioritizing-security-updates-based-risk ; Forensics Triage Requirements: https://www.cisa.gov/news-events/directives/bod-26-04-implementation-guidance-prioritizing-security-updates-based-risk ; https://nvd.nist.gov/vuln/detail/CVE-2026-115731
Description
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.
Key Findings
as of 2026-11-22- CISA added CVE-2026-115731 to the KEV catalog 14 days after its CVE record was published. The median for entries added in 2026 so far is 12.5 days.
- Its current EPSS score (1.2%) is higher than that of 3% of CISA KEV entries.
Severity
CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:H/VI:H/VA:H/SC:H/SI:H/SA:HOpen in CVSS calculator Remediation Timeline
BOD 26-04, US federal agenciesDeadlines for US federal civilian agencies under Table 1 of CISA BOD 26-04, from the CVE's KEV status (listed) and CISA's SSVC values (automatable no, technical impact total, 2026-11-17).
How the timeline is set
Table 1 of CISA's Binding Operational Directive 26-04 sets the time US federal civilian agencies have to remediate a vulnerability. It depends on four inputs: whether the asset is publicly exposed, whether the CVE is in the KEV catalog, whether an adversary can automate its exploitation, and whether exploitation gives partial or total control of the asset, which SSVC calls technical impact. CISA publishes the last three for every CVE through services such as its Vulnrichment program.
Days are calendar days. The clock starts at whichever comes first: CISA adds the CVE to the KEV catalog, or the agency identifies the vulnerability on an asset and reports it to its Continuous Diagnostics and Mitigation (CDM) dashboard. A publicly exposed asset is accessible to unauthenticated or untrusted entities via public networks, such as the internet. Forensic triage means assessing the asset to determine whether it has been compromised.
CISA calculates the KEV due date with the same table, using its own evidence on whether the vulnerability is present in a publicly exposed asset. Each agency makes the final exposure decision for each of its assets.
Affected Products
| Vendor | Product | Affected versions |
|---|---|---|
| Perforce | Perforce Puppet Enterprise | 2023.8.0 to <2023.8.13 2025.0.0 to <2025.12.1 2026.0.0 to <2026.0.1 2023.8.13 (unaffected) 2025.12.1 (unaffected) 2026.0.1 (unaffected) |
Solutions and Workarounds
from the CNA's CVE recordSolution
Upgrade to a release that bundles puppet-agent 8.22.2 or 9.1.3 (Puppet Enterprise 2023.8.13, 2025.12.1, or 2026.0.1) and restart puppet server so the fixed code is loaded.
References
1 linksRecord Details
- Published
- 2026-11-03
- Last updated
- 2026-11-18
- Assigner (CNA)
- Perforce
- Credited to
- -
CVE record data © The MITRE Corporation, used under the CVE Terms of Use. Exploited-in-the-wild data from the CISA Known Exploited Vulnerabilities catalog (CC0). Exploit prediction scores by FIRST EPSS (first.org/epss). Alert titles and links from CISA cybersecurity alerts. This site is not affiliated with or endorsed by MITRE, NVD, CISA, or FIRST.