Skip to navigation

Threat reportVulnerabilityTL-2026-6290

CISA KEV Addition: Perforce Puppet Enterprise Report-Processing Deserialization RCE (CVE-2026-115731)

criticalACTIVE

CVE-2026-115731 is a deserialization-of-untrusted-data flaw in Puppet's report-processing code (Puppet Server / Puppet Enterprise, and the OpenVox fork) that lets a client holding a CA-signed agent certificate run arbitrary code on the server as the puppet user. CISA added it to the Known Exploited Vulnerabilities Catalog on 2026-11-17 based on evidence of active exploitation. First disclosed .

Key facts

IdentifiersTL-2026-6290, CVE-2026-115731, CVE-2026-115732
Also known asGHSA-ffr6-rwpm-p5wq, Puppet Server report deserialization RCE
SeverityCRITICAL
CVSS9.9 (CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:H/I:H/A:H)
First disclosed
Affected productsPerforce Puppet Enterprise; Vox Pupuli OpenVox Server; Vox Pupuli OpenVox Agent
Weaknesses (CWE)CWE-502, CWE-863, CWE-94
MalwareRuby
MITRE ATT&CK techniquesT1059 Command and Scripting Interpreter, T1059.004 Command and Scripting Interpreter: Unix Shell, T1072 Software Deployment Tools, T1078 Valid Accounts, T1190 Exploit Public-Facing Application, T1550 Use Alternate Authentication Material, T1552.001 Unsecured Credentials: Credentials In Files, T1552.004 Unsecured Credentials: Private Keys, T1565.001 Data Manipulation: Stored Data Manipulation, T1649 Steal or Forge Authentication Certificates
MotivationUNKNOWN
Target sectorsinformation technology
Detection rules9 (1 shown free)
Sources10 cited sources

Detection coverage

As of 2026-11-18, Threadlinqs Intelligence publishes 9 detection rule(s) for TL-2026-6290 across Splunk SPL, Microsoft KQL and Sigma, covering 20 indicator(s) of compromise. The whole corpus is readable without an account. Every threat comes with one complete detection in Splunk SPL, Microsoft KQL and Sigma, free for everyone; a free account adds daily TL Creds to unlock the rest. Paid plans add a larger daily allowance, correlation and the MCP server. Threadlinqs MCP server · View plans.

Free detection: Shell Child Process of Puppet Server JVM Running as puppet User — Post-Exploitation

Detects a shell (sh, bash, dash, zsh, ksh) spawned by the Puppet Server / OpenVox Server Java process under the puppet service account. In CVE-2026-115731 the attacker-controlled RubyMethod body runs a backtick shell command via class_eval, so a shell child of puppetserver is the primary post-exploitation artifact.

  • Languages: Splunk SPL, Microsoft KQL, Sigma
  • ATT&CK: T1059.004, T1059, T1190
  • Data sources: Sysmon for Linux (index=linux sourcetype=sysmon:linux EventCode=1), DeviceProcessEvents, process_creation linux
  • Severity: critical
  • Confidence: high

Splunk SPL

index=linux sourcetype="sysmon:linux" EventCode=1 User="puppet" ParentImage="*/java" (ParentCommandLine="*puppetserver*" OR ParentCommandLine="*openvox-server*") (Image="*/sh" OR Image="*/bash" OR Image="*/dash" OR Image="*/zsh" OR Image="*/ksh") earliest=-24h
| stats count, min(_time) AS first_seen, values(CommandLine) AS commands, values(ParentCommandLine) AS parent_cmd BY host, User, Image
| convert ctime(first_seen)

Microsoft KQL

DeviceProcessEvents
| where Timestamp > ago(24h)
| where InitiatingProcessAccountName =~ 'puppet'
| where InitiatingProcessFileName =~ 'java' and InitiatingProcessCommandLine has_any ('puppetserver', 'openvox-server', 'puppet-server')
| where FileName in~ ('sh', 'bash', 'dash', 'zsh', 'ksh')
| project Timestamp, DeviceName, AccountName, FileName, ProcessCommandLine, InitiatingProcessCommandLine, InitiatingProcessParentFileName

Sigma

title: Shell Spawned by Puppet Server JVM as puppet User
id: 2d9f4a61-8c37-4b0e-a5d2-91e6b7c3f840
status: experimental
description: Detects a shell launched as a child of the Puppet Server or OpenVox Server Java process running as the puppet user, the post-exploitation artifact of CVE-2026-115731 report deserialization RCE.
references:
    - https://github.com/OpenVoxProject/openvox/security/advisories/GHSA-ffr6-rwpm-p5wq
    - https://www.cve.org/CVERecord?id=CVE-2026-115731
author: Threadlinqs Team
date: 2026/11/18
tags:
    - attack.execution
    - attack.t1059.004
    - attack.initial-access
    - attack.t1190
    - cve.2026.115731
logsource:
    category: process_creation
    product: linux
detection:
    selection_parent:
        ParentImage|endswith: '/java'
        ParentCommandLine|contains:
            - 'puppetserver'
            - 'openvox-server'
    selection_user:
        User: 'puppet'
    selection_child:
        Image|endswith:
            - '/sh'
            - '/bash'
            - '/dash'
            - '/zsh'
            - '/ksh'
    condition: selection_parent and selection_user and selection_child
falsepositives:
    - Custom Puppet Server hooks or scripts that deliberately shell out from the JVM
level: critical

Known false positives:

  • Custom Puppet Server extensions or hooks that intentionally invoke shell scripts from the JVM
  • Administrators debugging the service under the puppet account with an interactive shell

Tuning notes: Requires process telemetry with parent command line on the Puppet Server host (Sysmon for Linux, auditd with execve parent enrichment, or EDR). If your build runs the service under a different account, change the User value. Baseline for a week and exclude exact known hook command lines rather than excluding the parent process.

8 more detection rules (Splunk SPL, Microsoft KQL, Sigma) · unlock with TL Creds. Sign up free to unlock the detection rules or query them with the Threadlinqs MCP server (Purple)
  • Puppet Server Log Deserialization Artifacts (Pops Serialization / [indicator]) — Exploitation · unlock with TL Creds
  • Reconnaissance and Persistence Commands Run as puppet Service User — Post-Exploitation · unlock with TL Creds
  • Puppet Server Host Egress and Orchestration Abuse from puppet User — C2 and Lateral Movement · unlock with TL Creds
  • Puppet CA Autosign Activity Enabling Unauthenticated Exploit Chain — Exploitation · unlock with TL Creds
  • Download-and-Execute or Reverse Shell Command Lines Run as puppet User — Post-Exploitation · unlock with TL Creds
  • Puppet Orchestration Abuse and CA-Key Certificate Forging — Lateral Movement · unlock with TL Creds
  • Puppet Server Report Endpoint Deserialization Exploit (CVE-2026-115731) — Exploitation · unlock with TL Creds
  • Puppet CA Private Key Access by Non-JVM Process — Credential Theft and Certificate Forgery · unlock with TL Creds

Indicators of compromise

As of 2026-11-18, Threadlinqs Intelligence tracks 20 indicators of compromise for TL-2026-6290.

20 indicators of compromise · unlock with TL Creds. Compare plans

Technical analysis

CVE-2026-115731 (published by Perforce via CVE.org on 2026-11-03) is a deserialization of untrusted data (CWE-502) in the report-processing code used by Puppet Server, including Perforce Puppet Enterprise. An agent that holds a CA-signed certificate can submit a crafted rich-data report via PUT /puppet/v3/report and obtain code execution on the server as the service user (puppet). The related OpenVox advisory GHSA-ffr6-rwpm-p5wq (reporter: alain-neodyme, published by binford2k on 2026-11-03) documents the root cause: agent-supplied JSON events flow into Puppet::Pops::Serialization::FromDataConverter.convert, where the attacker-controlled __ptype value is parsed by Types::TypeParser and .create(value) is called on the resulting type. This reaches RubyGenerator.new.create_class, where class_eval executes attacker-controlled Ruby.

The advisory's high-level PoC structure is a normal-looking report JSON containing a resource_statuses entry for a Notify resource whose events array holds an object with a __ptype field carrying a serialized Puppet Object type definition. That definition includes a function with a RubyMethod annotation whose Ruby body uses backticks, so the shell command runs during compile/evaluation rather than at parse time. A __pvalue field holds a benign value. Secondary reporting (securityonline.info, dailysecurityreview.com) states a working malicious report that runs a shell command is public in the OpenVox advisory; the working command string was not reproduced in the sources reviewed here.

Authentication prerequisite is a valid CA-signed agent certificate (CVSS Privileges Required: Low). Where the CA autosigns requests without strong verification, an unauthenticated network attacker may obtain such a certificate through the client enrollment path, making the chain effectively unauthenticated. Code execution as the puppet user exposes the CA signing key, which per the advisory could let an attacker issue certificates with serverAuth and clientAuth EKUs and potentially run commands on other hosts in some orchestration setups. dailysecurityreview.com adds that forged certificates can remain valid after patching unless operators rotate trust material (single-source claim).

Severity is reported inconsistently: Red Hat and NVD list CVSS 3.1 9.9 (CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:H/I:H/A:H); CVE.org/secondary sources list CVSS 4.0 9.4 (the OpenVox vector is CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:H/VI:H/VA:H/SC:H/SI:H/SA:H). The CISA alert states the addition is based on evidence of active exploitation but gives no exploitation details, actor, or IOCs; securityonline.info notes its body said no in-the-wild exploitation of 115731 was confirmed at publication on 2026-11-04, while its sidebar lists the KEV addition. Disclosed alongside it was CVE-2026-115732 (CVSS 9.0), a certificate-name authorization bypass in trapperkeeper-authorization (GHSA-q4hm-33rc-572g) allowing node impersonation; securityonline.info reports, citing a Reddit thread (unverified), that this companion bug is exploited in the wild. No threat actor, malware, or network infrastructure has been publicly attributed, so no BeaconBeagle correlation was applicable (no network IOCs exist).

MITRE ATT&CK techniques by tactic:

Execution

T1059 Command and Scripting Interpreter; T1059.004 Command and Scripting Interpreter: Unix Shell

Lateral Movement

T1072 Software Deployment Tools; T1550 Use Alternate Authentication Material

Initial Access

T1078 Valid Accounts; T1190 Exploit Public-Facing Application

Credential Access

T1552.001 Unsecured Credentials: Credentials In Files; T1552.004 Unsecured Credentials: Private Keys; T1649 Steal or Forge Authentication Certificates

Impact

T1565.001 Data Manipulation: Stored Data Manipulation

Remediation

Patches

  • Puppet Enterprise 2023.8.13, 2025.12.1, 2026.0.1
  • OpenVox Server 9.2.0 / 8.18.0
  • OpenVox Agent 9.3.0 / 8.32.0
  • OpenVoxDB 9.2.0 / 8.18.0 (including container image)

Immediate actions

  • Upgrade Puppet Enterprise to 2023.8.13, 2025.12.1 or 2026.0.1 (or later) per Perforce guidance
  • Disable CA autosigning or require strong verification of certificate signing requests so untrusted clients cannot obtain a CA-signed agent certificate
  • Restrict network access to the Puppet Server / report endpoint (PUT /puppet/v3/report) to required agent networks only
  • Review Puppet Server logs for unusual report submissions from agents and for child shell processes spawned by the puppet service user

Workarounds

  • Avoid autosigning certificate requests without strong verification (official Red Hat/Perforce-derived guidance)
  • Restrict access to the report endpoint and limit server exposure to necessary networks if upgrade is not possible

Longer-term hardening

  • Rotate CA and issued trust material where compromise of the Puppet Server is suspected, since forged certificates may stay valid after patching
  • After upgrading, review custom auth.conf rules, as some may have relied on the previously buggy hostname-matching behavior
  • Monitor Puppet Server hosts with EDR/auditd/Falco-style telemetry as a compensating control

Affected and fixed versions

  • Perforce — Puppet Enterprise
    Vulnerable versions: versions prior to 2023.8.13; versions prior to 2025.12.1; versions prior to 2026.0.1
    Fixed in: 2023.8.13; 2025.12.1; 2026.0.1
  • Vox Pupuli — OpenVox Server
    Vulnerable versions: 9.1.0 and below; 8.17.0 and below
    Fixed in: 9.2.0; 8.18.0
  • Vox Pupuli — OpenVox Agent
    Vulnerable versions: 9.2.0 and below; 8.31.1 and below
    Fixed in: 9.3.0; 8.32.0

Timeline

Last updated · 2 updates · revalidated 2× · latest source

  • Perforce also releases fixed Puppet Core versions 9.1.3 and 8.22.2 for CVE-2026-115731 and CVE-2026-115732.
  • Fixed releases available: Puppet Enterprise 2023.8.13, 2025.12.1, 2026.0.1; OpenVox Server 9.2.0/8.18.0; OpenVox Agent 9.3.0/8.32.0. Companion CVE-2026-115732 (CVSS 9.0) disclosed and fixed in the same releases.
  • OpenVox publishes critical advisory GHSA-ffr6-rwpm-p5wq (CVSS 4.0 9.4) describing PUT /puppet/v3/report event deserialization leading to class_eval code execution, including PoC report structure; an oss-security post is also dated this day.
  • Perforce publishes CVE-2026-115731 via CVE.org; Vox Pupuli, Perforce and Neodyme (reporter alain-neodyme) coordinate public disclosure.
  • Unverified Reddit user report of an intrusion traced to CVE-2026-115731 in a fleet with a severely misconfigured CA; post URL slug references CVE-2026-115732, so the report is ambiguous.
  • Secondary reporting (securityonline.info, dailysecurityreview.com) states a working malicious report is public in the OpenVox advisory; Red Hat publishes CVE page (CVSS 3.1 9.9, CWE-502) with interim mitigation guidance. No confirmed in-the-wild exploitation stated at that time.
  • A secondary tracker lists CVE-2026-115732 as confirmed exploited from this date; not independently verified and not confirmed in KEV.
  • SmartScope publishes analysis of the Puppet Server/OpenVox flaws citing CVE.org, OpenVox advisories and JPCERT/CC.
  • CISA adds CVE-2026-115731 (Perforce Puppet Enterprise Deserialization of Untrusted Data) to the KEV Catalog based on evidence of active exploitation; BOD 26-04 prioritization applies to FCEB agencies.
  • SecurityWeek reports the critical Perforce Puppet RCE is being exploited in attacks; notes CISA KEV federal due date of 2026-12-01 and no named threat actor.
  • The Hacker News reports active exploitation of the Puppet flaw; no details on weaponization, actors or IOCs.
  • Remediation deadline for US FCEB agencies under CISA BOD 26-04.

Update history

Sources cited

Previous and next in vulnerability

Drafted by the Threadlinqs research pipeline from 10 sources; published ; last updated .

Threadlinqs Intelligence — Real-Time Threat Detection Platform

// threat_feed
$ sort --newest
Showing all threats

Live intelligence console

Threat level

Latest Threats