# CVE-2026-100102: Perforce P4 Search unauthenticated Java debug interface remote code execution

Source: https://junglewise.ai/threats/cve-2026-100102-perforce-p4-search-container-images-prior-to-2026-4-2-enable-an  
Publisher: Junglewise Threat Intelligence, https://junglewise.ai/threats  
Published: 2026-10-05. Updated: 2026-10-05  
License: CC BY 4.0 with a link back

CVE-2026-100102 · Severity: info · Published 2026-10-05

Perforce P4 Search is a search indexing service for Perforce version control repositories. Container images prior to version 2026.4.2 expose an unauthenticated Java Debug Wire Protocol (JDWP) interface on the network, allowing attackers to execute arbitrary code with the privileges of the P4 Search service account and potentially compromise connected P4 servers.

Technologies: [Perforce P4 Search](https://junglewise.ai/threats/technologies/p4-search). Vendors: [Perforce](https://junglewise.ai/threats/vendors/perforce).

## Quick answers

**Is CVE-2026-100102 exploited in the wild?** No. Junglewise Threat Intelligence has no report of CVE-2026-100102 being exploited in the wild.

**How severe is CVE-2026-100102?** Informational severity, published 5 October 2026.

**Which products and versions are affected?** Perforce P4 Search prior to 2026.4.2.

**Is there a fix for CVE-2026-100102?** Yes: fixed in P4 Search 2026.4.2. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.

**How is CVE-2026-100102 attacked?** It is attacked over the network, in a network appliance.

**Am I affected by CVE-2026-100102?** Check whether you run Perforce P4 Search at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.

## How to fix

- Fixed in P4 Search 2026.4.2

## Technical details

The vulnerability exists in P4 Search container images that expose the Java Debug Wire Protocol (JDWP) debug interface without authentication on a network-accessible port. An attacker with network access to this interface can send JDWP commands to execute arbitrary code as the P4 Search service account, leading to remote code execution. This precondition requires only network connectivity to the debug port with no authentication required.

## Affected products

- Perforce P4 Search prior to 2026.4.2

## Timeline

- 2026-10-05: disclosed

## References

- [https://portal.perforce.com/s/cve/a91Qi000003FE7NIAW/rce-via-exposed-jdwp-debug-agent-in-p4search](https://portal.perforce.com/s/cve/a91Qi000003FE7NIAW/rce-via-exposed-jdwp-debug-agent-in-p4search)

## Related threats

- [P4 Search credential disclosure in configuration API](https://junglewise.ai/threats/cve-2026-103509-p4-search-formerly-helix-search-returns-stored-credentials-in)
- [Perforce P4 Search path traversal via logging configuration](https://junglewise.ai/threats/cve-2026-103508-p4-search-formerly-helix-search-allows-an-authenticated-user)
- [Perforce P4 Search ticket validation bypass in client IP handling](https://junglewise.ai/threats/cve-2026-103512-perforce-p4-search-prior-to-2026-4-2-trusts-a-client-supplied)
- [Perforce P4 Search arbitrary file write in extension installation](https://junglewise.ai/threats/cve-2026-103511-perforce-p4-search-prior-to-2026-4-2-does-not-validate-file)
- [Perforce P4 Search authentication bypass via blank auth token](https://junglewise.ai/threats/cve-2026-103510-p4-search-prior-to-2026-4-2-does-not-fail-securely-when-its)