Home › Vulnerabilities

Puppet (Perforce) Puppet Server Flaw CVE-2026-115731: Update Now

Published November 3, 2026 · Last updated November 3, 2026

RCE CVE Critical Patch

The short version: CVE-2026-115731 is a critical-severity security flaw in Puppet (Perforce) Puppet Server. The National Vulnerability Database (NVD) published it on November 3, 2026, and the score it lists is 9.4 out of 10. When FraudMeNot checked on November 3, 2026, CISA had not added CVE-2026-115731 to its Known Exploited Vulnerabilities catalog, so there was no public U.S. government confirmation of attacks yet. A fix is available, which is why this page focuses on who should update and how.

What the official record says about CVE-2026-115731

The record was filed by puppet.com. In its own words: "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."

Why Puppet Server admins should care

Severity scores use the Common Vulnerability Scoring System (CVSS). the address listed on puppet.com rated CVE-2026-115731 9.4 (Critical) under CVSS 4.0. Reading that rating in everyday terms: it can be reached over a network, including the internet; an attacker needs a low-privilege account; no one has to click or open anything. If it is abused, the rated damage to keeping data private is high, to keeping data unaltered is high, and to keeping Puppet Server running is high. Scoring string: 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/E:X/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:X.

Affected Puppet Server releases

According to the record, these releases are vulnerable:

  • 2023.8.0 up to, but not including, 2023.8.13
  • 2025.0.0 up to, but not including, 2025.12.1
  • 2026.0.0 up to, but not including, 2026.0.1

The type of bug behind CVE-2026-115731

NVD classifies it using MITRE's Common Weakness Enumeration:

  • CWE-94, Improper Control of Generation of Code. MITRE describes this class of bug as follows: "The product constructs all or part of a code segment using externally-influenced input from an upstream component, but it does not neutralize or incorrectly neutralizes special elements that could modify the syntax or behavior of the intended code segment. (Roles: Common-Name, Attack-Focused)"
  • CWE-502, Deserialization of Untrusted Data. MITRE describes this class of bug as follows: "The product deserializes untrusted data without sufficiently ensuring that the resulting data will be valid."

Vendor remediation for CVE-2026-115731

The vendor advisory remediation for operators of Puppet Server, quoted for this page, is: "Upgrade to a Puppet Enterprise release that bundles puppet-agent 8.22.2 or 9.1.3 (Puppet Enterprise 2023.8.13, 2025.12.1 or 2026.0.1), or to Puppet Core 9.1.3, then restart Puppet Server so the fixed code is loaded. Affected are Puppet Enterprise 2023.8.0 up to but not including 2023.8.13, 2025.0.0 up to but not including 2025.12.1, and 2026.0.0 up to but not including 2026.0.1. Who should act: anyone who runs a Puppet Server. Also check how your certificate authority signs agent requests; where it autosigns without strong verification, an unauthenticated attacker can obtain the certificate this attack needs, so switch to manual or policy-based signing and review the list of signed agent certificates for any you do not recognize."

What to do about it

  • Update now: Upgrade to a Puppet Enterprise release that bundles puppet-agent 8.22.2 or 9.1.3 (Puppet Enterprise 2023.8.13, 2025.12.1 or 2026.0.1), or to Puppet Core 9.1.3, then restart Puppet Server so the fixed code is loaded. Affected are Puppet Enterprise 2023.8.0 up to but not including 2023.8.13, 2025.0.0 up to but not including 2025.12.1, and 2026.0.0 up to but not including 2026.0.1. Who should act: anyone who runs a Puppet Server. Also check how your certificate authority signs agent requests; where it autosigns without strong verification, an unauthenticated attacker can obtain the certificate this attack needs, so switch to manual or policy-based signing and review the list of signed agent certificates for any you do not recognize.
  • Who should act: IT teams, managed service providers, and developers who run or ship Puppet Server. Check every place it runs, including servers, build systems, containers, and older machines nobody watches closely.
  • Read the official advisory from Puppet (Perforce) (linked under Sources) for exact fixed builds and any temporary workaround if you cannot patch today.
  • After patching, confirm the new version is actually running and review logs from November 3, 2026 onward for anything unusual.
  • Home users: you do not need to buy or download anything because of CVE-2026-115731. A caller, text, or pop-up claiming your computer is "infected" with this CVE and asking for money or remote access is a scam.

CVE-2026-115731 record details from CISA and NVD

  • Attack complexity for CVE-2026-115731: low
  • CVE-2026-115731 attack requirements: none
  • Impact on connected systems: secrecy high, integrity high, availability high.
  • Who mapped the weakness type: the address listed on puppet.com (Secondary)
  • References in the NVD record: 1.

Dates to know

  • November 3, 2026: NVD publishes CVE-2026-115731.
  • November 3, 2026: FraudMeNot checks the CISA KEV catalog; CVE-2026-115731 is not listed.
  • November 3, 2026: most recent NVD update (record status: Received).

Official references

Links listed in the NVD record (labels in brackets come from NVD):

Sources

General education only, not security advice. Facts checked against the sources above on the date shown.