# CVE-2026-103511: Perforce P4 Search arbitrary file write in extension installation

Source: https://junglewise.ai/threats/cve-2026-103511-perforce-p4-search-prior-to-2026-4-2-does-not-validate-file  
Publisher: Junglewise Threat Intelligence, https://junglewise.ai/threats  
Published: 2026-10-05. Updated: 2026-10-05  
License: CC BY 4.0 with a link back

CVE-2026-103511 · Severity: info · Published 2026-10-05

Perforce P4 Search is a code search tool used to index and retrieve source code across repositories. Attackers with administrative privileges can write arbitrary files to the P4 Search installation directory by supplying malicious file names during extension installation, potentially leading to code execution or system compromise.

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

## Quick answers

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

**How severe is CVE-2026-103511?** Informational severity, published 5 October 2026.

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

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

**How is CVE-2026-103511 attacked?** It is attacked with local access.

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

## Technical details

The vulnerability exists in P4 Search's extension installation feature, which fails to properly validate file names. An attacker with super-user or service-token privileges can exploit this to write files with arbitrary content to the installation directory. This is a path traversal or file write vulnerability requiring elevated privileges.

## Affected products

- Perforce P4 Search prior to 2026.4.2

## Timeline

- 2026-10-05: disclosed

## References

- [https://portal.perforce.com/s/cve/a91Qi000003FDpdIAG/arbitrary-filewrite-via-extension-installation-in-p4search](https://portal.perforce.com/s/cve/a91Qi000003FDpdIAG/arbitrary-filewrite-via-extension-installation-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 path traversal via logging configuration](https://junglewise.ai/threats/cve-2026-103508-p4-search-formerly-helix-search-allows-an-authenticated-user)
- [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 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)