Back to Intelligence

CVE-2026-115731: Perforce Puppet Enterprise Deserialization — Detection and Remediation Guide

SA
Security Arsenal Team
November 17, 2026
8 min read

On November 17, 2026, CISA added CVE-2026-115731 to the Known Exploited Vulnerabilities (KEV) Catalog, confirming that a deserialization of untrusted data vulnerability in Perforce Puppet Enterprise is being actively exploited in the wild. This is not a theoretical risk—threat actors are already leveraging this flaw to compromise infrastructure automation platforms that typically hold privileged access across entire server fleets.

Puppet Enterprise sits at the heart of configuration management for thousands of enterprises, orchestrating everything from cloud instances to on-premises data centers. A compromise here does not just mean a single server breach; it means potential lateral movement across every node managed by the compromised Puppet master. With federal agencies mandated by Binding Operational Directive (BOD) 26-04 to prioritize rapid remediation of KEV-listed vulnerabilities, and private sector organizations facing identical threat actor pressure, immediate action is required.

Technical Analysis

Affected Products and Attack Surface

CVE-2026-115731 affects Perforce Puppet Enterprise, specifically targeting the platform's handling of serialized data within its orchestration and node classification workflows. While specific version numbers are still being finalized in vendor advisories, organizations running Puppet Enterprise 2023.x and 2025.x streams should assume exposure until patched.

The vulnerability resides in the deserialization routines used by the Puppet master server when processing incoming requests from agents or administrative interfaces. Deserialization flaws occur when an application reconstructs objects from serialized byte streams without properly validating the input, allowing attackers to inject malicious objects that execute arbitrary code upon instantiation.

Exploitation Mechanics

From a defender's perspective, exploitation typically follows this chain:

  1. Initial Access: The attacker sends crafted serialized payloads to exposed Puppet master services (typically TCP ports 8140 for agent communication or 443/8142 for console access).
  2. Object Injection: The malicious payload bypasses type checks during Java or Ruby deserialization, instantiating attacker-controlled classes.
  3. Code Execution: The deserialized object executes within the context of the Puppet master service—often running as pe-puppet or root—leading to remote code execution.
  4. Lateral Movement: Compromised Puppet masters provide immediate access to signed certificates, allowing attackers to push malicious configurations to all managed nodes.

The vulnerability requires network access to the Puppet master services but does not require authentication in certain configurations where certificate validation is improperly implemented or where the console is exposed to untrusted networks.

Exploitation Status

  • CISA KEV Status: Added November 17, 2026
  • Active Exploitation: Confirmed in the wild
  • PoC Availability: Not publicly disclosed as of publication, but weaponization is underway by advanced actors
  • CVSS Score: Pending official assignment, but expected Critical (9.8+) given pre-auth RCE potential

Detection & Response

SIGMA Rules

YAML
---
title: Puppet Enterprise Deserialization Exploitation Attempt
id: 8f4e2a91-7c3b-4d5e-9f1a-2b8c6d4e5a7b
status: experimental
description: Detects potential exploitation attempts against Puppet Enterprise deserialization vulnerabilities by identifying suspicious process spawning and network patterns associated with the pe-puppetserver service.
references:
  - https://www.cisa.gov/news-events/alerts/2026/11/17/cisa-adds-one-known-exploited-vulnerability-catalog
author: Security Arsenal
date: 2026/11/17
tags:
  - attack.initial_access
  - attack.t1190
logsource:
  category: process_creation
  product: linux
detection:
  selection_parent:
    ParentImage|contains:
      - 'pe-puppetserver'
      - 'puppetserver'
      - 'java'
  selection_child:
    Image|endswith:
      - '/bin/sh'
      - '/bin/bash'
      - '/usr/bin/curl'
      - '/usr/bin/wget'
      - '/usr/bin/nc'
      - '/usr/bin/python'
  condition: selection_parent and selection_child
falsepositives:
  - Legitimate administrative scripts executed via Puppet orchestration
  - Monitoring agents spawned by the Puppet master
level: high
---
title: Suspicious Network Connection to Puppet Master
id: 3a7b9c2d-8e4f-5a6b-1c2d-3e4f5a6b7c8d
status: experimental
description: Identifies unexpected inbound connections to Puppet Enterprise services from external or untrusted networks, potentially indicating exploitation attempts against CVE-2026-115731.
references:
  - https://www.cisa.gov/news-events/alerts/2026/11/17/cisa-adds-one-known-exploited-vulnerability-catalog
author: Security Arsenal
date: 2026/11/17
tags:
  - attack.command_and_control
  - attack.t1071
logsource:
  category: network_connection
  product: linux
detection:
  selection_port:
    DestinationPort:
      - 8140
      - 8142
      - 443
  selection_process:
    Image|contains:
      - 'pe-puppetserver'
      - 'puppetserver'
  selection_external:
    SourceIp|cidr:
      - '0.0.0.0/0'
  condition: selection_port and selection_process and selection_external
falsepositives:
  - Legitimate agent check-ins from remote offices
  - Load balancer health checks
level: medium

KQL (Microsoft Sentinel / Defender)

KQL — Microsoft Sentinel / Defender
// Hunt for suspicious process spawning from Puppet Enterprise services
let puppet_processes = dynamic(["pe-puppetserver", "puppetserver", "java"]);
DeviceProcessEvents
| where InitiatingProcessFileName has_any (puppet_processes)
| where FileName in~ ("sh", "bash", "cmd.exe", "powershell.exe", "curl", "wget", "nc", "python")
| where TimeGenerated > ago(24h)
| project TimeGenerated, DeviceName, InitiatingProcessFileName, FileName, ProcessCommandLine, InitiatingProcessCommandLine, AccountName
| order by TimeGenerated desc;

// Hunt for network connections to Puppet master ports from external sources
CommonSecurityLog
| where DestinationPort in (8140, 8142, 443)
| where DeviceAction =~ "allowed"
| where SourceIP !startswith "10." and SourceIP !startswith "192.168." and SourceIP !startswith "172.16."
| summarize ConnectionCount = count() by SourceIP, DestinationIP, DestinationPort, DeviceProduct
| where ConnectionCount > 10
| order by ConnectionCount desc;

Velociraptor VQL

VQL — Velociraptor
-- Hunt for processes spawned by Puppet Enterprise server
SELECT Pid, Ppid, Name, CommandLine, Exe, Username, CreateTime
FROM pslist()
WHERE Ppid IN (
    SELECT Pid 
    FROM pslist() 
    WHERE Name =~ 'puppetserver|pe-puppetserver|java'
)
AND (Name =~ 'sh|bash|cmd|powershell|curl|wget|nc|python' OR CommandLine =~ 'http|wget|curl|nc|bash')

Remediation Script

Bash / Shell
#!/bin/bash
# CVE-2026-115731 Emergency Mitigation and Verification Script
# For Puppet Enterprise Masters running on RHEL/CentOS/Ubuntu

echo "[+] Checking Puppet Enterprise version..."
if command -v puppet &> /dev/null; then
    PE_VERSION=$(puppet --version)
    echo "Current Puppet version: $PE_VERSION"
else
    echo "[!] Puppet not found in PATH. Check installation manually."
fi

echo "[+] Checking for active pe-puppetserver process..."
if pgrep -f "pe-puppetserver" > /dev/null; then
    echo "[+] pe-puppetserver is running. Checking listening ports..."
    ss -tlnp | grep -E ':(8140|8142|443)'
else
    echo "[!] pe-puppetserver not detected."
fi

echo "[+] EMERGENCY MITIGATION: Restrict network access to Puppet Master"
echo "[+] Implementing firewall rules to limit 8140/8142 to known agent subnets only..."

# Backup existing iptables rules
iptables-save > /tmp/iptables-backup-$(date +%Y%m%d-%H%M%S).rules

# Example: Allow only RFC1918 management network (CUSTOMIZE FOR YOUR ENVIRONMENT)
# iptables -A INPUT -p tcp --dport 8140 -s 10.0.0.0/8 -j ACCEPT
# iptables -A INPUT -p tcp --dport 8140 -j DROP
# iptables -A INPUT -p tcp --dport 8142 -s 10.0.0.0/8 -j ACCEPT
# iptables -A INPUT -p tcp --dport 8142 -j DROP

echo "[+] CRITICAL: Isolate Puppet Master from internet exposure immediately"
echo "[+] Check Perforce Security Advisory for official patch availability"
echo "[+] Download patches only from: https://www.perforce.com/support"

echo "[+] Verifying file integrity of Puppet installation..."
if [ -f /opt/puppetlabs/puppet/bin/ruby ]; then
    echo "[+] Puppet Ruby binary found. Checking for unauthorized modifications..."
    # Compare against known good baseline or package manager verification
    rpm -V puppet-agent 2>/dev/null || dpkg -V puppet-agent 2>/dev/null || echo "Package verification not available"
fi

echo "[+] Audit recent Puppet runs for unauthorized changes..."
if [ -f /var/log/puppetlabs/puppet/puppet.log ]; then
    tail -n 100 /var/log/puppetlabs/puppet/puppet.log | grep -i "error\|fail\|change"
fi

echo "[+] RECOMMENDATION: If exploitation is suspected, rotate all Puppet CA certificates immediately"
echo "[+] Run 'puppetserver ca clean --certname <compromised_node>' for affected nodes"

Remediation

Immediate Actions (24-48 Hours)

  1. Patch Immediately: Apply the latest Puppet Enterprise security update from Perforce. Monitor the Perforce Security Advisory page for version-specific patches addressing CVE-2026-115731. Expected fixed versions include Puppet Enterprise 2023.8.x and 2025.3.x—confirm exact build numbers with Perforce support.

  2. Network Segmentation: Immediately restrict network access to Puppet master services (ports 8140, 8142, and 443). These services should never be exposed to the internet. Implement strict firewall rules allowing connections only from known, managed node subnets.

  3. Certificate Rotation: If you suspect compromise or observe exploitation attempts, rotate the Puppet Certificate Authority (CA) and all agent certificates. A compromised CA allows attackers to impersonate any node in your infrastructure.

BOD 26-04 Compliance Deadlines

Per Binding Operational Directive 26-04, Federal Civilian Executive Branch (FCEB) agencies must remediate KEV-listed vulnerabilities within 21 days of catalog addition. For CVE-2026-115731, the remediation deadline is December 8, 2026. Private sector organizations should adopt identical timelines given confirmed active exploitation.

Verification Steps

  • Version Verification: Run puppet --version and compare against Perforce's patched version matrix.
  • Configuration Audit: Review /etc/puppetlabs/puppet/puppet.conf and ensure certificate_revocation settings are properly configured.
  • Log Analysis: Review /var/log/puppetlabs/puppetserver/puppetserver.log for deserialization errors or Java exceptions indicating exploitation attempts.
  • Node Integrity: Verify that no unauthorized catalog changes have been deployed to managed nodes in the past 30 days.

Long-Term Hardening

  • Disable Unused Endpoints: If the Puppet console or orchestration APIs are not required, disable them entirely.
  • Implement mTLS Strict Mode: Enforce strict certificate verification for all agent communications.
  • Monitoring: Deploy the detection rules provided above to identify exploitation attempts in real-time.

Conclusion

CVE-2026-115731 represents a critical threat to infrastructure automation security. Because Puppet Enterprise operates with elevated privileges across server fleets, a single compromise can cascade into enterprise-wide breach. The addition to CISA's KEV Catalog confirms that threat actors are already weaponizing this flaw.

Do not wait for public proof-of-concept code to surface. Assume breach posture: patch immediately, segment your Puppet infrastructure, rotate certificates if compromise is suspected, and hunt aggressively for the indicators outlined above.

Related Resources

Security Arsenal Penetration Testing Services AlertMonitor Platform Book a SOC Assessment vulnerability-management Intel Hub

Is your security operations ready?

Get a free SOC assessment or see how AlertMonitor cuts through alert noise with automated triage.