Skip to content
TrustList
Security advisories

CISA adds Puppet Enterprise flaw CVE-2026-115731 to its exploited vulnerabilities list

Editorial

By TrustList Editorial

CISA added CVE-2026-115731, a deserialization flaw in Puppet report processing that lets an agent certificate holder run code on Puppet Server, to the KEV list on 17 November 2026; fixed in Puppet Enterprise 2026.0.1, 2025.12.1 and 2023.8.13.

About CISA adds Puppet Enterprise flaw CVE-2026-115731 to its exploited vulnerabilities list

CISA adds Puppet Enterprise flaw CVE-2026-115731 to its exploited vulnerabilities list

17 November 2026: The US Cybersecurity and Infrastructure Security Agency (CISA) added CVE-2026-115731, a flaw in Perforce's Puppet Enterprise, to its Known Exploited Vulnerabilities catalogue. A KEV listing means CISA has evidence the flaw is being exploited. US federal civilian agencies must deal with it by 1 December 2026, and the date is a useful benchmark for everyone else.

Not yet independently verified. The fixed versions and the CVSS 4.0 score of 9.4 are from the record Puppet filed as CVE numbering authority, shown on NVD; Perforce's own advisory page would not render for us. CISA lists the flaw as exploited but does not describe the attacks; a press report says Perforce was not aware of attacks when it published the fix on 3 November. Fixed releases for open-source Puppet Core were not confirmed on a primary page. We will update this when it can be confirmed, and remove this note.

The flaw

Puppet is a configuration management system: a central Puppet Server tells managed machines, through their agents, how they should be configured. CISA describes CVE-2026-115731 as a deserialization of untrusted data flaw in Puppet's report-processing code. A client holding any agent certificate signed by the Puppet certificate authority can run arbitrary code on the Puppet Server, as the service user, by sending a report that contains a crafted rich-data type in a PUT request.

The second part matters most. If the certificate authority signs certificate requests automatically without strong verification, which is what autosigning does, an unauthenticated attacker on the network can obtain a valid certificate and then exploit the flaw. A Puppet Server controls the configuration of every machine it manages, so code running on it is a path to the whole estate.

Affected and fixed versions

The CVE record that Puppet filed, published on 3 November 2026, lists Puppet Enterprise 2023.8.0 to before 2023.8.13, 2025.0.0 to before 2025.12.1, and 2026.0.0 to before 2026.0.1 as affected. Versions 2023.8.13, 2025.12.1 and 2026.0.1 are fixed. Puppet scores it 9.4 out of 10 on CVSS 4.0, and NVD's own analysis gives 9.9 on CVSS 3.1, both critical. CISA files it under CWE-502 and CWE-94.

Upgrade, then check certificate signing

Upgrade Puppet Enterprise to 2026.0.1, 2025.12.1 or 2023.8.13, depending on your branch. If you run open-source Puppet or Puppet Core, check Perforce's advisory for the matching release before assuming you are safe.

Until you can upgrade, look at certificate signing. If autosign is turned on, either switch it off or make sure it uses policy-based signing that checks each request properly, for example with a pre-shared secret in the certificate request. Limit which networks can reach the Puppet Server's port.

Because CISA reports exploitation, check for signs of it as well: unexpected certificates signed recently, especially for unknown host names; unusual report submissions in the Puppet Server logs; new processes or files owned by the Puppet service user; and changes to the code or data the server distributes. If you find any, treat the server and the machines it manages as possibly compromised, revoke the suspect certificates and rotate the secrets Puppet holds.

Sources

Categories & features

TrustList Weekly

The week in software and IT, in one email

The news that matters to buyers, new rankings and our own research. Every Thursday, free, and easy to leave.

We will email you to confirm. Unsubscribe with one click in any issue. Privacy policy

You may be interested in

A client with no credentials can tie up memory, file descriptors and backend connections on Traefik 3.7.14 to 3.7.16 and 2.11.58 to 2.11.60, whether or not NTLM is used. It is the latest of more than a dozen fixes since 6 October.