CVE-2026-100103

Authentication bypass via default auth token in P4Search

Published Oct 5, 2026 CVSS 4.0 · 10 Critical EPSS < 1% KEV · Not listed
Description
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.

Analysis

AI-generated

Technical impact

Perforce P4 Search container images before version 2026.4.2 reset their service authentication token to a publicly documented default value. With this default token, an unauthenticated attacker can obtain the highest application privilege, enabling arbitrary code execution and full compromise of the connected P4 Server. The weakness is a default credential issue, allowing a privileged session to be started without authentication.

Affected Systems

The vulnerability affects Perfoce P4 (Helix Core) P4 Search container images released prior to 2026.4.2. No specific minor or patch sub‑versions are listed beyond the 2026.4.2 threshold, so all earlier releases are impacted. Users deploying earlier P4 Search containers should verify the image tag against the release date.

Risk and Exploitability

The CVSS score of 10 indicates maximum severity. EPSS data is not available, so exploitation probability cannot be quantified at present, but the lack of a requirement for privileged network positioning combined with the simplicity of the default token gives a high likelihood to attackers with network access. The vulnerability is not listed in the CISA KEV catalog. An attacker can exploit this by simply sending a request to the P4 Search service over the network, authenticating with the default token, and then performing privileged actions as the service administrator.

Remediation

No solution or workaround provided in the CVE record.

OpenCVE Recommended Actions

  • Deploy a P4 Search image with version 2026.4.2 or later, which removes the default authentication token behavior.
  • If an upgrade is not immediately possible, restrict network access to the P4 Search service so that only trusted hosts or internal networks can reach it, mitigating unauthorized external access.
  • Configure a firewall rule or reverse proxy to require valid authentication before allowing any requests to the P4 Search API, thereby preventing use of the default token.

Generated by OpenCVE AI on October 5, 2026 at 10:51 UTC.

Tracking

Sign in to view the affected projects.

Advisories

No advisories available
History
Type Values Removed Values Added
First Time appeared Perforce
Perforce helix Core
Vendors & Products Perforce
Perforce helix Core
Type Values Removed Values Added
Metrics ssvc

{'options': {'Automatable': 'no', 'Exploitation': 'none', 'Technical Impact': 'total'}, 'version': '2.0.3'}

Type Values Removed Values Added
Description 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.
Title Authentication bypass via default auth token in P4Search
Weaknesses CWE-1392
References
Metrics cvssV4_0

{'score': 10, 'vector': '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'}

Weaknesses

Sources

Status
PUBLISHED
Assigner
Perforce
Published
Updated
Oct 5, 2026, 1:56 PM
Reserved
Sep 25, 2026, 10:28 AM
Status
Awaiting Analysis
Published
Oct 5, 2026, 9:17 AM
Modified
Oct 6, 2026, 3:08 PM