CVE-2026-103510Perforce P4 (Helix Core)
NVD
Vulnerability Summary
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 v4.0 Base Metrics — Score 9.5 (CRITICAL)
CVSS:4.0/AV:N/AC:L/AT:P/PR:N/UI:N/VC:H/VI:H/VA:H/SC:H/SI:H/SA:HAttack VectorNetwork
Attack ComplexityLow
Attack RequirementsPresent
Privileges RequiredNone
User InteractionNone
Confidentiality (Vulnerable System)High
Integrity (Vulnerable System)High
Availability (Vulnerable System)High
Confidentiality (Subsequent System)High
Integrity (Subsequent System)High
Availability (Subsequent System)High
Affected & Patched Versions
- Perforce P4 (Helix Core) <= 2026.4.1
- Perforce P4 (Helix Core) 2026.4.1
What to do
Plan remediation soon. No exploitation is confirmed yet, but the severity is critical.
- Check whether you run Perforce P4 (Helix Core) and which version.
- Update to a patched version listed above, then confirm the new version.
Timeline
- Oct 5, 2026Published
- Oct 5, 2026Record last modified
Score, severity and exploitation changes are tracked from the day Watchtower started logging them.
Get notified about new Perforce P4 (Helix Core) CVEsYou are reading CVE-2026-103510. Get an email when KEV listings, exploits or new CVEs match your stack.
Set up CVE alertsRelated Coverage
External References
Data last checked: Nov 15, 2026 23:12 UTC