CVE-2026-103510Authentication bypass via blank auth token in P4Search
Updated under an hour ago ()
Does this affect you?
It affects Perforce P4 (Helix Core). Add what you run to find out whether that includes you.
EPSS puts the chance of exploitation in the next 30 days at 0.35%, higher than 27% of scored CVEs.
Do this next
Free account, 1 product
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.
- CVSS
- 9.5 CRITICAL (v4.0, CNA)CVSS:4.0/AV:N/AC:L/AT:P/PR:N/UI:N/VC:H/VI:H/VA:H/SC:H/SI:H/SA:H
- Weakness (CWE)
- CWE-636
- Known exploited
- Not in CISA's KEV catalog
- EPSS (exploitation in the next 30 days)
- 0.35% (percentile 27)
- Assigned by
- Perforce
- NVD analysis
- Awaiting Analysis
- Record last updated
- Oct 5, 2026
- First seen by InfoSec Signals
- Oct 9, 2026
Affected products
Perforce P4 (Helix Core) perforce:p4_helix_core (from the name) | through 2026.4.1; 2026.4.2 not affected | CNA record |
References
- https://portal.perforce.com/s/cve/a91Qi000003FDw5IAG/authentication-bypass-via-blank-auth-token-in-p4search
The CVE record on cve.org NVD's entry
The CVE record is authoritative. Products marked “from the name” were identified from the CNA's free-text names, not a CPE, and are matched less certainly. This product uses the NVD API but is not endorsed or certified by the NVD.