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
Affected Vendors & Products
References
History
Fri, 24 Apr 2026 12:15:00 +0000
| Type | Values Removed | Values Added |
|---|---|---|
| References |
| |
| Metrics |
ssvc
|
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
|
Status: PUBLISHED
Assigner: Perforce
Published: 2026-04-24T11:02:50.723Z
Updated: 2026-04-25T07:17:52.914Z
Reserved: 2026-04-09T17:45:51.571Z
Link: CVE-2026-6043
Updated: 2026-04-24T12:01:57.679Z
Status : Awaiting Analysis
Published: 2026-04-24T12:17:07.660
Modified: 2026-04-24T14:39:28.770
Link: CVE-2026-6043
No data.