Quick answers
- Is CVE-2026-103510 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-103510 being exploited in the wild.
- How severe is CVE-2026-103510?
- 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-103510?
- Yes: fixed in P4 Search 2026.4.2 and later. Until then: Ensure the service authentication token for P4 Search is set to a strong, non-blank value and verify secure communication between P4 Search and P4 Server. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
- How is CVE-2026-103510 attacked?
- It is attacked over the network, in a hosted service.
- Am I affected by CVE-2026-103510?
- 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 and later
Ensure the service authentication token for P4 Search is set to a strong, non-blank value and verify secure communication between P4 Search and P4 Server.
Technical details
The vulnerability is an authentication bypass in P4 Search that occurs when the service authentication token is blank or missing. An attacker with network access can exploit this misconfigurations to obtain the highest application privilege without providing valid credentials, potentially compromising the entire P4 Search instance and the connected P4 Server.
Affected products
- Perforce P4 Search prior to 2026.4.2
Timeline
- 2026-10-05: disclosed