CVE-2026-6043: high-severity vulnerability in Perforce Helix Core Server (P4D)
Insecure Default Configuration in P4 Server
Published · Updated
E-mail alert when it lands in KEV, gets a public PoC or its score goes up.
41Vexday Risk Score
No sign of exploitation. It has a public proof of concept.
ssvc Attendcvss 8.8epss 1.3%
from disclosure to weaponsame day
Published on NVDApr 24
1st PoCApr 3
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
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
Affected products
Perforce · Helix Core Server (P4D)public PoCs found — 1
githubgithub.com/flyingllama87/p4wned★ 2⚠ Public resources, to assess the exposure of systems you control or are authorized to test. Test only with authorization.