Veille CVE

Octobre 2026

8 CVE

Critique 3 Élevée 3 Moyenne 2 Faible 0 Non évaluée 0 Exploitées (KEV) Tri : plus récentes « Perforce P4 (Helix core) » ✕
  1. CVE-2026-103509 8.5 Élevée

    Perforce P4 (Helix core)

    P4 Search (formerly Helix Search) returns stored credentials in cleartext through its configuration API to users with administrative privileges on the connected P4 Server, allowing privilege escalation. This affects 2026.4.2 and earlier and is fixed in 2026.4.3.

  2. CVE-2026-103508 7.3 Élevée

    Perforce P4 (Helix core)

    P4 Search (formerly Helix Search) allows an authenticated user holding administrative privileges on the connected P4 Server to supply a crafted logging configuration that causes files to be written or deleted outside the intended logging directory. This could lead to code execution as the P4 Search service account. This issue affects P4 Search 2026.4.2 and earlier. Perforce resolved it in 2026.4.3.

  3. CVE-2026-103512 5.3 Moyenne

    Perforce P4 (Helix Core)

    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 ticket can bypass host-based ticket restrictions and trusted-address controls, gaining access to P4 Search as the ticket's owner.

  4. CVE-2026-103511 5.1 Moyenne

    Perforce P4 (Helix Core)

    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 privileges can write files with arbitrary content to the P4 Search installation directory.

  5. CVE-2026-103510 9.5 Critique

    Perforce P4 (Helix Core)

    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 network access can obtain the highest application privilege, potentially leading to compromise of P4 Search and the connected P4 Server.

  6. CVE-2026-103507 7.5 Élevée

    Perforce P4 (Helix Core)

    Perforce P4 Search prior to 2026.4.2 does not restrict file paths written through its logging configuration interface. An attacker holding the service authentication token can write arbitrary files on the host, potentially leading to code execution as the P4 Search service account.

  7. CVE-2026-100103 10.0 Critique

    Perfoce P4 (Helix Core)

    Perforce P4 Search container images prior to 2026.4.2 reset the service authentication token to a publicly documented default value. An unauthenticated attacker with network access can obtain the highest application privilege, potentially leading to arbitrary code execution and compromise of the connected P4 Server.

  8. CVE-2026-100102 9.5 Critique

    Perforce P4 (Helix Core)

    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 execute arbitrary code as the P4 Search service account, potentially leading to compromise of the connected P4 Server.