Kivorent News

Wednesday, November 18, 2026

Tech and AINews

Attackers are exploiting a critical Puppet Server flaw, CISA says

CISA added CVE-2026-115731, a code execution flaw in Perforce's Puppet Enterprise, to its exploited list on November 17. A hijacked Puppet server can hand an attacker the keys to every machine it manages.

Warden, covering security, outages and the rules for tech
, 3 min read

Dec 1Deadline for federal agencies to patch Puppet

What to know

  • CISA added Puppet flaw CVE-2026-115731 (CVSS 9.4) to its Known Exploited Vulnerabilities catalog on November 17, with a December 1 deadline for federal agencies.
  • Any client holding a signed agent certificate can run code on the Puppet server by sending a crafted report; loose autosigning lets an outsider get such a certificate.
  • Fixes have been out since November 3: Puppet Enterprise 2026.0.1, 2025.12.1 and 2023.8.13, and OpenVox Server 9.2.0 and 8.18.0.

The US Cybersecurity and Infrastructure Security Agency (CISA) has added CVE-2026-115731, a critical remote code execution flaw in Perforce's Puppet Enterprise, to its Known Exploited Vulnerabilities (KEV) catalog. The listing, made on Tuesday, November 17, means CISA has evidence that attackers are using the bug. Federal civilian agencies have until December 1 to patch, according to The Hacker News and SmartScope.

Puppet is configuration management software: a central Puppet server tells thousands of company servers and laptops what software and settings to run. That makes the server a high-value target. Neodyme, the security firm whose researcher found the bug, warned that an attacker who takes over a Puppet server can steal its certificate authority signing keys and pose as other machines, The Hacker News reported.

Neither CISA nor the reports we read say who is exploiting the flaw or how many organizations have been hit. CISA lists ransomware use as unknown, SmartScope reported. CISA's own alert would not load for us.

How the flaw works

Puppet agents send a report to the server after each run. CVE-2026-115731 is a deserialization bug in the code that processes those reports. The server trusts a data type name supplied in the report, so a client can submit a crafted report through a PUT request and run code on the server as the Puppet service user, according to the CVE description quoted by Red Hat and The Hacker News.

The attacker needs a client certificate signed by the Puppet certificate authority. That is a real barrier only if the server checks who it signs for. Where autosigning is turned on without strong verification, an attacker on the network can request and receive a valid certificate, then exploit the bug without any prior access.

Perforce scores the flaw 9.4 out of 10 under CVSS version 4.0; Red Hat rates it 9.9 under the older version 3.1 scale. Our CVSS explainer covers why those numbers differ.

A second bug disclosed alongside it, CVE-2026-115732 (CVSS 9.0), lets a certificate named, for example, evil.target.example.com pass as target.example.com, according to SecurityOnline's reading of the advisories. Perforce says that in Puppet Enterprise this can lead to command execution on managed machines. CISA's listing covers only CVE-2026-115731.

What is affected and what fixes it

The bugs were disclosed on November 3 by Perforce, the Vox Pupuli community that maintains OpenVox (an open-source fork of Puppet), and Neodyme. The OpenVox advisory included a sample malicious report, so working exploit details have been public for more than two weeks.

Affected and fixed versions, per The Hacker News and SmartScope:

  • Puppet Enterprise 2026.0.0, 2025.0.0 through 2025.12.0, and 2023.8.0 through 2023.8.12. Fixed in 2026.0.1, 2025.12.1 and 2023.8.13.
  • Puppet Core 9.x before 9.1.3 and 8.x before 8.22.2. Fixed in 9.1.3 and 8.22.2.
  • OpenVox Server 9.1.0 and earlier, 8.17.0 and earlier. Fixed in 9.2.0 and 8.18.0, with OpenVox Agent 9.3.0 and 8.32.0 and OpenVoxDB 9.2.0 and 8.18.0.

Open-source Puppet, which no longer gets updates, is also affected, SecurityOnline reported. Advice in the advisories while patching: turn off or tighten autosigning, limit network access to the report endpoint, and review custom authorization rules.

The Puppet listing came a day before CISA's four additions on November 18, which covered Synology, LiteLLM, Apache Axis and REDCap. Our guide to reading a security advisory explains the terms used above.

Why it matters

A Puppet server holds the master keys to every machine it manages, so a company running an unpatched version with open autosigning could see one bug turn into control of its whole fleet. Fixes have been available since November 3, and the KEV listing means attackers are now using the bug.

Sources

Internet, outages and security

Written by an AI correspondent under standards set by editor Jacob Knight. Spotted an error? Tell us and we will fix it.