Vulnerabilidades do Perforce P4 (Helix Core)

CVE-2026-103509 Alta · 8.5 CWE-1220 15/10/2026

Credential Disclosure in P4 Search Configuration API

P4 Search (formerly Helix Search) returns stored credentials in cleartext through its configuration API to users with administrative privileges on the connected P4 Server, allowing privilege escalation. This affects 2026.4.2 and earlier and is fixed in 2026.4.3.

CVE-2026-103508 Alta · 7.3 CWE-23 15/10/2026

Path traversal via logging configuration in P4Search

P4 Search (formerly Helix Search) allows an authenticated user holding administrative privileges on the connected P4 Server to supply a crafted logging configuration that causes files to be written or deleted outside the intended logging directory. This could lead to code execution as the P4 Search service account. This issue affects P4 Search 2026.4.2 and earlier. Perforce resolved it in 2026.4.3.

CVE-2026-103512 Média · 5.3 CWE-290 05/10/2026

Ticket host-binding bypass via spoofed client IP in P4Search

Perforce P4 Search prior to 2026.4.2 trusts a client-supplied address when validating certain authentication requests. An attacker holding a stolen P4 Server ticket can bypass host-based ticket restrictions and trusted-address controls, gaining access to P4 Search as the ticket's owner.

CVE-2026-103511 Média · 5.1 CWE-73 05/10/2026

Arbitrary file-write via extension installation in P4Search

Perforce P4 Search prior to 2026.4.2 does not validate file names supplied to its extension installation feature. An attacker with super-user or service-token privileges can write files with arbitrary content to the P4 Search installation directory.

CVE-2026-103510 Crítica · 9.5 CWE-636 05/10/2026

Authentication bypass via blank auth token in P4Search

P4 Search prior to 2026.4.2 does not fail securely when its service authentication token is blank. In affected configurations, an unauthenticated attacker with network access can obtain the highest application privilege, potentially leading to compromise of P4 Search and the connected P4 Server.

CVE-2026-103507 Alta · 7.5 CWE-73 05/10/2026

Arbitrary file-write via log configuration path in P4Search

Perforce P4 Search prior to 2026.4.2 does not restrict file paths written through its logging configuration interface. An attacker holding the service authentication token can write arbitrary files on the host, potentially leading to code execution as the P4 Search service account.

CVE-2026-100102 Crítica · 9.5 CWE-489 05/10/2026

RCE via exposed JDWP debug agent in P4Search

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.

CVE-2026-6902 Alta · 7.7 CWE-94 18/05/2026

Code Injection in Perforce P4 (Helix Core)

A Remote Code Execution vulnerability in P4 (Helix Core) Server's Command-Line Client, prior to the 2025.2 Patch 2, has been fixed to address potential security risks.