P.K. SHARMA

Cyber security intelligence, AI governance, practitioner analysis

CISA lists Puppet Enterprise CVE-2026-115731 as exploited 14 days after Perforce's record; who is not stated

CISA added Perforce's Puppet Enterprise flaw CVE-2026-115731 to its Known Exploited Vulnerabilities catalogue on 17 November 2026, 14 days after the CVE record appeared. Who is exploiting it, and whether autosign was involved, is not stated.

By · LinkedIn · · 13 min read

The CVE record appeared on 3 November and the exploited listing on 17 November: 14 days (derived)

Perforce, the assigner, published the CVE record for CVE-2026-115731 on 3 November 2026 at 20:40 UTC. The Known Exploited Vulnerabilities (KEV) catalogue run by CISA lists the same flaw with a date added of 2026-11-17, and a CISA container inside the CVE record carries the rating "Exploitation: active", stamped 2026-11-17. So the first public record of the flaw in the pages this site saved and the first public record of exploitation are 14 calendar days apart (derived: 17 minus 3). Counted to the minute the gap is slightly shorter: the catalogue file this site read was released at 17:53 UTC on 17 November, 13 days 21 hours after the record appeared (derived). The CVE id itself was reserved on 23 October, 25 days before the listing (derived).

The flaw is in Perforce's Puppet Enterprise. The record's title is "Report Deserialization Code Execution", and its description says a client that holds any CA-signed agent certificate can run arbitrary code on the Puppet Server as its service user by submitting a report containing a crafted rich-data type by a PUT request. That is the checkable fact. Here is what it does not establish:

  • When exploitation began. The catalogue prints a date added, not a date of first exploitation, and no saved page gives one.
  • Who is exploiting it, how many servers, and what the attackers did. No saved page says. The catalogue entry says only that the flaw is in the catalogue.
  • What evidence CISA used. The entry does not state it.
  • That autosign was involved. The record names autosign as a condition under which an unauthenticated attacker can obtain a certificate. No saved page says the exploitation CISA lists used it.
  • Whether a public exploit exists. This site read no page that settles it and prints no claim from search results.
  • That open source Puppet or its forks are affected, or are not. The CVE record's affected list names Puppet Enterprise. The Perforce page also lists Puppet Core. No saved page names open source Puppet or the fork OpenVox.
  • Any group behind it. No saved page names one.

The dates, to scale, and what each one is

Diagram 1 puts every date the saved pages print on one axis. The CVE record's vendor part (the container Perforce wrote) was last edited at 20:52 UTC on 3 November, 12 minutes after publication (derived), so the vendor's part of the record as saved says nothing about exploitation. The rating "active" sits in CISA's container, which is dated 17 November.

Drawn from the CVE record, the CISA catalogue entry and the sibling CVE record as saved on 18 November 2026. Positions come from one time scale; intervals are derived.

Table 1. Every date the saved pages print for CVE-2026-115731, with where it is printed. Intervals in the text are derived.

Date (UTC)What it isPrinted in
23 Oct 2026, 11:46CVE id reservedCVE record, dateReserved
3 Nov 2026, 20:40Record published by PerforceCVE record, datePublished
3 Nov 2026, 20:52Last edit of the vendor part of the recordCVE record, vendor container, dateUpdated
3 Nov 2026 (as 11/3/2026)Resolution Date; Reported Date is blankPerforce CVE page
17 Nov 2026Date added to the KEV catalogue; due date set to 2026-12-01CISA catalogue entry
17 Nov 2026 (no time)Exploitation rating "active" stampedCVE record, CISA container
17 Nov 2026, 17:53Catalogue file releasedCISA catalogue file header
18 Nov 2026, 04:55CVE record last updatedCVE record, dateUpdated

Three intervals follow from those dates (all derived): 11 days from reservation to publication, 14 days from publication to the catalogue listing, and 14 days from the listing to the due date. The last two are the same number. The entry does not say how the due date was chosen and this site did not read CISA's directive text, so it does not say the two are related.

The Perforce page prints "11/3/2026" as its Resolution Date. This site reads that month first, as 3 November, because the CVE record was published on that day; read day first it would be 11 March, before the id was reserved.

The condition that decides who is exposed is a setting, not only a version

The record gives two sentences. The first: the flaw "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 with a crafted rich-data type. The second: "Where the certificate authority autosigns requests without strong verification, an unauthenticated network attacker can obtain such a certificate." The CISA catalogue entry repeats both, with "If the certificate authority automatically signs requests without strong verification" in place of "Where".

Drawn from the wording of the CVE record and the Perforce page, as saved on 18 November 2026. The dashed box holds what no saved page states.

Two readings follow, and the second is this site's. A fixed version is what the vendor prints as the cure. Who can reach the flaw is set by who can obtain a certificate, which is a configuration of the certificate authority. Where autosign is on without strong verification, the record says no prior access is needed. Where it is off, the description's condition is still "any CA-signed agent certificate", so any managed node that holds one meets it (this site's reading of the description, not a statement in the record).

Three labels in the pages do the work of a control and are not one:

  • "CA-signed" reads as vetted. The record's own second sentence says that with autosign it can be obtained by an unauthenticated attacker.
  • Privileges required: low. The record's CVSS 4.0 vector prints PR:L, which reads as needing an account. The description, under autosign, says no account is needed. Both are printed; neither is reconciled here.
  • "Automatable: no". The CISA container prints this beside "Exploitation: active". The saved pages do not say what the "no" rests on, and it sits beside a description that mentions an unauthenticated network attacker.

What the catalogue entry says, sets and leaves out

The entry is a catalogue line, not an advisory. It names the vendor and product, repeats the flaw's description, and sets the action and the deadline. Perforce sells Puppet Enterprise, wrote the CVE record and ships the fixed releases, so the description of the flaw is the vendor's own. CISA's catalogue is a US government list: its due date is a remediation deadline for US federal agencies and a prompt for everyone else (this site's reading; the entry does not say who the date binds).

Table 2. The CISA catalogue entry for CVE-2026-115731 as saved on 18 November 2026 (catalogue file released 2026-11-17 at 17:53 UTC, 1,782 entries).

FieldAs printedNote
vendorProject, productPerforce, Puppet EnterpriseOpen source Puppet and forks are not named
vulnerabilityNamePerforce Puppet Enterprise Deserialization of Untrusted Data VulnerabilityNames the weakness class
dateAdded2026-11-17Same day as the CISA container rating
dueDate2026-12-0114 days after dateAdded (derived)
knownRansomwareCampaignUseUnknownNot a statement that there is none
forensicTriageNoSee the differences below
cwesCWE-502, CWE-94Same two as the CVE record
Score, versions, fixNot printedThe entry points to the vendor

The required action starts "Apply mitigations in accordance with vendor instructions", names CISA's directive BOD 26-04 and its "Forensics Triage Requirements", and says to follow cloud guidance or "discontinue use of the product if mitigations are unavailable". It ends: "Stakeholders are responsible for evaluating each asset's internet exposure and ensuring adherence to BOD 26-04 patching guidelines." This site did not read the directive or the triage requirements.

Where the pages differ, with nothing resolved

Four sources were saved: the Perforce CVE page, the CVE record (with its CISA container), the catalogue entry and the sibling record. Diagram 3 shows what each prints and where each is silent. Table 3 lists the differences, each as printed.

Drawn from the four pages saved on 18 November 2026. Wording is the pages own, shortened.

Table 3. Differences between and inside the saved pages. Each is reported as printed; none is resolved.

PointOne page printsAnother prints
SeverityPerforce page and CVE record (Perforce): CVSS 4.0, base score 9.4, CRITICAL, with the vectorCISA catalogue entry: no score. CISA container: no CVSS, only SSVC options
Product nameCVE record text: "Puppet, as used by Puppet Server". Its affected list and the catalogue: Puppet EnterprisePerforce page: Puppet Enterprise and Puppet Core ranges. No page names open source Puppet or OpenVox
Version labelsCVE record solution: a release that bundles puppet-agent 8.22.2 or 9.1.3Perforce page: Puppet Core 8.22.2 and 9.1.3. Same numbers, two names; not reconciled
Who can exploitDescription: any holder of a CA-signed agent certificate; vector PR:LDescription, autosign case: an unauthenticated network attacker. CISA container: Automatable no
ImpactDescription: arbitrary code as the Puppet Server service userCISA container: Technical Impact total
Same day stampsCISA container rating: 2026-11-17, date onlyCatalogue dateAdded: 2026-11-17. Same day; neither has a time
ForensicsRequired action names "Forensics Triage Requirements"The entry field forensicTriage reads No
What the Perforce page isA CVE page: name, number, description, affected, resolved in, rating 9.4, vector, resolution dateNo solution text, no restart instruction, no mitigation, no mention of exploitation. The restart is only in the CVE record

The sibling record, CVE-2026-115732, read on its own

Perforce published a second record the same evening, CVE-2026-115732, 1 minute 46 seconds before the first (derived), and reserved the two ids 25 seconds apart (derived). Its title is "Certificate Name Authorization Bypass". It carries CVSS 4.0 base score 9.0, CRITICAL, with attack requirements PRESENT where the first record has NONE, and CWE-863 and CWE-697. Its description says a client with a CA-signed certificate whose name extends or shortens an authorized hostname can be authorized as that host, which "enables impersonation of other nodes and, in Puppet Enterprise, access to certificate-authority administration and remote command execution on managed nodes". It adds: "Exploitation requires a certificate with a colliding name, which the certificate authority issues by approval or autosign." The affected and fixed Puppet Enterprise releases are the same three. Its solution text names no puppet-agent version and no restart.

CISA's container on that record stamps Exploitation: none on 6 November 2026 at 19:38 UTC. This site saved the catalogue entry for CVE-2026-115731 only, so it does not say whether the sibling is in the catalogue or has been rated differently since. It does not say what, if anything, links the two beyond the certificate authority and the shared releases.

What the pages state, and what they do not

Table 4. What the saved pages establish and what they leave open.

QuestionStatedNot stated
Is it exploited?The catalogue lists it from 17 Nov; the CISA container prints "active"Who, how many servers, since when, what the attackers did, the evidence
Who is exposed by version?Three Enterprise ranges; fixed in 2023.8.13, 2025.12.1, 2026.0.1; Core ranges on the Perforce pageHow many servers run them
What makes it reachable?A CA-signed agent certificate; autosign without strong verification removes the need for prior accessHow many installs autosign; whether autosign featured in the exploitation
Is there a public exploit?Nothing in the saved pagesNot read; searches conflicted and no saved page settles it
Does Perforce say it is exploited?Its part of the record, last edited 3 Nov, and its page say nothing about exploitationWhether Perforce knew of exploitation, and when
Ransomware?knownRansomwareCampaignUse: UnknownAny campaign, group or victim
Other products?Puppet Core ranges on the Perforce pageOpen source Puppet and OpenVox are not named

What the records print

This is the defensive text the saved pages print, copied as printed. The pages print no log lines, detection rules, file names, hashes, addresses or other indicators, and this site prints no request body, type name or payload. A defender can use these items to check versions and to know what the catalogue asks for.

The first block is the CVE record as Perforce wrote it: the identifiers, the weakness classes and the score as the record assigns them.

Text
CVE-2026-115731  (assigner: Perforce)
title: Report Deserialization Code Execution
CWE-502 Deserialization of Untrusted Data
CWE-94 Improper Control of Generation of Code ('Code Injection')
CAPEC-586 Object Injection
CAPEC-242 Code Injection
CVSS 4.0, baseScore 9.4, baseSeverity CRITICAL
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
From the CVE record, vendor container, as saved on 18 November 2026. The score and vector are Perforce's.

The second block is what is affected and what the vendor says to do. The restart is only in the CVE record's solution text. The Core lines are only on the Perforce page.

Text
affected  Puppet Enterprise 2023.8.0 before 2023.8.13
affected  Puppet Enterprise 2025.0.0 before 2025.12.1
affected  Puppet Enterprise 2026.0.0 before 2026.0.1
solution  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.
Perforce page, extra lines:
affected  Puppet Core 9.0.0 before 9.1.3
affected  Puppet Core 8.x before 8.22.2
resolved  Puppet Enterprise 2026.0.1 (Puppet Core 9.1.3)
resolved  Puppet Enterprise 2025.12.1 (Puppet Core 8.22.2)
resolved  Puppet Enterprise 2023.8.13 (Puppet Core 8.22.2)
From the CVE record solution text and the Perforce CVE page, as saved on 18 November 2026.

The third block is CISA's rating inside the CVE record. The options are CISA's wording; the date carries no time of day.

Text
container: CISA-ADP, title "CISA ADP Vulnrichment"
ssvc  role: CISA Coordinator  version: 2.0.3
ssvc  timestamp: 2026-11-17T00:00:00+00:00
ssvc  Exploitation: active
ssvc  Automatable: no
ssvc  Technical Impact: total
timeline  2026-11-17T00:00:00.000Z  CVE-2026-115731 added to CISA KEV
From the CVE record, CISA container, as saved on 18 November 2026.

The fourth block is the catalogue entry's fields, with its notes field omitted (it lists four links to the Perforce page, two CISA directive pages and an NVD page). The typographic quotation marks are the entry's own.

Text
cveID: CVE-2026-115731
vendorProject: Perforce
product: Puppet Enterprise
vulnerabilityName: Perforce Puppet Enterprise Deserialization of Untrusted Data Vulnerability
dateAdded: 2026-11-17
requiredAction: 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.
dueDate: 2026-12-01
knownRansomwareCampaignUse: Unknown
forensicTriage: No
cwes: CWE-502, CWE-94
From the CISA catalogue entry, catalogue file released 2026-11-17 at 17:53 UTC, as saved on 18 November 2026.

What to do, in order

First, what the records say. The CVE record's solution text says to 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. The CISA entry says to apply mitigations in accordance with vendor instructions by the due date of 2026-12-01. The rest is this site's suggestion.

Take this with you

A checklist for a Puppet Enterprise or Puppet Server owner

  • The records: upgrade to Puppet Enterprise 2023.8.13, 2025.12.1 or 2026.0.1 (or a release bundling puppet-agent 8.22.2 or 9.1.3) and restart puppet server so the fixed code is loaded.
  • The records: for US federal agencies the catalogue due date is 2026-12-01; for everyone else it is a prompt.
  • This site's suggestion: list every Puppet Server and Puppet Enterprise install, including test and forgotten ones, and compare each version with the three fixed releases and, if Puppet Core is in use, with 8.22.2 and 9.1.3.
  • This site's suggestion: after upgrading, confirm the puppet server process was restarted. The solution text says the fixed code is not loaded otherwise.
  • This site's suggestion: check the certificate authority autosign setting on each server. Autosign without strong verification is the condition the record names for an attacker with no certificate. Turn it off or tighten it where it is not needed.
  • This site's suggestion: list every agent certificate that is signed and revoke any you cannot account for. The description treats any CA-signed agent certificate as enough.
  • This site's suggestion: treat the Puppet Server as a high value host. It runs code for the estate it manages. Review its reports, logs and outbound connections since 3 November, when the record appeared. The saved pages give no earlier start date for exploitation, so a review that begins on 17 November may miss earlier activity.
  • This site's suggestion: read the headline for what it is. The catalogue says exploited. It does not say by whom, how many, or how.

The question the listing leaves open

CISA's entry settles one thing: somebody has used this flaw. It does not say whether the somebody needed a certificate or was handed one by a setting. The vendor's fix is a version number; the vendor's own description of reach is a configuration. If the only thing between an unknown network client and your configuration server's service user is an autosign setting, who checked it this week?

Key facts

Sources

  1. PrimaryThe CVE record for CVE-2026-115731: dates, description, CWE, CVSS 4.0 metrics, affected and fixed Puppet Enterprise releases, solution text, and the CISA container with the SSVC options and the KEV reference. Read in full by this site on 18 November 2026CVE Services (record assigned by Perforce, with a CISA-ADP container)accessed 2026-11-18
  2. PrimaryThe Known Exploited Vulnerabilities catalogue feed; the entry for CVE-2026-115731 (date added, required action, due date, ransomware field) and the file's release time and entry count, saved on 18 November 2026CISAaccessed 2026-11-18
  3. PrimaryPerforce's CVE page for CVE-2026-115731: description, affected and resolved Puppet Enterprise and Puppet Core ranges, rating, score, resolution date. A rendered copy of the page text was saved on 18 November 2026Perforceaccessed 2026-11-18
  4. PrimaryThe sibling record CVE-2026-115732, Certificate Name Authorization Bypass: read as a record only, for its dates, score, description and the CISA rating of 6 November 2026CVE Services (record assigned by Perforce, with a CISA-ADP container)accessed 2026-11-18

Share this briefing

Know someone who owns this problem? Send it to them.

Related briefings

The briefing, in your inbox

Practitioner analysis of cyber and AI security news. No vendor noise.

How often

Every new briefing in one email, at 7am, or at 7am, 12:30pm and 6pm. Nothing is sent when nothing is new. Unsubscribe any time.