Skip to content
Connect AISign inSign up free
CVE-2026-1001029.5CriticalCWE-489

CVE-2026-100102: RCE via exposed JDWP debug agent in P4Search

Perforce · P4 (Helix Core)

Vendor fix available · Affected: Perforce P4 (Helix Core) · Exploitation: not established

At a glance

0.4%probability of exploitation in the next 30 days
29th percentile
050100

Higher than 29% of scored CVEs

9.5CriticalCVSS 4.0
LowCrit.

What it isNVD

Perforce P4 Search container images prior to 2026.4.2 enable an unauthenticated Java debug interface. An attacker with network access to this interface can execute arbitrary code as the P4 Search service account, potentially leading to compromise of the connected P4 Server.

ExploitationNot established

Not in CISA KEV as of catalogue 2026.11.18 (18 Nov)

  1. Not establishedNothing in the sources we check

Not seen so far: in CISA KEV · exploited (reported) · scanning observed · proof of concept public.

Weakness and public checks

Public check
No public nuclei template
Weakness
Active Debug Code · Misconfiguration and Insecure Design

Other CVEs in P4 (Helix Core)

Every published CVE for Perforce P4 (Helix Core), by how far exploitation has gone. This one is among them.

As a list
Other CVEs in P4 (Helix Core): each mark is one CVE.Drag to move · Ctrl + scroll to zoom · a mark opens that CVE

Coverage1 article · 1 outlet

First in our coverage: SecurityOnline, 5 Oct.

  1. Perforce P4 Search Flaws Let Attackers Seize Unprotected Services
    SecurityOnline · first in our coverage · mentions it in passing

New articles also arrive in the RSS feed.

References