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.
Metrics
Affected Vendors & Products
Advisories
No advisories yet.
Fixes
Solution
No solution given by the vendor.
Workaround
No workaround given by the vendor.
References
History
Mon, 05 Oct 2026 09:00:00 +0000
| Type | Values Removed | Values Added |
|---|---|---|
| Description | 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. | |
| Title | Arbitrary file-write via log configuration path in P4Search | |
| Weaknesses | CWE-73 | |
| References |
| |
| Metrics |
cvssV4_0
|
Projects
Sign in to view the affected projects.
Status: PUBLISHED
Assigner: Perforce
Published:
Updated: 2026-10-05T08:31:12.818Z
Reserved: 2026-09-30T17:38:12.196Z
Link: CVE-2026-103507
No data.
Status : Received
Published: 2026-10-05T09:17:06.843
Modified: 2026-10-05T09:17:06.843
Link: CVE-2026-103507
No data.
OpenCVE Enrichment
Updated: 2026-10-05T10:30:18Z
Weaknesses