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