Skip to main content

P4 Server EUVDEUVD-2026-30747

| CVE-2026-6902 HIGH
Code Injection (CWE-94)
2026-05-18 Perforce GHSA-9fr9-58h7-gj3c
7.7
CVSS 4.0 · Vendor: Perforce
View

Attack ChainAIDerived

Hypothetical attack flow derived from CVE metadata – not a confirmed exploit chain

  1. Access
    Deliver malicious input
  2. Delivery
    User processes input via P4 CLI
  3. Exploit
    Trigger code injection
  4. Execution
    Execute arbitrary commands
  5. Impact
    Compromise 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.

This Week Schedule remediation this week. Why: HIGH severity (CVSS 7.0-8.9).
No patch listed yet 0.0% exploitation probability (EPSS)

Get an e-mail when this CVE is exploited, patched or re-scored. Free account.

Alert me

AnalysisAIv1 – 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

P4 (Helix Core) 0 <P4 (Helix Core) 2025.2 Patch 2

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

Vendor (Perforce) PRIMARY 7.7 HIGH
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

Attack Vector
Network
Attack Complexity
Low
Attack Requirements
Present
Privileges Required
None
User Interaction
Passive
Vulnerable system: Confidentiality
High
Vulnerable system: Integrity
High
Vulnerable system: Availability
High
Subsequent system: Confidentiality
Low
Subsequent system: Integrity
Low
Subsequent system: Availability
Low

Lifecycle Timeline

1
CVSS changed
May 18, 2026 - 09:22 NVD
7.7 (HIGH)

DescriptionCVE.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

Why It Matters

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.

Business Impact: High
Compensating Controls

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

EPSS Score
0.0%
Top 85% exploitable
Data Quality
6 sources
Confidence: High

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.

SignalValue
Severity HIGH
CISA KEV No
Public POC No
EPSS 0.0%
Patch available No
Active threat No
Deciding rule
HIGH severity (CVSS 7.0-8.9)
What every action level means
Emergency Immediate action required. Criteria: CRITICAL + in CISA KEV (actively exploited) without patch, OR CRITICAL + EPSS > 30% without patch, OR CRITICAL + active threat signals without patch.
Act Now Prioritize within 24-48h. Criteria: in KEV with patch available, OR CRITICAL + public POC, OR HIGH + EPSS > 10%, OR CRITICAL + active threat, OR any CRITICAL severity.
This Week Schedule remediation this week. Criteria: HIGH severity (CVSS 7.0-8.9). Patch within normal change window.
This Month Plan within 30 days. Criteria: MEDIUM severity (CVSS 4.0-6.9), lower exploitation probability. Include in regular patch cycle.
Monitor Track and reassess. Criteria: LOW severity (CVSS 0.1-3.9), minimal exploitation risk. No immediate action needed.

SSVC AssessmentENISA

SSVC Decision
Scheduled
Exploitation
None
System Exposure· derived
Open
Automatable
No
Human Impact
High
Technical Impact
Total

Priority Score

38
Low Medium High Critical
KEV: 0
EPSS: 0
CVSS: +38
PoC: 0
Weaponized: 0
Threat intel: 0
Gov advisory: 0

Attack Technique

Code Injection CRITICAL

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.

This site uses cookies essential for authentication and security. No tracking or analytics cookies are used. Privacy Policy