Cybersecurity 3 min read

CISA Lists Exploited Puppet Enterprise Flaw That Lets Any Signed Agent Run Code on the Server

The US Cybersecurity and Infrastructure Security Agency listed the flaw on 17 November, two weeks after Perforce fixed it. Servers whose certificate authority autosigns requests face the most risk.

Priya Nair
Data, AI Governance & Policy Analyst
Published 18 Nov 2026, 2:17 PM (SGT)
Share:
A technician working on cabling at a network equipment rack A technician working on cabling at a network equipment rack Photo by RodDIYguy on Pixabay
Advertisement

18 NOV 2026 — The US Cybersecurity and Infrastructure Security Agency (CISA) has added a code-execution flaw in Perforce's Puppet Enterprise to its known exploited vulnerabilities catalogue. CVE-2026-115731 went in on 17 November, the only addition that day, taking the list to 1,782.

Perforce's advisory traces the bug to how Puppet deserialises the reports that agents send to Puppet Server. A client holding any agent certificate signed by the Puppet certificate authority can submit a report carrying "a crafted rich-data type" in a PUT request and run code of its choosing on the server, with the rights of the account the service runs under. Perforce rates it critical, at 9.4 on CVSS 4.0. The NVD record adds its own CVSS 3.1 score of 9.9.

Exposure hinges on that certificate requirement. An attacker normally needs a signed agent certificate. If a certificate authority signs requests automatically, without checking them properly, Perforce warns, an attacker with no credentials at all can get one, and CISA's entry says that attacker can then "exploit the vulnerability".

3 NovResolution date in Perforce's advisory; NVD record published the same day
17 NovAdded to CISA's exploited list, 14 days later
1 DecDue date for US federal civilian agencies, another 14 days on
UnknownCISA's answer on use in ransomware campaigns

Perforce fixed the flaw on 3 November. CISA listed it 14 days later, and the federal deadline falls another 14 days after that. That leaves 28 days between the fixed releases and the deadline, and 14 of them had passed before CISA said the flaw was being exploited.

Advertisement

Perforce fixes this in Puppet Enterprise 2026.0.1, 2025.12.1 and 2023.8.13, and in Puppet Core 9.1.3 and 8.22.2. Every earlier release in those lines is affected, back to 2026.0.0, 2025.0.0 and 2023.8.0 for Puppet Enterprise, and to 9.0.0 and the whole 8.x series for Puppet Core. CISA and the NVD name only Puppet Enterprise, but Perforce's own list also covers Puppet Core.

The deadline binds only US federal civilian agencies. The directive behind it, BOD 26-04, does not extend to contractors unless their contracts say so. For other organisations, the listing is a signal. CISA's instruction is to apply the vendor's mitigations or stop using the product if none are available.

CISA confirms only that the flaw is exploited. Its entry does not say who is behind the attacks, which organisations have been hit or how many, and its field for ransomware use reads "Unknown". Neither the advisory nor the NVD record, as read on 18 November, describes any attack. Readers who want to see how the 9.9 is built can enter the NVD vector, "CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:H/I:H/A:H", into our CVSS calculator.

Advertisement
Priya Nair
Data, AI Governance & Policy Analyst

Priya Nair covers AI governance, data protection, privacy, and digital trust topics for RECATOOLS.

View author profile → · Editorial policy

About this byline Priya Nair is a RECATOOLS editorial persona for AI governance, privacy, and digital trust coverage. Articles are produced and reviewed under RECATOOLS editorial supervision.

Corrections policy

Advertisement