Blog
Puppet Enterprise: critical CVE-2026-115731 under active attack
What CVE-2026-115731 is and who it affectsPerforce Puppet Enterprise, and the underlying Puppet codebase it ships, contain a deserialization of untrus...
What CVE-2026-115731 is and who it affects
Perforce Puppet Enterprise, and the underlying Puppet codebase it ships, contain a deserialization of untrusted data vulnerability tracked as CVE-2026-115731. The flaw sits in Puppet's report-processing code: a client holding any CA-signed agent certificate can submit a report containing a crafted rich-data type through a PUT request and, in doing so, execute arbitrary code on the Puppet Server as the service user.

The dangerous part is the certificate authority. Where it autosigns requests without strong verification, an attacker who has no account at all can obtain a valid certificate and reach the same code path over the network. The NVD classifies the issue under CWE-94 and CWE-502, and scores it CVSS 4.0 9.4 — CRITICAL. It was published on the NVD on 3 November 2026.
Affected releases, as listed by the NVD, are:
- puppet puppet: from 8.0.0 up to, but not including, 8.22.2
- puppet puppet: from 9.0.0 up to, but not including, 9.1.3
- puppet puppet_enterprise: from 2023.8.0 up to, but not including, 2023.8.13
- puppet puppet_enterprise: from 2025.0.0 up to, but not including, 2025.12.1
- puppet puppet_enterprise: 2026.0.0
In practice this concerns any organisation running Puppet to manage its estate — including small and mid-sized companies in Barcelona, Lleida, Tarragona or Girona that use it to keep servers and WordPress, PrestaShop or Joomla hosts in a consistent state. If your configuration management server is internet-facing, the exposure is considerably worse.
Why it is urgent: it is already being exploited
This is not a theoretical risk. CISA added CVE-2026-115731 to its Known Exploited Vulnerabilities (KEV) catalogue on 17 November 2026, which means it has been observed in real attacks. The catalogue entry sets US federal agencies a remediation deadline of 1 December 2026.
CISA's required action is to apply mitigations in line with the vendor's instructions, following its BOD 26-04 guidance on prioritising security updates by risk and its forensics triage requirements. Where mitigations are unavailable — for example in a cloud service — the guidance is to stop using the product. Asset owners are expected to assess each system's internet exposure themselves.
The KEV listing does not state that the vulnerability has been used in ransomware campaigns. That does not make it less pressing: a critical remote code execution flaw on a server that holds credentials and configuration for the whole estate is a high-value target on its own.
What to do today
- Inventory first. Find every Puppet Server and Puppet Enterprise installation you run, and record its exact version. Compare it against the ranges above; a single unpatched instance is enough.
- Apply the vendor's fix. Perforce has published an advisory for this issue. Follow the update or mitigation it specifies for your release line — do not assume a version number; check the advisory itself.
- Review your certificate authority. If autosigning is enabled without strong verification, treat that as a second vulnerability. Tighten or disable it, and audit which certificates have been issued and to whom.
- Look for signs of intrusion. Review Puppet Server logs for unexpected PUT requests and unusual report submissions, and check for processes or files created by the service user that you cannot explain.
- Reduce what is exposed. A Puppet Server has no business being reachable from the open internet. Restrict access to known management networks and review firewall rules and any port forwarding still in place.
Under GDPR, an intrusion that exposes configuration data, credentials or personal information carries notification obligations, so keep a record of what you checked and when.
How a cybersecurity team such as ALMC's can help
Most small IT teams we work with know their web platforms well but treat the configuration management layer as background infrastructure — until something like this lands. Our work starts with the unglamorous part: establishing what you actually run, at which version, and what of it is visible from outside. From there we handle server hardening, patch and update cycles for WordPress, PrestaShop and Joomla alongside the rest of the stack, and continuous monitoring so that an unexpected request or a new service user gets noticed rather than discovered months later.
When an incident has already happened, we carry out forensic triage, clean and repair compromised systems, and close the route the attacker used. Where a client wants proof rather than assumptions, security audits and pentesting show which doors are genuinely locked. The aim is simple: find and close the gaps before someone else does.
Related
- Ivanti Connect Secure: CVE-2026-104935 Under Active Attack
- CVE-2026-96951: Windows Shell Command Injection Under Attack
- Click to Chat for WhatsApp: CVE-2026-92097 in WordPress
- Abuse Shield
Is your business exposed to flaws like this?
ALMC checks which versions you are running, applies the patches and hardens your servers and website. Contact our team for a security review.
