NIST deprecates RSA-2048 from 2030. Find every one of them before attackers do.
🛡️
Not in CISA KEV
CRITICAL severity

CVE-2026-115731 — PUPPET

CRITICAL

CVE-2026-115731 is a critical-severity (CVSS 9.9) Code Injection vulnerability in puppet puppet. A fix is available — see the affected versions and patch details below.

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…

Published
Updated
Affected
2 products
Patched
See advisory
Exploits
None indexed
Exploitation data as of Nov 16, 2026 · OSV.dev, NVD, FIRST.org (EPSS)

Exploitation Status

No confirmed exploitation observed yet

  • A successful exploit gives an attacker total control of the affected component, not partial access.
  • CISA’s own triage has not observed active exploitation or public proof-of-concept code for this CVE as of its last assessment.

Exploitation and automatability from CISA’s SSVC triage for CVE-2026-115731.

EPSS Exploitation Probability

via FIRST.org ↗
0.4%probability of exploitation in next 30 days
Lower Risk0.00%
Lower risk than most CVEs31th percentile — riskier than 31% of all scored CVEsHighest risk

Probability of exploitation in the next 30 days, from FIRST.org EPSS.

How urgent is this, really

Where this sits among everything scored

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

2 products · 5 configurations
Application
puppetpuppet
≥ 9.0.0 && < 9.1.3
range
Application
puppet enterprisepuppet
≥ 2025.0.0 && < 2025.12.1
1 version
2026.0.0

Detection & mitigation playbook

Vendor / appliance
  1. Detect

    Inventory every puppet puppet deployment and check each version against the affected-products list above.

  2. Fix

    Apply the puppet puppet security patch or hotfix for CVE-2026-115731 on the affected version, following the vendor advisory for your exact build.

  3. Workarounds

    Stop passing untrusted input into the interpreter or shell: call the affected binary with an argument array rather than a composed command string, reject anything outside a strict allowlist of expected values, and run the component under an account that cannot reach beyond the work it legitimately does. Alongside that, restrict the management interface to trusted networks and apply the vendor's recommended configuration mitigations.

Fixing This On Your OS

If you run this on a Linux distribution, patch through your package manager against the distro's own security advisory below — it tracks the exact backported fix for your release, which can ship on a different timeline (and sometimes a different severity) than the upstream project.

Red HatCritical

Red Hat has rated this vulnerability as having a Critical impact because successful exploitation enables remote execution of arbitrary commands with the privileges of the Puppet service account, which can compromise the central certificate authority and all downstream managed systems. Within Red Hat Satellite…

Workaround published by Red Hat
Until patched, avoid autosigning certificate requests without strong verification so untrusted clients cannot obtain a CA-signed agent certificate. --- CME Mitigation Guidance (2026-11-04) --- Disclaimer: The following mitigation solutions are provided as a courtesy, pending the application of an official patch. This content was generated utilizing AI tools in conjunction with data from https://cmetaxonomy.org. Customers are advised to independently evaluate and test these temporary mitigations within their own infrastructure. The highest-value action is to enforce safe deserialization allowlists for report event types in FromDataConverter to prevent dynamic class_eval execution: upgrade to…
Source: Red Hat security advisory for CVE-2026-115731 (CC BY 4.0)
ProductFixed inAdvisory
Red Hat Satellite 6.16 for RHEL 8openvox-server-0:8.18.0-1.el8satRHSA-2026:95655
Red Hat Satellite 6.17 for RHEL 9openvox-agent-0:8.32.0-1.el9satRHSA-2026:95656
Red Hat Satellite 6.19 for RHEL 9openvox-server-0:8.18.0-1.el9satRHSA-2026:95652
Satellite Client 6 for RHEL 10openvox-agent-0:8.32.0-1.el10satRHSA-2026:95653

Frequently Asked Questions

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.
O3 Security · Runtime Protection

Is CVE-2026-115731 being exploited in your environment?

Detect and block the exploit chain at execution, on systems you cannot patch yet.

CVE-2026-115731: PUPPET RCE (Critical 9.9, KEV)