Perforce P4 (Helix Core)
8 CVEs affecting Perforce P4 (Helix Core). Latest disclosed: 2026-10-15. Critical: 0, High: 0.
| CVE | Severity | Score | Published | Summary |
|---|---|---|---|---|
CVE-2026-103509 | | 2026-10-15 | P4 Search (formerly Helix Search) returns stored credentials in cleartext through its configuration API to users with administrative privileges on the connecte… | |
CVE-2026-103508 | | 2026-10-15 | P4 Search (formerly Helix Search) allows an authenticated user holding administrative privileges on the connected P4 Server to supply a crafted logging configu… | |
CVE-2026-103512 | | 2026-10-05 | Perforce P4 Search prior to 2026.4.2 trusts a client-supplied address when validating certain authentication requests. An attacker holding a stolen P4 Server t… | |
CVE-2026-103511 | | 2026-10-05 | Perforce P4 Search prior to 2026.4.2 does not validate file names supplied to its extension installation feature. An attacker with super-user or service-token… | |
CVE-2026-103510 | | 2026-10-05 | P4 Search prior to 2026.4.2 does not fail securely when its service authentication token is blank. In affected configurations, an unauthenticated attacker with… | |
CVE-2026-103507 | | 2026-10-05 | Perforce P4 Search prior to 2026.4.2 does not restrict file paths written through its logging configuration interface. An attacker holding the service authenti… | |
CVE-2026-100102 | | 2026-10-05 | Perforce P4 Search container images prior to 2026.4.2 enable an unauthenticated Java debug interface. An attacker with network access to this interface can exe… | |
CVE-2026-6902 | | 2026-05-18 | A Remote Code Execution vulnerability in P4 (Helix Core) Server's Command-Line Client, prior to the 2025.2 Patch 2, has been fixed to address potential securit… |