CISA flags active exploitation of a deserialization flaw in Puppet Enterprise
CISA has added a deserialization of untrusted data vulnerability in Perforce Puppet Enterprise to its Known Exploited Vulnerabilities catalogue, citing evidence of active exploitation. Organisations running the configuration management platform are concerned, with US federal civilian agencies bound to prioritise remediation.
What to do now
- Product
- Perforce Puppet Enterprise
- Affected versions
- —
- CVE
- CVE-2026-115731
On 17 November 2026 the US Cybersecurity and Infrastructure Security Agency (CISA) added CVE-2026-115731 to its Known Exploited Vulnerabilities (KEV) catalogue. The flaw affects Perforce Puppet Enterprise and is classed as deserialization of untrusted data. A KEV listing means CISA has evidence the vulnerability is already being used by attackers.
Puppet Enterprise automates the configuration and deployment of servers and endpoints, so it typically holds broad privileges over the infrastructure it manages. That makes a compromise of the platform especially consequential. CISA's notice does not state which versions are affected, whether a fix has been released, or how the flaw is being exploited.
The alert points to Binding Operational Directive 26-04, which requires US federal civilian agencies to fix KEV-listed vulnerabilities first when they sit on publicly exposed assets and allow full takeover after exploitation. The directive also sets expectations for checking whether a system was compromised before the patch went in.
Although the directive only binds federal agencies, CISA urges every organisation to take a risk-based approach and prioritise KEV entries. Puppet Enterprise administrators should turn to Perforce's own security guidance for affected versions and remediation details.
What to do now
- Identify every Puppet Enterprise instance in your environment, starting with any reachable from the internet.
- Check Perforce's security advisory for CVE-2026-115731 and apply the recommended update or mitigation as soon as it is available.
- Meanwhile, restrict network access to Puppet Enterprise servers to the systems and administrators that need it, as general good practice.
- Review Puppet Enterprise server logs and activity for signs of compromise that may predate remediation.