Science & Tech · Cybersecurity · 10 hrs ago
CISA Flags Critical Puppet Server Flaw After Reports of Exploitation
CISA added a critical Perforce Puppet flaw to its Known Exploited Vulnerabilities list on November 17, citing reports of attacks.
Puppet is a tool organizations use to manage software and settings across their computer systems.
The flaw, CVE-2026-115731, can let a client with a Puppet-authority-signed certificate run code on a Puppet server by sending a malicious report.
If attackers gain control of the server, they could access its certificate-signing key and affect systems it manages.
Reports of exploitation conflict with Perforce’s account: some sources describe attacks, but Perforce says it is unaware of exploitation and has found no evidence of customer data being accessed.
Perforce released fixes on November 3, and organizations are advised to update or turn off automatic certificate signing unless requests are strongly verified.
Federal agencies must fix the flaw by December 1, 2026; the flaw also affects OpenVox, which has its own fixed versions.
CISA added the critical Puppet Enterprise vulnerability CVE-2026-115731 to its Known Exploited Vulnerabilities catalog, citing reports of active exploitation.
The flaw can let an attacker with a Puppet CA-signed agent certificate execute arbitrary code on a Puppet Server.
If a certificate authority signs requests without strong verification, a network attacker may be able to obtain a valid certificate without prior authentication.
Perforce released fixes on November 3, 2026, and federal agencies have until December 1, 2026, to apply them.
The articles differ on exploitation: The Hacker News reports CISA cited active exploitation, while Security Affairs says there are no reports confirming it and Perforce is unaware of attacks.
- Who
- CISA added the vulnerability to its catalog; the flaw affects Perforce Puppet Enterprise and Puppet Server.
- What
- CVE-2026-115731 is a critical deserialization flaw that can enable remote code execution.
- When
- CISA added it on November 18, 2026, according to the articles.
- Where
- The flaw affects Puppet Server; the articles do not state where exploitation occurred.
- Why
- CISA cited reports of active exploitation and added the flaw to its Known Exploited Vulnerabilities catalog.
Reports of active exploitation
Perforce's stated position
Exploitation status
Reports of active exploitation
CISA cited reports of active exploitation, according to The Hacker News.
Perforce's stated position
Perforce said it was not aware of attacks exploiting the flaw, according to Security Affairs.
Evidence
Reports of active exploitation
A Reddit user said they traced actions back to an intrusion involving the vulnerability.
Perforce's stated position
Security Affairs reported there were no reports confirming active exploitation and no evidence of customer data being accessed.
Perforce released security updates addressing the vulnerability.
A Reddit user said the vulnerability was being exploited shortly after public disclosure.
CISA added CVE-2026-115731 to its Known Exploited Vulnerabilities catalog.
Federal agencies are due to apply fixes for the vulnerability.
- CVE
- CVE-2026-115731
- CVSS score
- 9.4
- Affected component
- Puppet Server
- Fix release date
- November 3, 2026
- Federal agency deadline
- December 1, 2026
3 sources
What people are saying
Perforce Puppet Enterprise contains a deserialization of untrusted data vulnerability in Puppet's report-processing code that allows a client with any CA-signed agent certificate to execute arbitrary code on the Puppet Server as the service user by submitting a report containing a crafted rich-data type through a PUT request
Independent of the configuration, an attacker with RCE on a Puppet server can grab the CA signing keys and impersonate other hosts.
Remote Code Execution on such a central and important system can lead to worst-case scenarios: Deployment of ransomware, mass data exfiltration, and potentially lateral movement to other parts of the network.
After finding a severely misconfigured CA in my fleet, I traced the actions backwards on a [CVE-2026-]115731 intrusion