# Puppet Enterprise: exploited report processing flaw requires server updates

Canonical: https://www.oktsec.com/radar/puppet-enterprise-cve-2026-115731
Publisher: Oktsec
Language: en
Published: 2026-11-17T19:12:01Z
Updated: 2026-11-17T19:12:01Z
Record reviewed: 2026-11-17T19:12:01Z
Latest evidence check: 2026-11-17T19:12:01Z
Disclosed: 2026-11-03

CISA added this Puppet Enterprise flaw to KEV on November 17: a client holding a certificate signed by the Puppet CA can execute code as the server service account. Permissive automatic certificate signing can let an untrusted network client obtain that credential.

## Evidence and response priority

- Category: Vulnerability
- Oktsec priority: Act now
- Rationale: CISA lists known exploitation. A certificate signed by the Puppet CA is required; automatic signing without strong verification can let untrusted clients obtain one.
- Evidence: Attacks confirmed
- Verification: Vendor confirmed
- Fix status: Fix available
- Exposure requirement: Application or configuration dependent
- Vendor: Perforce
- Products: Puppet Enterprise
- CVEs: CVE-2026-115731

## Technical overview

CISA added this flaw to its Known Exploited Vulnerabilities catalog on November 17. That establishes known exploitation, not that every exposed server or managed host has been compromised. The catalog does not identify a victim count or campaign.

The vulnerable code processes agent reports. The attacker needs a certificate signed by the Puppet certificate authority; weak automatic signing can make that credential obtainable by an untrusted client. Execution occurs as the Puppet service account, not necessarily root.

Perforce published the advisory on November 3. Install the corrected release for the existing branch and restart the server. The certificate prerequisite remains relevant when assessing exposure before maintenance.

Oktsec recommends reviewing certificate issuance, submitted reports and unusual service activity before returning the environment to normal operation. Preserve evidence and investigate suspected compromise separately from patch verification.

## Recommended response

Update the installed Puppet Enterprise branch to 2023.8.13, 2025.12.1 or 2026.0.1 and restart Puppet Server. Review certificate issuance and suspicious service activity.

Relevant to: Teams operating Puppet Enterprise servers and their certificate authority.

## CVE attribution

- CVE-2026-115731: Perforce — Puppet Enterprise. [Source](https://raw.githubusercontent.com/CVEProject/cvelistV5/main/cves/2026/115xxx/CVE-2026-115731.json)

## Affected systems and fixes

### Puppet Enterprise 2023

Affected: 2023.8.0 through versions before 2023.8.13. Requires a certificate signed by the Puppet CA.

Fixed release / action: 2023.8.13

### Puppet Enterprise 2025

Affected: 2025.0.0 through versions before 2025.12.1. Requires a certificate signed by the Puppet CA.

Fixed release / action: 2025.12.1

### Puppet Enterprise 2026

Affected: 2026.0.0 through versions before 2026.0.1. Requires a certificate signed by the Puppet CA.

Fixed release / action: 2026.0.1

Confirm the running version against the vendor advisory, including any distribution backports.

## CISA KEV evidence

Catalog: 2026.11.17
Checked: 2026-11-17T19:15:14.934Z

### [CVE-2026-115731](https://www.cisa.gov/known-exploited-vulnerabilities-catalog?field_cve=CVE-2026-115731)

- Added: 2026-11-17
- Ransomware use: Not confirmed by CISA
- Federal due date: 2026-12-01
- Federal forensic triage: No

Action specified by 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.

CISA KEV inclusion establishes known exploitation of the listed CVE, not compromise of your environment. Absence does not rule out exploitation. The date added is not the first attack date. Federal deadlines and forensic triage requirements are context, not universal obligations for private organizations or businesses in Latin America.

## Supporting evidence

Snapshot checked: 2026-11-17T19:15:16.057Z. These dates do not change the incident’s editorial review date.

### FIRST EPSS forecast

- [CVE-2026-115731](https://api.first.org/data/v1/epss?cve=CVE-2026-115731): 0.37% probability of observed exploitation in the next 30 days; percentile 30.88%; score date 2026-11-17.

EPSS is a prediction, not exploitation evidence or organization-specific risk. Confirmed exploitation takes precedence. A missing score is not zero. Check status: available; last successful check: 2026-11-17T19:15:16.057Z.

## Response checklist

1. **Identify servers and signing policy** — Inventory Puppet Enterprise branches, server versions and certificate authority policy. Check whether untrusted clients can obtain signed agent certificates through automatic signing.
2. **Update the installed branch and restart** — Perforce specifies Enterprise 2023.8.13, 2025.12.1 or 2026.0.1, bundling puppet-agent 8.22.2 or 9.1.3. Restart Puppet Server to load the corrected code; verify the running release.
3. **Restrict enrollment and server access** — Oktsec recommends requiring strong verification before signing certificates and limiting server access to approved clients. Changing signing policy does not invalidate certificates already issued.
4. **Review activity before the update** — Oktsec recommends preserving server and CA records, reviewing unexpected certificate issuance and report submissions, and investigating unusual processes under the Puppet service account. An update alone does not establish that a previously exposed environment is clean.

## Relevance to AI environments

Puppet agents are configuration management clients. This advisory does not establish involvement of AI agents.

## Sources

- [Perforce CNA: scope, corrected releases and server restart](https://raw.githubusercontent.com/CVEProject/cvelistV5/main/cves/2026/115xxx/CVE-2026-115731.json) — Perforce; Vendor notice; checked 2026-11-17T19:12:01Z
- [CISA KEV: CVE-2026-115731 added November 17](https://www.cisa.gov/sites/default/files/feeds/known_exploited_vulnerabilities.json) — CISA; Government advisory; checked 2026-11-17T19:12:01Z

## Editorial record

- 2026-11-17T19:12:01Z: Added the November 17 KEV inclusion, certificate prerequisite, Perforce branch corrections and required server restart.

## Use this advisory in Radar

Use the Advisory view to understand the issue and its evidence, Affected systems to compare versions, and Response plan to record applicability, an owner and action progress. Plans are saved only in the current browser and can be downloaded for sharing; they are not a shared team account or an automated scan. Completing a plan does not validate remediation. Talk to Oktsec opens a technical consultation with the advisory and selected service preserved. Scope, fees and access are agreed before any assessment.

[Open advisory](https://www.oktsec.com/radar/puppet-enterprise-cve-2026-115731) · [Build a response plan](https://www.oktsec.com/radar/puppet-enterprise-cve-2026-115731#review-workspace)

- [Exposure check consultation](https://www.oktsec.com/contact?source=radar&intent=assessment&item=puppet-enterprise-cve-2026-115731&service=exposure_check)
- [Patch verification consultation](https://www.oktsec.com/contact?source=radar&intent=assessment&item=puppet-enterprise-cve-2026-115731&service=patch_verification)

## Scope and corrections

Radar is a selected editorial collection, not a complete vulnerability database or a scan of your environment. Priorities are Oktsec analysis. Source confirmation and checklist completion do not establish whether your systems are compromised or secure.

[Sources and methodology](https://www.oktsec.com/radar/about). Report corrections with supporting sources to info@oktsec.com. Do not send secrets or private incident data.

