CVE record
CVE-2026-115731
Report Deserialization Code Execution
How scary is it?
updated 22 Nov 2026- No
Works without logging in1
Needs a login: a basic user account (CVSS PR:L).
- Yes
Reachable over the network1
Can be attacked remotely (CVSS AV:N).
- Yes
Proof-of-concept code is public2
1 GitHub proof of concept. GitHub proofs of concept are unvetted: some are fake or carry malware. No Exploit-DB entry or Metasploit exploit module on record.
- Yes
Attacks seen in the wild3
CISA lists it as exploited in the wild.
- Yes
On CISA's exploited list (since 17 Nov 2026)3
CISA deadline for US federal agencies: 1 Dec 2026.
Scare-o-meter
Drop everything
Attackers are already on it. Patch now.
- Low signal
- Routine patch
- Act this week
- Drop everything
Why: Listed in CISA's Known Exploited Vulnerabilities catalog: it is being used in attacks.3 Read from the same rule that decides our alert emails.
Are you affected? only if all are true
You run Perforce Puppet Enterprise in an affected version>= 2023.8.0 and < 2023.8.13 / >= 2025.0.0 and < 2025.12.1 / >= 2026.0.0 and < 2026.0.1
Vendor says fixed in: 2023.8.13, 2025.12.1, 2026.0.1.
As published in the CVE record. A version outside these ranges is not a statement that it is unaffected: vendors sometimes understate a range, and distribution builds with backported fixes keep the upstream number.
See the affected products table · Source 1
An attacker can reach it over the network
CVSS attack vector: Network (AV:N). Reachable over the internet or any routable network.
Source 1
The attacker has a user account
CVSS privileges required: Low (PR:L). The attacker needs basic user privileges.
Source 1
Read from the CVE record: affected versions and the CVSS vector. It narrows things down. It does not prove you are safe.
What to do
Per the vendorUpgrade to a fixed release2023.8.13 / 2025.12.1 / 2026.0.1
Fixed releases as stated by the vendor in the CVE record.
See the affected products table · Source 1
CISA required actionApply mitigations in accordance with vendor instructions, ensuring compliance with CISA’s BOD 26-04 Prioritizing…
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's required action for this KEV entry, due 1 Dec 2026 for US federal agencies.
Source 3
Fix reported in the news, AI summaryPuppet Enterprise and Puppet Enterprise Advanced versions 2026.0.1, 2025.12.1, and 2023.8.13; Puppet Core versions…
Steps marked AI were written by a language model, from the CVE record or from the linked news pages. They are not the vendor's wording: check them against the sources.
This is the official CVE record as published. We have not analysed this CVE yet, so there is no plain-English summary, WAF verdict or stack matching here. Browse the CVEs we have analysed.
- CVSS
- 9.4Criticalscored by the publisher (CNA)
- Exploited in the wild
- Yes, in CISA KEV since 17 Nov 2026CISA deadline for US federal agencies: 1 Dec 2026unvetted proof-of-concept code on github
- EPSS
- 1.2%chance of exploitation in the next 30 daystop 31% of scored CVEsFIRST score of 21 Nov 2026
- Fix
- Fixed in 2023.8.13, 2025.12.1, 2026.0.1per the vendor
- Published
- 3 Nov 2026record updated 18 Nov 2026
In the news
Reported by 4 security news and advisory sources since 2026-11-18. Last widely reported 22 Nov 2026.
AI summary of the linked sources, written 22 Nov 2026
Perforce Puppet Enterprise deserialization of untrusted data in the report-processing code allows a client with any CA-signed agent certificate to execute arbitrary code on the Puppet Server as the service user.
- Impact
- An attacker can execute malicious payloads on the server with elevated privileges and could expose the server's certificate-signing key to generate trusted certificates and alter software or configurations.
- Root cause
- Deserialization of untrusted data in Puppet's report-processing code.
- Fix
- Puppet Enterprise and Puppet Enterprise Advanced versions 2026.0.1, 2025.12.1, and 2023.8.13; Puppet Core versions 9.1.3 and 8.22.2.
Summary written from: news4hackers.com, thehackernews.com, helpnetsecurity.com. Other coverage: wid.cert-bund.de.
Written by a language model from those pages only, and not updated when they change. It can be wrong: read the sources.
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.
Affected products
| Product | Affected versions | Vendor says fixed in |
|---|---|---|
| Puppet EnterprisePerforce | >= 2023.8.0 and < 2023.8.13>= 2025.0.0 and < 2025.12.1>= 2026.0.0 and < 2026.0.1Vendor says fixed in: 2023.8.13, 2025.12.1, 2026.0.1 |
As stated by the publisher in the CVE record.
Exploitation evidence
- CISA KEV catalog
- Listed since 17 Nov 2026.
- CISA due date
- 1 Dec 2026, the remediation deadline for US federal agencies
- CISA 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.
- Public exploit code
- Unvetted proof-of-concept code on GitHub: 1 GitHub proof of concept
- CISA SSVC
- exploitation active, automatable no, technical impact totalAssessed by CISA 17 Nov 2026 (SSVC 2.0.3). Exploitation is none, poc (public proof of concept) or active.
GitHub proofs of concept
Listed so you can judge urgency, not as a recommendation to run anything. GitHub “proofs of concept” are unvetted: some are fake or carry malware. Exploit-DB marks the entries its staff verified.
Timeline
- 3 Nov 2026Published
- 17 Nov 2026Added to CISA KEV (exploited in the wild)13 days later
- 17 Nov 2026CISA SSVC assessment: exploitation activesame day later
- 18 Nov 2026First proof-of-concept repository on GitHub (unvetted)1 day later
- 18 Nov 2026CVE record last updatedsame day later
- 1 Dec 2026CISA remediation due date (US federal agencies)13 days later
CVSS 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
References
2 references in the CVE record, grouped by the tags the record gives them.
Other links (2)
- portal.perforce.com /s/cve/a91Qi000003IaHpIAK/report-deserialization-code-execution
- cisa.gov /known-exploited-vulnerabilities-catalog?field_cve=CVE-2026-115731
Record
- Published by
- Perforce
- Published
- 3 Nov 2026
- Last updated
- 18 Nov 2026
- Source
- The CVE List, via cve.org, with CISA’s enrichment (CISA-ADP). Retrieved 21 Nov 2026.
Get CVEs like this by email. Join the free digest: the CVEs we flag as major, all CVSS 8.0 or higher, in up to three emails a day (sent at 05:00, 11:00 and 15:00 UTC). Matching alerts to the products you run needs an account, and accounts are invite-only during the beta.
Have an account? Check a lockfile against known advisories.