CISA added a critical Puppet flaw, CVE-2026-115731, to its Known Exploited Vulnerabilities (KEV) catalog on Nov. 17, saying it has evidence of active exploitation. The bug lets a client with a valid agent certificate run code on the Puppet server, which often controls a whole fleet of machines. Fixes have been available since Nov. 3.
What happened
Researchers at Neodyme found the flaw while preparing for a red team engagement and reported it to Perforce, which sells Puppet Enterprise, and to OpenVox, a community fork. Fixes and advisories were published together on Nov. 3. CISA’s Nov. 17 alert adds the bug to KEV and sets a Dec. 1 remediation deadline for U.S. federal civilian agencies. The catalog lists known ransomware use as “Unknown”.
The weakness sits in how the server handles reports that agents send after each run. According to the OpenVox advisory, the server rebuilds report events from JSON and trusts a type description supplied by the client. A crafted description makes the server generate and evaluate Ruby code, which then runs as the puppet service user. The advisory rates it critical, at 9.4 on the CVSS 4.0 scale, and includes a proof of concept, so exploit details are public.
Neodyme says the same technique worked against an open-source release from July 2021, so the problem is not limited to recent versions. It also reported a companion bug, CVE-2026-115732, in a hostname check that can let a certificate named like a longer variant of a trusted host impersonate that host.
Why it matters
The attack formally needs a client certificate signed by the Puppet certificate authority (CA). But both the OpenVox advisory and Neodyme note that many large deployments use autosign, where new hosts are enrolled automatically. In that setup, an attacker who can reach the server may be able to obtain a certificate and then send the malicious report, making the chain effectively unauthenticated.
Code execution on the server also exposes the CA signing key, according to the advisory. Neodyme demonstrated in a lab that a stolen key can be used to mint certificates and, where Puppet Enterprise’s orchestration feature is enabled, run commands on managed hosts. It adds that hardened environments reduce the direct impact.
What to do
- Upgrade. For OpenVox, the advisory lists fixed releases: Server 9.2.0 or 8.18.0, and Agent 9.3.0 or 8.32.0. For Puppet Enterprise, a Ciphers Security report lists 2023.8.13, 2025.12.1 and 2026.0.1 as fixed builds; confirm the exact version against Perforce’s advisory.
- Review autosign. Check whether your CA signs requests automatically. If so, tighten it or restrict who can reach port 8140 until you are patched (our analysis).
- Audit certificates. Look for unexpected agent certificates, including odd hostnames that extend a real host’s name (our analysis).
- Hunt for signs of abuse. A Puppet server process launching shells or download tools is not normal behavior and deserves investigation (our analysis).
- If you find compromise, treat the CA key as exposed and plan to rotate it, since it signs trust for the whole fleet (our analysis, based on the advisory’s description of the impact).
What we still do not know
CISA’s alert does not say who is exploiting the flaw, how many organizations are affected, or whether attacks involve autosign. We have not seen published indicators of compromise, and no victim has been named. We also could not open Perforce’s own advisory page, so the Puppet Enterprise version numbers above come from secondary reporting.
Sources: CISA alert, Nov. 17, 2026; CISA KEV catalog entry, added Nov. 17, 2026; OpenVox advisory GHSA-ffr6-rwpm-p5wq, Nov. 3, 2026; Neodyme research write-up, Nov. 3, 2026; Ciphers Security, Nov. 18, 2026.
Leave a Reply