# CVE-2026-103508: Perforce P4 Search path traversal via logging configuration

Source: https://junglewise.ai/threats/cve-2026-103508-p4-search-formerly-helix-search-allows-an-authenticated-user  
Publisher: Junglewise Threat Intelligence, https://junglewise.ai/threats  
Published: 2026-10-15. Updated: 2026-10-16  
License: CC BY 4.0 with a link back

CVE-2026-103508 · Severity: info · Published 2026-10-15

P4 Search is a search service for Perforce's source control system. An authenticated administrator can supply a malicious logging configuration that writes or deletes files outside the intended directory, potentially allowing the attacker to execute arbitrary code as the P4 Search service account and gain complete control of the search infrastructure.

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

## Quick answers

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

**How severe is CVE-2026-103508?** Informational severity, published 15 October 2026.

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

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

**How is CVE-2026-103508 attacked?** It is attacked over the network, in a hosted service.

**Am I affected by CVE-2026-103508?** 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.3

## Technical details

A path traversal vulnerability in P4 Search's logging configuration allows an authenticated administrative user to manipulate file paths and write or delete arbitrary files on the system running the P4 Search service. The vulnerability requires valid administrative credentials on the connected P4 Server and could lead to code execution with P4 Search service account privileges. The issue has been patched in version 2026.4.3.

## Affected products

- Perforce P4 Search 2026.4.2 and earlier

## Timeline

- 2026-10-15: disclosed

## References

- [https://portal.perforce.com/s/cve/a91Qi000003GdOfIAK/path-traversal-via-logging-configuration-in-p4search](https://portal.perforce.com/s/cve/a91Qi000003GdOfIAK/path-traversal-via-logging-configuration-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 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)
- [Perforce P4 Search arbitrary file write in logging configuration](https://junglewise.ai/threats/cve-2026-103507-perforce-p4-search-prior-to-2026-4-2-does-not-restrict-file)