Skip to content
OpenAdvisories

Vendor

Perforce

25 known vulnerabilities.

Perforce at a glance

Last 12 months
18
Critical · all time
7
Exploited · all time
0
Public exploit · all time
1
New vulnerabilities per month · last 12 months
0 5 10 December 2025: 2 vulnerabilities Dec 2025 January 2026: 0 vulnerabilities February 2026: 0 vulnerabilities March 2026: 0 vulnerabilities Mar April 2026: 1 vulnerability May 2026: 1 vulnerability June 2026: 0 vulnerabilities Jun July 2026: 2 vulnerabilities August 2026: 0 vulnerabilities September 2026: 2 vulnerabilities, 1 critical Sep October 2026: 8 vulnerabilities, 3 critical November 2026: 2 vulnerabilities, 2 critical
Show as table
MonthVulnerabilitiesCritical
Nov 202622
Oct 202683
Sep 202621
Aug 202600
Jul 202620
Jun 202600
May 202610
Apr 202610
Mar 202600
Feb 202600
Jan 202600
Dec 202520
Nov 202500
Oct 202500
Sep 202510
Aug 202500
Jul 202500
Jun 202510
May 202500
Apr 202531
Mar 202510
Feb 202500
Jan 202500
Dec 202400

25 results · Feed

  • Critical 9.4

    Report Deserialization Code Execution

    Deserialization of untrusted data in the report-processing code of Puppet, as used by Puppet Server, in the affected releases, allows a client that holds any CA-signed agent certificate to execute arbitrary code on the Puppet Server as its service user by sub…

  • Critical 9.0

    Certificate Name Authorization Bypass

    Incorrect authorization in the certificate-name matching of trapperkeeper-authorization, as used by Puppet Server, in the affected products, allows a client that holds a CA-signed certificate whose name extends or shortens an authorized hostname to be authori…

  • High 8.5

    Credential Disclosure in P4 Search Configuration API

    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…

  • High 7.3

    Path traversal via logging configuration in P4Search

    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…

  • Critical 9.3

    Perforce Helix Authentication Service (HAS) deployments that retain the shipped default SCIM bearer token are vulnerabl…

  • Critical 9.5

    Authentication bypass via blank auth token in P4Search

    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 P…

  • Medium 5.1

    Arbitrary file-write via extension installation in P4Search

    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.

  • Medium 5.3

    Ticket host-binding bypass via spoofed client IP in P4Search

    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 S…

  • High 7.5

    Arbitrary file-write via log configuration path in P4Search

    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 …

  • Critical 9.5

    RCE via exposed JDWP debug agent in P4Search

    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 conne…

  • High 8.6

    XML External Entity in Akana API Platform

    A flaw resulting in XML external entity (XXE) was found in Akana API Platform in which references were improperly restricted during XML-to-JSON processing. The issue affects Akana versions 2026.1, 2025.1.1, and all versions before 2024.1.6 (including older un…

  • Critical 9.8

    Unauthenticated Remote Code Execution in Akana API Platform

    An unauthenticated remote code execution vulnerability exists in the Policy Manager console of Akana API Platform. A path normalization discrepancy between the authentication filter and the servlet dispatcher allows a crafted request to bypass authentication …

  • High 8.3

    Improper Restriction of Excessive Authentication Attempts in Delphix Continuous Data

    A race condition in the account lockout mechanism in Delphix Continous Data allowed the lockout threshold to be bypassed through concurrent authentication requests. Parallel login attempts were processed before the failed-login counter and lockout status were…

  • Medium 6.7

    Cleartext Storage of Sensitive Information for Puppet Resource API

    Puppet resource_api (shipped in Puppet Core 8.x and Puppet Enterprise 2023.8.x and 2025.x) does not preserve the sensitive flag on parameters defined via the resource-api, causing values such as passwords to be stored in cleartext in the agent's local transac…

  • High 7.7

    Code Injection in Perforce P4 (Helix Core)

    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 security risks.

  • High 8.8
    CVE-2026-6043 Public exploit

    Insecure Default Configuration in P4 Server

    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 s…

  • Medium 5.3

    PII Leak Due to Change in EOR Handling

    In Delphix Continuous Compliance version 2025.3.0 and later, following a recent bug fix to correctly handle CR+LF (Windows and DOS) End-of-Record (EOR) characters in delimited files, an issue was identified: using an incorrect EOR configuration can cause inac…

  • Medium 5.3

    Missing authorization in BlazeMeter Jenkins Plugin

    A fix was made in BlazeMeter Jenkins Plugin version 4.27 to allow users only with certain permissions to see the list of available resources like credential IDs, bzm workspaces and bzm project Ids. Prior to this fix, anyone could see this list as a dropdown o…

  • Medium 6.9

    Insufficiently Protected Credentials in Puppet Enterprise 2025.4 and 2025.5

    In Puppet Enterprise versions 2025.4.0 and 2025.5, the encryption key used for encrypting content in the Infra Assistant database was not excluded from the files gathered by Puppet backup. The key is only present on the system if the user has a Puppet Enterpr…

  • High 8.6

    OS Command Injection

    A user with specific node group editing permissions and a specially crafted class parameter could be used to execute commands as root on the primary host. It affects Puppet Enterprise versions 2018.1.8 through 2023.8.3 and 2025.3 and has been resolved in vers…

  • High 8.5

    Privilege Chaining in Delphix

    An attacker with knowledge of creating user accounts during VM deployment on Google Cloud Platform (GCP) using the OS Login feature, can login via SSH gaining command-line control of the operating system. This allows an attacker to gain access to sensitive da…

  • Critical 9.0

    Improper Access Control in Delphix Masking Engine

    A valid, authenticated user with sufficient privileges and who is aware of Continuous Compliance’s internal database configurations can leverage the application’s built-in Connector functionality to access Continuous Compliance’s internal database. This allow…

  • Medium 6.3

    Potential Username Enumeration in Helix ALM

    Helix ALM prior to 2025.1 returns distinct error responses during authentication, allowing an attacker to determine whether a username exists.

  • Medium 6.9

    Username Enumeration in Gliffy

    Lack of Rate Limiting in Sign-up workflow in Perforce Gliffy prior to version 4.14.0-7 on Gliffy online allows attacker to enumerate valid user emails and potentially DOS the server

  • Low 2.0

    Command Injection in Helix ALM

    In Helix ALM versions prior to 2024.2.0, a local command injection was identified. Reported by Bryan Riggins.