enzosoler.comreviews 09bench 9 deviceslive test Can a ring and a watch replace my Apple Watch?
Published

Puppet Server flaw CVE-2026-115731 is now exploited. Patch it and check how your CA signs certificates

Blue network cables plugged into a patch panel in a server rack
Image: Brett Sayles / Pexels

CISA added Puppet Server flaw CVE-2026-115731 (CVSS 9.4) to its exploited list on November 17. Any machine with a CA-signed agent certificate can run code on the server and take the CA signing keys. Fixes shipped November 3: Puppet Enterprise 2026.0.1, 2025.12.1 and 2023.8.13, Puppet Core 9.1.3 and 8.22.2, and OpenVox Server 9.2.0 and 8.18.0.

If your company manages servers with Puppet or OpenVox, update the Puppet Server today. CISA added CVE-2026-115731 to its Known Exploited Vulnerabilities catalog on November 17, based on evidence of active exploitation. Fixed versions have been out since November 3. Puppet pushes configuration to every machine it manages, so a compromised Puppet Server can reach every one of them.

What is affected and what fixes it

CVE-2026-115731 is rated CVSS 9.4. It is a deserialization flaw in how Puppet Server processes agent reports. CISA says it lets a client with any CA-signed agent certificate run arbitrary code on the server. Researcher Alain Rödel of Neodyme found it, and Neodyme’s write-up says an attacker with code execution can take the CA signing keys and impersonate other hosts.

Product Affected Fixed
Puppet Enterprise 2026 2026.0.0 2026.0.1
Puppet Enterprise 2025 2025.0.0 up to 2025.12.0 2025.12.1
Puppet Enterprise 2023 LTS 2023.8.0 up to 2023.8.12 2023.8.13
Puppet Core 9 9.0.0 up to 9.1.2 9.1.3
Puppet Core 8 8.x before 8.22.2 8.22.2
OpenVox Server earlier 9.x and 8.x 9.2.0 and 8.18.0

OpenVox, the community fork of Puppet, also ships fixed agents (9.3.0 and 8.32.0), per its GitHub advisory. Version details are from The Hacker News, which links each vendor advisory.

A second flaw fixed in the same releases, CVE-2026-115732 (CVSS 9.0), lets one node pass itself off as another through a certificate-name check. Perforce has a separate advisory for it.

Auto-signing turns this into an outside attack

The flaw needs a signed agent certificate, which sounds like an insider problem. CISA’s note is the part to act on: if your certificate authority signs requests without strong checks, an unauthenticated attacker on the network can get a valid certificate and then exploit the server. Many fleets turn on auto-signing to make new machines join without a human step. That setting is the open door here.

What to do this week:

  • Upgrade Puppet Server, Puppet Enterprise or OpenVox Server to the fixed version for your branch.
  • Check autosign in your Puppet configuration. Turn it off, or limit it to a policy script that verifies each request.
  • Review the signed certificates on your CA for hosts you don’t recognize.
  • If the server was exposed and unpatched, treat the CA keys as possibly stolen and plan to reissue certificates.

US federal civilian agencies must patch by December 1. A Reddit user reported on November 4 that they traced an intrusion in their fleet to this flaw after finding a badly misconfigured CA, according to The Hacker News. No vendor or firm has published how the in-the-wild attacks work.

Neodyme says it found the bugs with AI assistance. Google warned this month that AI tools now turn published patches into working exploits within days. Here the first report of an attack came one day after the fix shipped. Other server flaws to patch this month: Java4Shell in OpenJDK, Ivanti Connect Secure and Check Point’s PHP2Shell hotfix.

Primary source: CISA KEV alert, November 17, 2026.

Related, November 18: nginx 1.31.9 and 1.30.7 fix 10 security flaws. Update your web servers this week.

One email when a review goes up. Unsubscribe from any of them.