CVE-2026-103507: Arbitrary file-write via log configuration path in P4Search

Published Oct 5, 2026
·
Updated

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.

Affected Software

1 affected component
Perforce P4 Search<2026.4.2

Remediation

Recommended actions to resolve this vulnerability, in priority order.

  1. Upgrade

    Upgrade Perforce P4 Search to a version that resolves this vulnerability.

    Fixed in 2026.4.2

Event History

Oct 5, 2026
CVE Published
via MITRE·08:31 AM
Data Sourced
via MITRE·08:31 AM
DescriptionWeakness

Frequently Asked Questions

1

Who can exploit this issue?

An attacker needs the P4 Search service authentication token. The available information does not indicate that unauthenticated users can exploit it.

2

What systems are affected?

Perforce P4 Search versions prior to 2026.4.2 are affected. Exploitation can write arbitrary files on the P4 Search host.

3

What is the potential impact of successful exploitation?

An attacker may be able to write arbitrary files as the P4 Search service account. This could potentially be used to achieve code execution with that account's privileges.

Contact

SecAlerts Pty Ltd.
132 Wickham Terrace
Fortitude Valley,
QLD 4006, Australia
info@secalerts.co
By using SecAlerts services, you agree to our services end-user license agreement. This website is safeguarded by reCAPTCHA and governed by the Google Privacy Policy and Terms of Service. All names, logos, and brands of products are owned by their respective owners, and any usage of these names, logos, and brands for identification purposes only does not imply endorsement. If you possess any content that requires removal, please get in touch with us.
© 2026 SecAlerts Pty Ltd.
ABN: 70 645 966 203, ACN: 645 966 203