Attack ChainAIDerived
Hypothetical attack flow derived from CVE metadata – not a confirmed exploit chain
-
AccessDeliver malicious input
-
DeliveryUser processes input via P4 CLI
-
ExploitTrigger code injection
-
ExecutionExecute arbitrary commands
-
ImpactCompromise system
Vulnerability Assessment
| Weakness |
CWE
OWASP Top 10:2025
A05:2025 - Injection
ASVS 5.0
V1 - Encoding and Sanitization Code injection prevention, sandbox exec
MITRE ATT&CK
2 techniques across 2 tactics: Execution, Initial Access The technique list with ATT&CK links and the kill-chain view is part of the Basic plan and up. |
| Exploitation Conditions | Successful exploitation requires a legitimate user to interact with malicious input through the P4 command-line client. The vulnerability does not require authentication from the attacker's perspective but does require user interaction to trigger the code injection. The CVSS vector indicates specific attack requirements must be present (AT:P), though the exact conditions are not detailed in the available information. |
| Impact | The CVSS 7.7 score reflects a network-based attack (AV:N) with low complexity (AC:L) that requires no authentication (PR:N) but does require user interaction (UI:P). The CVSS vector indicates high impact to confidentiality, integrity, and availability (VC:H/VI:H/VA:H) with lower secondary system impacts. The 'AT:P' (Attack Requirements: Present) suggests specific conditions must be met for exploitation. No EPSS score or KEV status is provided, and no public exploit code has been identified, suggesting this may not be widely exploited despite the high CVSS score. The requirement for user interaction significantly reduces the automated exploitation risk. |
| Exploit ScenarioDerived | An attacker crafts malicious input that, when processed by a legitimate user through the P4 command-line client, injects and executes arbitrary code. This could occur when a user interacts with attacker-controlled repository content or processes malicious command-line arguments, leading to full system compromise with the privileges of the user running the client. |
Get an e-mail when this CVE is exploited, patched or re-scored. Free account.
Alert meAnalysisAIv1 – May 18, 2026
Code injection vulnerability in the Command-Line Client of P4 Server (Helix Core) prior to version 2025.2 Patch 2 allows remote attackers to execute arbitrary code. The vulnerability requires user interaction but no authentication, with a CVSS 7.7 score indicating high impact across confidentiality, integrity, and availability. Perforce has released a patch in version 2025.2 Patch 2.
RemediationAI
Upgrade P4 Server to version 2025.2 Patch 2 or later, which contains the fix for this vulnerability. The patch is available from Perforce and should be applied immediately to all affected installations. No specific workarounds are documented in the advisory. Organizations unable to patch immediately should restrict access to the P4 command-line client to trusted users only and monitor for suspicious command-line activity, though this provides limited protection against user interaction-based attacks.
Affected VersionsENISA
Affects your stack
Find out whether the stacks and servers you run are on an affected version.
Checking this CVE against your own stacks and servers is part of the Basic plan and up.
Technical ContextAI · show details
P4 Server, also known as Helix Core, is Perforce's version control system used for managing source code and digital assets. The vulnerability affects the command-line client component and is classified as CWE-94 (Improper Control of Generation of Code), indicating that user-supplied input can be interpreted as executable code. The CPE identifier confirms this affects all versions of Helix Core prior to the patched release.
Know when P4 Helix Core gets its next vulnerability
- Watch products and get an email when something new is published
- Check this CVE against your own stack and servers
- Exploit and PoC references, threat intelligence from 22 sources
No credit card · 7-day full trial
Severity by source
CVSS:4.0/AV:N/AC:L/AT:P/PR:N/UI:P/VC:H/VI:H/VA:H/SC:L/SI:L/SA:L
Primary rating from Vendor (Perforce) · only source for this CVE.
CVSS VectorVendor: Perforce
Lifecycle Timeline
1DescriptionCVE.org
A vulnerability in Command-Line Client in P4 Server prior to the 2025.2 Patch 2, identified as CVE-2026-6902, has been fixed in P4 Server to address potential security risks.
Executive ViewAI
CVE-2026-6902 is a high-severity code injection vulnerability in Perforce Helix Core's command-line client that enables unauthenticated remote code execution with user interaction. Organizations running Helix Core versions prior to 2025.2 Patch 2 face immediate risk of system compromise, data theft, and operational disruption through compromised development workflows.
Apply vendor patch version 2025.2 Patch 2. If immediate patching is not feasible, restrict command-line client access to trusted internal networks only, disable remote CLI functionality where operationally acceptable, and implement strict input validation and monitoring on CLI commands.
Threat Intelligence Overview
How this decision was reached
The engine reads each signal below and applies a fixed list of rules from top to bottom. The first rule that matches sets the recommended action – like a statement, every line is shown.
What every action level means
SSVC AssessmentENISA
Priority Score
Attack Technique
Code injection occurs when an application accepts user input and passes it directly into a language interpreter or evaluator without proper sanitization.
Remote Code Execution represents the critical moment when an attacker successfully runs arbitrary code on a target system without physical access.
More in P4 Helix Core
View allUnauthenticated network attackers can gain the highest application privileges on Perforce P4 Search container images pri
Unauthenticated remote code execution is possible in Perforce P4 Search container images prior to 2026.4.2 due to an exp
Perforce P4 Search before 2026.4.2 fails open when its service authentication token is blank, so an unauthenticated remo
Cleartext credential disclosure in P4 Search (formerly Helix Search) 2026.4.2 and earlier allows an authenticated admini
Arbitrary file write in Perforce P4 Search versions prior to 2026.4.2 allows an attacker who already holds a valid P4 Se
Host-based authentication controls in Perforce P4 Search prior to 2026.4.2 can be bypassed because the service trusts a
Arbitrary file write in Perforce P4 Search versions prior to 2026.4.2 allows an attacker who already holds super-user or
EUVD-2026-30747
GHSA-9fr9-58h7-gj3c
NVD
CVE.org
EPSS
Vulnrichment
VulDB
Exploit-DB