CVE Watchtower

CVE-2026-100103Perfoce P4 (Helix Core)

NVD

Vulnerability Summary

Perforce P4 Search container images prior to 2026.4.2 reset the service authentication token to a publicly documented default value. An unauthenticated attacker with network access can obtain the highest application privilege, potentially leading to arbitrary code execution and compromise of the connected P4 Server.
Severity Level
CRITICAL(10.0)
Published Date
Oct 5, 2026
Last Modified
Oct 5, 2026
Exploitation Status
No confirmed exploitation yet
EPSS Score (30-Day)
0.42%Probability
Root Weakness (CWE)
See the MITRE CWE entry for the full definition of this weakness.
CVSS v4.0 Base Metrics — Score 10.0 (CRITICAL)
CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:H/VI:H/VA:H/SC:H/SI:H/SA:H
Attack VectorNetwork
Attack ComplexityLow
Attack RequirementsNone
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

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

What to do

Plan remediation soon. No exploitation is confirmed yet, but the severity is critical.

  1. Check whether you run Perfoce 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 Perfoce P4 (Helix Core) CVEsYou are reading CVE-2026-100103. Get an email when KEV listings, exploits or new CVEs match your stack.
Set up CVE alerts

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