RCE via exposed JDWP debug agent in P4Search
Default status is the baseline for the product, each version can override it (e.g. patched versions marked unaffected).
| Vendor | Product | Default status | Versions | |||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|
| Perforce | P4 (Helix Core) | affected |
|
No data.
No data.
| Vendor | Product | Versions | ||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| Perforce | Helix Core |
|
No CVSS v3.1
No CVSS v3.0
No CVSS v2
This CVE is not in the KEV list.
Exploit prediction score: < 1% (0.357% probability within 30 days)
| Type | Values Removed | Values Added |
|---|---|---|
| First Time appeared |
Perforce
Perforce helix Core |
|
| Vendors & Products |
Perforce
Perforce helix Core |
| Type | Values Removed | Values Added |
|---|---|---|
| Metrics |
ssvc
|
| Type | Values Removed | Values Added |
|---|---|---|
| Description | 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. | |
| Title | RCE via exposed JDWP debug agent in P4Search | |
| Weaknesses | CWE-489 | |
| References |
| |
| Metrics |
cvssV4_0
|