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

Project Subscriptions

Vendors Products
Perforce Subscribe
Helix Core Server P4d Subscribe
Advisories

No advisories yet.

Fixes

Solution

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.


Workaround

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.

History

Fri, 24 Apr 2026 12:15:00 +0000

Type Values Removed Values Added
References
Metrics ssvc

{'options': {'Automatable': 'yes', 'Exploitation': 'none', 'Technical Impact': 'partial'}, 'version': '2.0.3'}


Fri, 24 Apr 2026 12:00:00 +0000

Type Values Removed Values Added
Description 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 enforces secure-by-default 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

Fri, 24 Apr 2026 11:30:00 +0000

Type Values Removed Values Added
Description 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 enforces secure-by-default
Title Insecure Default Configuration in P4 Server
First Time appeared Perforce
Perforce helix Core Server P4d
Weaknesses CWE-1188
CPEs cpe:2.3:a:perforce:helix_core_server_p4d_:*:*:*:*:*:*:*:*
Vendors & Products Perforce
Perforce helix Core Server P4d
References
Metrics cvssV4_0

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


Projects

Sign in to view the affected projects.

cve-icon MITRE

Status: PUBLISHED

Assigner: Perforce

Published:

Updated: 2026-04-24T12:02:01.772Z

Reserved: 2026-04-09T17:45:51.571Z

Link: CVE-2026-6043

cve-icon Vulnrichment

Updated: 2026-04-24T12:01:57.679Z

cve-icon NVD

Status : Received

Published: 2026-04-24T12:17:07.660

Modified: 2026-04-24T12:17:07.660

Link: CVE-2026-6043

cve-icon Redhat

No data.

cve-icon OpenCVE Enrichment

No data.

Weaknesses