CISA Says a Critical Puppet Enterprise Flaw Is Being Exploited, and Autosigned Certificates Make It Easier
CVE-2026-115731 lets any holder of a Puppet CA certificate run code on the Puppet Server, and CISA has listed it as exploited. Affected Puppet Enterprise versions, the fixed releases, why autosigning matters and what to check tonight.

In this article
Table of Contents
Table of contents
CISA added CVE-2026-115731, a critical flaw in the server side of Perforce Puppet Enterprise, to its Known Exploited Vulnerabilities catalogue on Tuesday 17 November. The CVE record, filed by Puppet’s own security team, says that any client holding a certificate signed by the Puppet certificate authority can run code on the Puppet Server, as the server’s service user, by sending it a crafted report. It adds that where the certificate authority autosigns requests without strong checks, an unauthenticated attacker on the network can obtain such a certificate first. The record was published on Tuesday 3 November and names fixed releases; CISA’s due date for US federal agencies is Tuesday 1 December.
#What the record actually says
The weakness is a deserialisation flaw (the record lists CWE-502) in the code that processes the reports agents send back to the server after each run. A report can carry what the record calls a “rich-data type”. Hand the server a crafted one in an HTTPThe KBY LexiconHTTPHTTP is a stateless application-level protocol for request and response messages. Safe validation requires a bounded target and both protocol and application evidence. PUT request and it runs the attacker’s code as its service user. The only precondition is a certificate signed by the Puppet CA, which every legitimate agent holds.
That precondition is why the second half of the record matters. Puppet agents join a deployment by asking the CA to sign a certificate request. Some sites sign each request by hand. Others turn on autosigning so that new servers and virtual machines can enrol without anyone clicking anything. The record says that where autosigning lacks strong verification, no existing credential is needed at all: someone who can reach the server over the network can ask for a certificate, receive it and use it.
Perforce’s own severity score is 9.4 out of 10 under CVSS 4.0. NIST’s National Vulnerability Database scores it 9.9 under CVSS 3.1. Either way it sits at the top of the scale. CISA’s catalogue entry describes the same behaviour and carries the required action to apply mitigations following the vendor’s instructions. It lists known ransomware campaign use as “Unknown”, and neither the entry nor the record says who is exploiting the flaw or what they do after they get in.
#Which releases are hit and which are fixed
The record’s affected list names Puppet Enterprise only:
- 2023.8.0 up to, but not including, 2023.8.13: fixed in 2023.8.13
- 2025.0.0 up to, but not including, 2025.12.1: fixed in 2025.12.1
- 2026.0.0 up to, but not including, 2026.0.1: fixed in 2026.0.1
A second flaw published at the same moment is worth knowing about. CVE-2026-115732 is an authorisation bypass in how Puppet Server matches certificate names. A client whose certificate name extends or shortens an authorised hostname can be treated as that host, which the record says allows impersonation of other nodes and, in Puppet Enterprise, access to certificate authority administration and remote command execution on managed nodes. Perforce scores it 9.0 under CVSS 4.0. It affects the same three version ranges and is fixed by the same three releases, so one upgrade closes both. It also needs a certificate the CA has issued, by approval or autosign. As of the CISA catalogue published at 17:53 UTC on Tuesday, it is not in the exploited list.
One gap needs a straight answer. The record’s description says the flaw is in “Puppet, as used by Puppet Server”, but its list of affected products names only Puppet Enterprise. We have not seen a vendor statement on whether open-source Puppet Server builds, or forks that share the code, are affected. If you run one of those, ask whoever supplies it rather than assuming either way.
#Why autosigning is the setting to look at first
Puppet’s own documentation has been blunt about this for a long time. Of the basic autosign.conf allowlist it says: “Because any host can provide any certname when requesting a certificate, basic autosigning is insecure.” It tells administrators to use it “only when you fully trust any computer capable of connecting to the primary server”. Of the alternative, policy-based autosigning, where the CA runs a script of your choosing on each request, it says security depends entirely on what the script checks. A script that verifies a pre-shared key or looks the machine up in your cloud account can be solid; one that approves anything with a plausible name is not.
The documentation also describes the off switch: setting autosign = false in the [server] section of the CA primary server’s puppet.conf disables CA autosigning even if an allowlist file or a policy script exists. An empty or missing autosign.conf means nothing is signed automatically.
Our reading is that this turns a version question into two separate questions with different urgency. If your CA signs everything automatically, you are exposed to anyone who can reach the server’s agent port, and you should treat the server as the priority patch of the week. If signing is manual or governed by a strict policy script, an attacker first needs a certificate you issued or one that slipped through, so the practical risk is lower. It is not zero: any compromised managed machine already holds a valid certificate.
#Why we rate this above the usual critical server bug
A configuration managementThe KBY LexiconConfiguration ManagementConfiguration Management defines, applies and audits the intended state of infrastructure and software, detecting drift and providing a traceable record of configuration change. server is not an ordinary application server. Its whole job is to tell every machine it manages what state to be in, and in most deployments those machines apply the instructions with full privileges. Code running as the Puppet Server’s service user is therefore not one compromised host, it is a position from which an attacker could try to change what hundreds or thousands of hosts do next. That is our reading of how Puppet is normally deployed, not something the record states, and the record itself stops at code execution on the server. We do not know what the attackers CISA is watching do with that foothold.
It is also an uncomfortable shape of bug for defenders, because the front door is the mechanism the product depends on. Agents have to be able to reach the server and present a certificate, so you cannot simply block the port, and a firewall rule that is too broad takes your own fleet offline. The realistic defence is narrower: patch, close autosigning, and make sure only the networks your agents live on can reach the server at all.
The timing deserves a note too. The record was published on 3 November and the exploited listing arrived two weeks later. We do not know when exploitation began, and CISA does not say. Anyone who held off patching on the grounds that a certificate was needed should read the autosigning point above again.
#What to do tonight and tomorrow morning
- Find every Puppet Enterprise primary server and any compilers, and note the version your console reports. Anything inside the three affected ranges above needs upgrading to 2023.8.13, 2025.12.1 or 2026.0.1, whichever matches your release line.
- On the CA server, check how signing is configured. Run
puppet config print autosignand look at whether the answer is a file path, an executable or false. If it is a basic allowlist full of wildcards, or a script that approves on name alone, treat that as the finding. - If you can enrol new machines by hand or by a controlled process for a while, set autosign to false until the upgrade is done. Where you cannot, restrict the server’s agent port to the address ranges your agents actually use.
- List the certificates the CA has signed, with
puppetserver ca list --all, and look for certnames nobody recognises, names that look like variations of real hosts, and anything signed since the record appeared on 3 November. Revoke what should not be there. - Look in the Puppet Server logs for report submissions, which the record says are HTTP PUT requests, from certnames you do not recognise or at unusual times. If you find any, treat the server as compromised and follow your incident process rather than patching over it.
- Diary the follow-up: confirm CVE-2026-115732 is closed by the same upgrade, and re-read the CISA entry on Friday in case Perforce or CISA add detail.
We have not been able to load Perforce’s own advisory page, which needs a full browser session, so everything above is drawn from the CVE record Perforce’s security team filed, CISA’s catalogue and Puppet’s documentation. Where Perforce’s advisory gives a more specific mitigation than the ones here, follow Perforce.
#What we do not know yet
CISA’s listing says exploitation has happened. It does not say how many organisations, in which countries, or whether the attackers needed to obtain certificates through autosigning or already held them. The record does not name any exploitation technique beyond the one it describes. We do not know whether open-source builds are affected, and we have not confirmed whether public exploit code exists. We will update this story if Perforce, CISA or a security researcher publishes any of those details, or if CVE-2026-115732 joins the exploited list.
Evidence trail
Sources and verification
Primary documentation and external technical references used in this article.
- 01NVD record for CVE-2026-115731 (filed by Puppet's security team)services.nvd.nist.gov
- 02NVD record for CVE-2026-115732services.nvd.nist.gov
- 03CISA Known Exploited Vulnerabilities catalogue (JSON feed)cisa.gov
- 04Puppet documentation: autosign.conf, basic certificate autosigninghelp.puppet.com
- 05Puppet documentation: policy-based autosigninghelp.puppet.com
About this page
Credited to
Dates
Published
Corrections
No corrections are listed for this page. Some review sweeps corrected pages without naming each one; those are in the corrections log.
Read-only scripts
- Windows devices with no BitLocker recovery key in Entra IDMicrosoft Entra ID, Windows
- Intune devices that haven't synced in N daysMicrosoft Intune
- Mailboxes forwarding to external addressesExchange Online
- BitLocker status of every volume on this PCWindows
Upcoming deadlines
- Intune moves to macOS 15 and laterQ4 2026
- SAP SuccessFactors provisioning: move from basic auth to workload identityNovember 2026
- Intune November release: JIT registration reminder at APNs renewal and automatic JIT for eligible tenantsNovember 2026
Explore KBY
The KBY Brief
A short email about twice a week with new runbooks, configuration traps and fixes from KBY Technologies.
SubscribeMore news
All newsWas this useful?
Reports go to the site owner and are used to correct pages. Corrections are listed at /corrections.
Get new fixes by email.
New runbooks, configuration traps and fixes from KBY Technologies, about twice a week.




Comments
Add a thoughtful note on CISA Says a Critical Puppet Enterprise Flaw Is Being Exploited, and Autosigned Certificates Make It Easier. Comments are checked for spam and held for moderation before appearing.