CVE-2026-6043 PUBLISHED

Insecure Default Configuration in P4 Server

Assigner: Perforce
Reserved: 09.04.2026 Published: 24.04.2026 Updated: 25.04.2026

P4 Server versions prior to 2026.1 are configured with insecure default settings that, when exposed to untrusted networks, allow unauthenticated attackers to create arbitrary user accounts, enumerate existing users, authenticate to accounts with no password set, and access depot contents via the built-in 'remote' user. These default settings, taken together, can lead to unauthorized access to source code repositories and other managed assets. The 2026.1 release, expected in May 2026, enforces secure-by-default configurations on upgrade and new installations

Metrics

CVSS Vector: CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:H/VI:L/VA:N/SC:N/SI:N/SA:N
CVSS Score: 8.8

Product Status

Vendor Perforce
Product Helix Core Server (P4D)
Versions Default: unaffected
  • affected from 0 to 2025.2 (incl.)

Workarounds

For installations that cannot immediately upgrade to 2026.1, administrators should apply manual hardening by configuring security-related server settings as documented at https://help.perforce.com/helix-core/server-apps/p4sag/current/Content/P4SAG/security-configurables.html.

Solutions

Upgrade to P4 Server (P4D) version 2026.1 or later, expected in May 2026, which enforces secure-by-default configurations on both new installations and upgrades.

References

Problem Types

  • CWE-1188 Initialization of a resource with an insecure default CWE

Impacts

  • CAPEC-169 Footprinting