November 15, 2026

CVE Watchtower

CVE-2026-103512Perforce P4 (Helix Core)

NVD

Vulnerability Summary

Perforce P4 Search prior to 2026.4.2 trusts a client-supplied address when validating certain authentication requests. An attacker holding a stolen P4 Server ticket can bypass host-based ticket restrictions and trusted-address controls, gaining access to P4 Search as the ticket's owner.
Severity Level
MEDIUM(5.3)
Published Date
Oct 5, 2026
Last Modified
Oct 5, 2026
Exploitation Status
No confirmed exploitation yet
EPSS Score (30-Day)
0.37%Probability
Root Weakness (CWE)
CWE-290 ↗
See the MITRE CWE entry for the full definition of this weakness.
CVSS v4.0 Base Metrics — Score 5.3 (MEDIUM)
CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:L/VI:L/VA:N/SC:N/SI:N/SA:N
Attack VectorNetwork
Attack ComplexityLow
Attack RequirementsNone
Privileges RequiredLow
User InteractionNone
Confidentiality (Vulnerable System)Low
Integrity (Vulnerable System)Low
Availability (Vulnerable System)None
Confidentiality (Subsequent System)None
Integrity (Subsequent System)None
Availability (Subsequent System)None

Affected & Patched Versions

Affected Versions
  • Perforce P4 (Helix Core) <= 2026.4.1
Patched Versions
  • Perforce P4 (Helix Core) 2026.4.1

What to do

Fix it during your normal patch cycle. No exploitation is confirmed yet.

  1. Check whether you run Perforce P4 (Helix Core) and which version.
  2. 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-103512. Get an email when KEV listings, exploits or new CVEs match your stack.
Set up CVE alerts

Related Coverage

External References

Data last checked: Nov 15, 2026 23:12 UTC