Skip to main content
QUIETLYTIC
Active exploitation

CISA flags exploited Puppet Enterprise report deserialization flaw

CISA added a Puppet Enterprise report deserialization bug to its KEV catalog. Any agent certificate can run code on the Puppet Server; patch by 1 December.

CISA flags exploited Puppet Enterprise report deserialization flaw — Active exploitation
Category
Active exploitation
Severity
Critical
CVEs
CVE-2026-115731

Attackers are exploiting a code execution flaw in Perforce Puppet Enterprise, the configuration management platform many organisations use to push settings and software to their servers. The US Cybersecurity and Infrastructure Security Agency added CVE-2026-115731 to its Known Exploited Vulnerabilities (KEV) catalog on 17 November, two weeks after the CVE was published, and set federal civilian agencies a remediation deadline of 1 December. The bug lands on the Puppet Server itself, which makes it a control-plane problem rather than a single-host one.

How the flaw works

The weakness sits in the code Puppet uses to process the run reports that managed nodes send back to the server after applying their configuration. Report data is deserialized without adequate checks (CWE-502, with CWE-94 code injection also recorded), so a report carrying a specially shaped rich-data value can make the server run code of the sender’s choosing. That code runs with the privileges of the Puppet Server’s service account.

The precondition is a certificate. Puppet agents authenticate to the server with certificates signed by the deployment’s own certificate authority, and the CVE record says any client holding one such agent certificate can trigger the bug. On its own, that limits the attacker pool to machines already enrolled, or anyone who has stolen an enrolled machine’s credentials. The record adds a sharper caveat: where the certificate authority signs new requests automatically without strong checks on who is asking, an attacker with network access and no prior foothold can simply request a certificate and then use it. Because that condition turns an authenticated flaw into one reachable without a foothold, it is worth checking before anything else.

Perforce, the CVE numbering authority for the product, scores the flaw 9.4 (Critical) under CVSS 4.0, with network access, low attack complexity and low privileges required. CISA’s own assessment in the CVE record rates exploitation as active, the technical impact as total, and the flaw as not automatable.

What CISA has and has not said

The confirmed facts are limited to the following:

  • Exploitation is under way. CISA added the vulnerability to KEV on the basis of evidence of active exploitation, and its SSVC entry in the CVE record was updated to show active exploitation on the same day.
  • Three release lines are affected. The CVE record lists 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. Versions the record does not mention are treated as affected by default, so releases outside those ranges, including older lines, should be presumed vulnerable.
  • The deadline is 1 December. Federal civilian agencies must apply the vendor’s mitigations under Binding Operational Directive 26-04, or stop using the product if no mitigation is available. The catalog entry does not require forensic triage for this one.

What remains unknown matters just as much. CISA has not named who is exploiting the flaw, how many deployments have been hit, or which sectors are affected, and its catalog records ransomware use as unknown. No indicators of compromise accompany the entry. The record does not say whether exploitation in the wild relied on autosigned certificates or on certificates taken from already-compromised agents. It also lists only Puppet Enterprise as affected, even though the description refers to Puppet’s report-processing code as used by Puppet Server; whether open-source Puppet Server installations need the same fix is not settled by the government sources.

Why a Puppet Server compromise is serious

This is our assessment, not a statement from CISA. A Puppet Server compiles the configuration that every enrolled node applies, and it usually has access to the secrets those configurations need, such as service passwords, keys and tokens held in data files or connected secret stores. Code execution as the server’s service account therefore offers an attacker more than one host. Depending on how the deployment is built, it can expose credentials used across the estate and, in the worst case, a route to influence what managed machines are told to install or run. That reach is why a configuration management server deserves the same urgency as an identity provider or a hypervisor manager.

What to do now

  1. Find every Puppet Enterprise primary server and compiler. Include test, disaster recovery and lab installations, and note which release line each one runs.
  2. Upgrade to 2023.8.13, 2025.12.1 or 2026.0.1. These releases bundle the fixed puppet-agent (8.22.2 or 9.1.3). The CVE record says the Puppet Server service must be restarted afterwards so the patched code is actually loaded; confirm the restart happened.
  3. Review certificate autosigning now. If the certificate authority signs requests automatically, or relies on weak checks such as hostname patterns, switch to manual approval or a policy-based check with a strong shared secret until every server is patched.
  4. Audit issued agent certificates. Look for certificates signed recently for hostnames you do not recognise, and revoke any that cannot be matched to a real managed node.
  5. Look for signs of earlier compromise. Review server logs for report submissions from unfamiliar certificates or unexpected addresses, and check for new processes, scheduled jobs or files created by the Puppet Server service account. Compare recent changes to code and data in your control repository against what your team actually committed.
  6. Rotate secrets on any server you cannot clear. If a primary server may have been compromised, assume that the credentials it can read have been exposed and replace them.
  7. Limit who can reach the server. Puppet Servers rarely need to accept connections from the public internet; restrict access to the networks where managed nodes actually live.

Organisations outside the US federal government are not bound by the 1 December date, but confirmed exploitation of a critical-rated flaw in an estate-wide control system puts this ahead of routine patching. The CVE search lists other actively exploited flaws covered on this site.

Frequently Asked Questions

Is CVE-2026-115731 in Puppet Enterprise being exploited? Yes. CISA added it to the Known Exploited Vulnerabilities catalog on 17 November 2026 based on evidence of active exploitation. It has not said who is responsible or how widespread the attacks are.

Which Puppet Enterprise versions fix CVE-2026-115731? Puppet Enterprise 2023.8.13, 2025.12.1 and 2026.0.1 contain the fix. Restart the Puppet Server service after upgrading so the patched code is loaded.

Can an attacker exploit this without credentials? Only in some deployments. Exploitation needs an agent certificate signed by the deployment’s certificate authority, but if that authority signs requests automatically without strong verification, an attacker with network access can obtain one. Autosigning should be reviewed or disabled until patching is complete.


Source: Cybersecurity and Infrastructure Security Agency (CISA)

Report an error

Found a factual error, an outdated figure, or a broken source link? Let us know and our editorial desk will review it.


Sources

  1. CISA — CISA Adds One Known Exploited Vulnerability to Catalog (17 November 2026)
  2. CISA — Known Exploited Vulnerabilities Catalog
  3. CISA — BOD 26-04 Implementation Guidance: Prioritizing Security Updates Based on Risk
  4. CVE.org — CVE-2026-115731
  5. NVD — CVE-2026-115731

Related intelligence


Analyst tools