A client holding any CA-signed agent certificate can submit a crafted report and execute code on the server as its service user. CISA added the flaw to its Known Exploited Vulnerabilities catalog on 17 November 2026.The certificate is an important access condition. CISA says an attacker without one can obtain a certificate when the CA autosigns requests without strong verification. Puppet says its November 2026 Enterprise releases fix the server code-execution path. See the vulnerability intelligence platform for related product context.
What it allows
How Does CVE-2026-115731 Reach Code Execution?
The vulnerable report-processing code deserializes untrusted rich-data content. A holder of any CA-signed agent certificate can submit a crafted report that reaches the Puppet Server. CISA and the Puppet CNA record say the resulting code runs as the server's service user. This is remote code execution on the management server, not merely on an agent.
Certificate issuance controls change the exposure. When a CA automatically signs requests without strong verification, CISA says a network attacker without prior authentication can obtain a usable certificate. Audit autosign rules and certificate issuance as part of the response. Treat a certificate that was issued unexpectedly as an investigation lead, even after patching.
What Does the Exploitation Record Establish?
CISA listed CVE-2026-115731 in KEV on 17 November 2026, establishing known exploitation. Its catalog labels ransomware campaign use as unknown. The listing does not identify an actor, affected organization, or incident count. It gives US federal agencies a remediation due date of 1 December 2026.
Brandefense Blackhole counted one dark-chat post mentioning this CVE from 19 August through 17 November 2026. The unit is a post mentioning the identifier, not an exploited server or confirmed incident. The count is an internal discussion signal and is separate from CISA's exploitation finding.
Who is affected
Which Puppet Enterprise Releases Are Affected?
NVD lists Puppet Enterprise 2023.8.0 through versions before 2023.8.13, and 2025.0.0 through versions before 2025.12.1, as affected. It also lists 2026.0.0. Puppet identifies 2023.8.13, 2025.12.1, and 2026.0.1 as the corresponding November 2026 security releases. Check the version of each self-managed Puppet Enterprise Server and record its branch before upgrading.
NVD also lists the Puppet package from 8.0.0 to before 8.22.2 and from 9.0.0 to before 9.1.3. Those Puppet package ranges do not replace the Enterprise Server release check. The exposed service is the Puppet Server that processes agent reports, provided a client has a valid CA-signed agent certificate. Weakly verified autosign increases the reachable attacker population.
Prioritize servers that accept reports from less trusted network segments. Use the patch management process to track the server upgrade and follow-up checks.
Timeline
-
2026-11-03
NVD published the CVE record supplied by Puppet's CNA.
-
2026-11-17
CISA added CVE-2026-115731 to its Known Exploited Vulnerabilities catalog.
What to do
-
Inventory Puppet Servers
Identify each self-managed Puppet Enterprise Server, its installed release, network exposure, and the CA that signs its agents. Prioritize the affected branches listed by NVD.
-
Upgrade the affected branch
Apply Puppet Enterprise 2023.8.13, 2025.12.1, or 2026.0.1 for the matching branch. Follow Puppet's release guidance. After restart, run `puppetserver -v` on each Puppet Server host and compare its output with Puppet's component-version table for the target Enterprise release.
-
Review certificate issuance
Inspect CA autosign configuration and recent agent certificate approvals. Require strong verification before signing new requests and investigate certificates issued unexpectedly.
-
Investigate possible server execution
Review Puppet Server report activity and service-user process activity around suspicious submissions. Preserve relevant server and CA logs, then scope any confirmed compromise.
What Brandefense can do
- Watch your stack for exploited flaws
Name the vendors and products you run, and Brandefense alerts you when a CVE in them is exploited.
- See CVE-2026-115731 in Brandefense Atlas
The Atlas record of CVE-2026-115731: severity, exploitation status and the sources behind it.
- Vulnerability intelligence platform
Brandefense Vulnerability Intelligence follows which vulnerabilities attackers are using, so your team can patch what is under attack first.
Frequently Asked Questions
Does CVE-2026-115731 require an agent certificate?
Yes. CISA says a client needs any CA-signed agent certificate. Weakly verified autosign can let a network attacker obtain one without prior authentication.
Which Puppet Enterprise versions fix CVE-2026-115731?
Puppet lists 2023.8.13, 2025.12.1, and 2026.0.1 as the November 2026 security releases. Upgrade within the matching branch and verify the running server version.
Is CVE-2026-115731 known to be exploited?
Yes. CISA added it to KEV on 17 November 2026. CISA marks ransomware campaign use as unknown and does not name an actor in the entry.