Perforce P4 Search: Authentication bypass via blank service token
Summary
P4 Search before 2026.4.2 does not fail securely when its service authentication token is blank. In affected configurations, an unauthenticated attacker with network access can obtain the highest application privilege. This could lead to compromise of P4 Search and the connected P4 Server.
Affected
- Perforce P4 Search (P4 Helix Core), versions 0 through 2026.4.1
- Affected configurations depend on a blank service token; the exact conditions are unknown.
- Whether the default installation is affected is unknown.
Fixed in
- Upgrade to P4 Search 2026.4.2 or later.
- For container deployments, rebuild from the patched image instead of patching in place (according to a secondary source).
Workaround
- No vendor-documented workaround found.
- Ensure a strong, non-empty service token is set (not vendor-confirmed).
- Restrict network access to the P4 Search port (not vendor-confirmed).
Exploitation
- Not known to be exploited in the wild.
- CISA SSVC: Exploitation none, Automatable no, Technical Impact total.
- A public proof-of-concept listing is unverified.
Our recommendation
- Check whether P4 Search is deployed, which version runs, whether it is containerised and whether it is reachable from untrusted networks.
- Patch to 2026.4.2 as a priority, especially for internet-reachable instances.
- Replace the service token with a strong, unique value and rotate it after the upgrade.
- Review the connected P4 Server for signs of misuse and monitor access logs.
- Check the companion CVEs in the same release (CVE-2026-100103, CVE-2026-100102, CVE-2026-103507).
Public exploits
PoC-in-GitHub, Metasploit and Exploit-DB list nothing for this CVE.
Research sources
- Perforce advisory (CNA record portal) portal.perforce.com
- CVE record (cvelistV5) raw.githubusercontent.com
- SecurityOnline: Perforce P4 Search vulnerabilities securityonline.info
- VulDB: CVE-2026-103510 vuldb.com
- Strix: CVE-2026-103510 www.strix.ai
- Dev.to: P4 Search default service token (CVE-2026-100103) dev.to
- Perforce P4 Search configuration perforce.com
Researched and written up in English and German by an AI (Claude by Anthropic) based on NVD, CISA, EPSS and the sources listed. The vendor information is authoritative. Researched on 30 Oct 2026, 23:33.
Original description (NVD)
P4 Search prior to 2026.4.2 does not fail securely when its service authentication token is blank. In affected configurations, an unauthenticated attacker with network access can obtain the highest application privilege, potentially leading to compromise of P4 Search and the connected P4 Server.
Sources
The tracker combines official, freely usable data sources – updated continuously:
- NVD (NIST) – CVEs, rating (CVSS), affected products
- CISA KEV – vulnerabilities confirmed by CISA as actively exploited
- CISA Vulnrichment – CISA assessment (SSVC) in the official CVE record
- FIRST EPSS – probability of exploitation
- Microsoft MSRC – Patch Tuesday: vulnerabilities, severity, updates
- PoC-in-GitHub – public proof-of-concept repositories
- Metasploit (Rapid7) – modules of the Metasploit Framework
- Exploit-DB (OffSec) – archive of public exploits (links only)
- Patch days: official vendor pages (linked per vendor) (Vendor patch days)
This product uses data from the NVD API but is not endorsed or certified by the NVD. EPSS data © FIRST.org.
Affected? We can help.
We check whether your systems are affected, install updates and close the gap – continuously with the System Health Checker if you wish.