Live Exposure Defense: From CVE to Confirmed Exposure in 12 Hours – See more

Back
New CVE Detected

CVE-2026-103510 – Authentication Bypass / Unauthenticated RCE Risk – Perforce P4 Search prior to 202

Be the first to know when new zero-days emerge:

Subscribe to Email Alerts
Subscribe to RSS Feed

Summary

CVE-2026-103510 is an authentication bypass vulnerability in Perforce P4 Search, the search component bundled with P4 (Helix Core). The component fails to fail securely when its service authentication token is left blank, allowing an unauthenticated, network-based attacker to obtain the highest application privilege within P4 Search. This can lead to full compromise of P4 Search and the connected P4 Server, and Perforce has rated the issue Critical (CVSS 9.5).

Technical details

  • Root cause: P4 Search validates requests using a service authentication token, but when that token is configured as blank (empty), the component does not reject the request — it "fails open" rather than failing securely (CWE-636: Not Failing Securely).
  • Trigger conditions: The flaw manifests "in affected configurations" where the P4 Search service authentication token has been left blank, which removes the intended authentication check entirely.
  • Attack vector: Network — no authentication or user interaction is required; an attacker only needs network access to the exposed P4 Search service.
  • Impact: A successful attacker can obtain the highest application privilege within P4 Search, enabling compromise of the P4 Search instance and, through its connection, the backing P4 Server — threatening confidentiality, integrity, and availability of source code and related data.

Affected software

  • Perforce P4 (Helix Core) — P4Search component, versions 0 through 2026.4.1 (i.e., all versions prior to 2026.4.2) where the service authentication token is blank.
  • Fixed in P4Search 2026.4.2.

Severity

  • CVSS v4.0 Base Score: 9.5 (Critical)
  • Vector: 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
  • Attack Vector: Network, Attack Complexity: Low, Privileges Required: None, User Interaction: None, with High impact to Confidentiality, Integrity, and Availability.

Mitigation and recommended actions

  • Immediate: Upgrade P4 Search to version 2026.4.2 or later, which addresses the insecure fail-open behavior.
  • If immediate patching is not possible: Ensure the P4 Search service authentication token is explicitly configured with a strong, non-blank value, and restrict network access to the P4 Search service to trusted hosts/networks only (e.g., via firewall rules or network segmentation) until the patch can be applied.
  • Review P4 Search and P4 Server logs for unexpected or unauthenticated access patterns as part of incident response.

References

Are you exposed?

Get a free report of your organization’s exposure to this CVE and threat

  • Mapping of all Assets with this Technology
  • Identification of potentially exposed assets to this CVE
  • Confirmation of verified exploitable assets
Get Exposure Report

How IONIX’s External Exposure Management Platform Detects and Validates
Zero-Days to Shrink MTTR

1

Map your entire attack surface (continously)

IONIX uses multi-factor discovery methods, including DNS analysis, certificate mapping, metadata inspection, and more, to automatically map every internet-facing asset across your environment. This includes cloud instances, third-party platforms, shadow IT, and even forgotten infrastructure that traditional tools miss.

2

Monitor for new CVEs

Dozens of threat intel feeds using agentic technology are continuously analyzed to detect the appearance of proof-of-concept code, exploit kits, and indicators of active targeting. IONIX goes further by applying AI to proactively evaluate whether emerging vulnerabilities are likely to be exploited, even before PoCs go public.

3

Identify Potential External Exposures

Not all CVEs matter. IONIX filters vulnerabilities by asking attacker-centric questions: Can it be reached from the internet? Does it require authentication? Is it being exploited in the wild? This dramatically reduces noise and focuses teams on threats that can actually be weaponized.

4

Create Safe, Scalable Exploit Validations

IONIX transforms real-world PoCs into safe, non-intrusive test payloads that can be run in production environments without disruption. These simulations are precisely targeted to the systems that are vulnerable, ensuring rapid validation without unnecessary load.

5

Execute Exploit Validations

By combining context about software stack, versioning, exposure status, and reachability, IONIX ensures that only the right payloads are executed against the right assets, maximizing efficiency and minimizing risk.

6

Drive Fast and Actionable Remediation

Results are routed through integrations with ticketing, SOAR, and SIEM tools. Issues are written in plain language, bundled into remediation clusters, and prioritized based on asset criticality, exploitability, and blast radius. This shortens mean time to remediation (MTTR) and empowers teams to act with confidence.

Are you exposed?

Get a free report of your organization’s exposure to this CVE and threat

  • Mapping of all Assets with this Technology
  • Identification of potentially exposed assets to this CVE
  • Confirmation of verified exploitable assets
Get Exposure Report
Close

Subscribe to Threat Center RSS

Copy/paste the link below into your preferred RSS reader or follow these instructions to subscribe to Slack alerts.

Open RSS feedSlack setup instructions

Close

Get Real-Time CVE Alerts to Your Email

Be the first to know when new zero-days emerge