CVE-2026-103507
HighCVSS 7.5Summary
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.
Risk Assessment
Arbitrary code execution with the privileges of the P4 Search service account is possible, potentially leading to host compromise. An authentication token is required, but if leaked the impact is critical.
Recommendation
Update Perforce P4 Search to version 2026.4.2 or later. Protect authentication tokens and restrict access to the logging configuration interface.
Other vulnerabilities in Perforce P4 Search
See all- CVE-2026-103512Medium
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-103511Medium
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.
Original NVD description (English source)
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.
Vulnerability data from NVD (NIST) · CISA KEV · EPSS