Security alerts · November 18, 2026

Critical Puppet Server flaw exploited in attacks lets agent certificate holders run code

On November 3, 2026, Perforce fixed critical flaw CVE-2026-115731 in Puppet Enterprise and Puppet Core, and OpenVox is affected too. Anyone holding any signed agent certificate can run code on the Puppet Server. CISA confirms active exploitation, so patch as soon as possible.

What happened

Perforce, the company behind the Puppet configuration management platform, released fixes on November 3, 2026 for a critical vulnerability tracked as CVE-2026-115731. The bug sits in the part of Puppet Server that processes reports sent in by managed machines. It was published in the NVD database the same day.

The US agency CISA added the flaw to its Known Exploited Vulnerabilities (KEV) catalog on November 17, 2026. The European vulnerability database EUVD, run by ENISA, also lists it as exploited since November 17, 2026, under EUVD-2026-116495. According to The Hacker News, there are no public details yet on how attackers are using it. The outlet quotes a Reddit user who wrote on November 4 that they traced an intrusion through this flaw after finding a severely misconfigured certificate authority in their fleet.

The flaw was found by Alain Rödel of the German security firm Neodyme AG. Rödel also reported a second critical bug, CVE-2026-115732, which lets attackers bypass authorization based on certificate names. Neodyme says AI assistance helped uncover the issues. OpenVox, an open-source implementation of Puppet, is affected as well.

Why it is dangerous

This is a deserialization of untrusted data flaw. When programs send data over a network, they “pack” it into a transferable format and “unpack” it back into objects on the other side. If a server unpacks whatever a client sends, it is like a mailroom that opens every parcel and automatically carries out any instructions it finds inside. An attacker can therefore slip content into a report that makes the Puppet Server run their code.

According to NVD, the attacker only needs any agent certificate signed by the Puppet certificate authority. The code then runs on the Puppet Server under its service account. If the certificate authority signs requests automatically without strong verification, an attacker can obtain a certificate without logging in at all, network access to the server is enough.

Neodyme notes that the impact depends on the server configuration and on which orchestration protocols are enabled. Regardless of configuration, though, an attacker can grab the certificate authority’s signing keys and impersonate other machines. Because Puppet often has full access to a company’s entire fleet, Neodyme warns of ransomware deployment, mass data theft and attackers moving further into the network.

NVD rates the flaw CVSS 9.9 on a 0 to 10 scale, which is critical: the attack works over the network, is easy to carry out and needs only low privileges. The CISA KEV catalog lists flaws CISA knows are being exploited, and use in ransomware campaigns is currently marked as unknown. EPSS estimates the chance of exploitation in the next 30 days, and as of November 18, 2026 it stands at 0.69%, higher than roughly 54% of all flaws. A low EPSS is no reason to relax here, since CISA has already confirmed exploitation.

Who is affected

The following versions are affected:

  • Puppet Enterprise 2026.0.0 before 2026.0.1
  • Puppet Enterprise 2025.0.0 before 2025.12.1
  • Puppet Enterprise 2023.8.0 before 2023.8.13
  • Puppet Core 9.0.0 before 9.1.3
  • Puppet Core 8.x before 8.22.2
  • OpenVox: fixed only in OpenVox Agent 9.3.0 and 8.32.0 and OpenVox Server 9.2.0 and 8.18.0

Puppet is mainly used by companies and organizations that manage larger numbers of servers or workstations automatically. A central Puppet Server pushes configuration to agents on the managed machines. It usually runs on the internal network, but is sometimes reachable from the internet, for example for branch offices or cloud servers. Installations with automatic certificate signing are most at risk.

Organizations that use neither Puppet nor OpenVox are not affected. The Hacker News does not list older community (open-source) Puppet releases. If you still run them, treat them as at risk and check their status in the vendor bulletin.

How to check if you are affected

On the Puppet Server, use these commands to find the version. They only read information and change nothing.

puppetserver --version
puppet --version

On Puppet Enterprise, the version is also stored in /opt/puppetlabs/server/pe_version and shown in the Puppet Enterprise console.

cat /opt/puppetlabs/server/pe_version

To list installed Puppet and OpenVox packages:

rpm -qa | grep -Ei 'puppet|openvox'    # RHEL, Rocky, Alma
dpkg -l | grep -Ei 'puppet|openvox'   # Debian, Ubuntu

Also check whether automatic certificate signing is enabled. A value of false means it is off. A value of true means the server signs every request, which is the riskiest setting. A file path means signing is decided by an allowlist of names in that file, or by a script. If the file does not exist, nothing is signed automatically. The second command prints the file if it exists. Pay special attention to wildcard entries such as *.example.com.

puppet config print autosign --section server
f=$(puppet config print autosign --section server); [ -f "$f" ] && ls -l "$f" && cat "$f"

How to fix it

Perforce released fixes on November 3, 2026. Update to one of these versions:

  • Puppet Enterprise 2026.0.1 (includes Puppet Core 9.1.3)
  • Puppet Enterprise 2025.12.1 (includes Puppet Core 8.22.2)
  • Puppet Enterprise 2023.8.13 (includes Puppet Core 8.22.2)
  • Puppet Core 9.1.3 or 8.22.2
  • OpenVox Agent 9.3.0 or 8.32.0, OpenVox Server 9.2.0 or 8.18.0

Recommended order:

  • Inventory every Puppet Server, including compilers and replicas.
  • Immediately restrict network access to the Puppet Server (port 8140 by default) to known managed machines and block it from the internet.
  • If you use automatic signing without strong verification, turn it off for now and approve certificate requests manually.
  • Back up the server, including the certificate authority, and upgrade Puppet Server following the vendor’s procedure.
  • Then update the agents on managed machines where a fixed version is available.
  • Finally, check for signs of compromise as described in the next section, since the flaw is already being exploited.

Detailed steps and any interim mitigations are in the Perforce bulletin at https://portal.perforce.com/s/cve/a91Qi000003IaHpIAK/report-deserialization-code-execution. Check the status of the second flaw, CVE-2026-115732, with the vendor, or with the OpenVox project if you run OpenVox. CISA requires applying mitigations per the vendor’s instructions, or discontinuing the product if none are available. US federal agencies must do so by December 1, 2026, which is a sensible deadline for everyone else too.

What if you may already be compromised

Because the flaw is being exploited, patching alone is not enough. Neither CISA nor The Hacker News lists specific indicators of compromise yet, so focus on these areas:

  • The list of signed certificates: machine names you do not recognize, or certificates signed at unusual times.
  • The Puppet Server access log: reports from unknown certificates or IP addresses. Regular reports from your own agents are normal.
  • Processes, files and scheduled jobs belonging to the Puppet Server service account that should not be there, and unusual outbound connections from the server.
  • Unexpected changes to Puppet code and configuration that could spread to managed machines.
puppetserver ca list --all
cat /etc/puppetlabs/puppetserver/ca/inventory.txt
zgrep -h 'PUT /puppet/v3/report/' /var/log/puppetlabs/puppetserver/puppetserver-access* | awk '{print $1, $7}' | cut -d'?' -f1 | sort | uniq -c
ps -fu puppet    # on Puppet Enterprise: ps -fu pe-puppet

The second command prints the certificate authority inventory with each certificate’s validity period, which also shows roughly when it was issued. The third command summarizes reports from the current and archived access logs by IP address and machine name. Look for names and addresses you do not recognize.

If anything looks suspicious, bring in an incident response specialist. According to Neodyme, an attacker may have taken the certificate authority’s signing keys, which can mean building a new CA and reissuing certificates to every machine. Check the managed servers too, since Puppet often has full access to them.

Sources

Articles are put together by an AI agent from public sources (vendors, CISA, ENISA, NVD, SK-CERT, NÚKIB), and version numbers and CVEs are checked against them automatically. Always confirm the steps in the vendor advisory before touching production.

← All alerts · RSS

Need help patching or checking your systems?

I can help you find out which systems are affected, update them safely and check whether an attacker already got in. Let us start with an initial consultation, which is deducted from the project price if we work together.