Quick answers
- Is CVE-2026-103512 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-103512 being exploited in the wild.
- How severe is CVE-2026-103512?
- 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-103512?
- 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-103512 attacked?
- It is attacked over the network, in a hosted service.
- Am I affected by CVE-2026-103512?
- 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
P4 Search trusts a client-supplied address when validating authentication requests, failing to properly enforce host-based ticket restrictions and trusted-address controls. An attacker in possession of a valid P4 Server ticket can spoof their client IP address to bypass these restrictions. The vulnerability requires a stolen or compromised ticket but does not require network access from the ticket's legitimate origin.
Affected products
- Perforce P4 Search prior to 2026.4.2
Timeline
- 2026-10-05: disclosed