CVE-2026-6902
Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.
NVD · uneditedA 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.
Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.
dbcve analysis · moderate confidenceA Remote Code Execution vulnerability exists in the P4 (Helix Core) Server's Command-Line Client prior to version 2025.2 Patch 2. Attackers could potentially execute arbitrary code on affected systems through the CLI client.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.
From the vector- Attack vector
- Network
- Complexity
- Low
- Privileges
- None
- Authentication
- X
- User interaction
- P
- Scope
- X
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/E:X/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:X
Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.
dbcve checksWork through these to decide whether this CVE applies to you.
-
Check if the P4 (Helix Core) CLI client is installedRun 'p4 -V' or 'p4 version' or 'which p4' to verify the client binary exists on the systemAffected if The p4 command returns a version number, indicating the CLI client is installed
-
Determine the installed P4 CLI client versionExecute 'p4 -V' and note the version string in the output (typically shows as YYYY.N patch number)Affected if A version number is displayed in the output
-
Compare the installed version against the affected rangeCompare the version obtained from 'p4 -V' to version 2025.2 Patch 2. Versions prior to 2025.2 Patch 2 are affected.Affected if The installed version is earlier than 2025.2 Patch 2 (for example, 2025.1, 2024.2, or older)
-
Verify the CLI client is exposed to untrusted execution contextsReview file permissions on the p4 binary and check if untrusted users or processes can invoke the p4 command. Check for world-executable permissions with 'ls -la $(which p4)'Affected if The p4 binary is executable by untrusted users and the version is below 2025.2 Patch 2
A system is affected if the P4 Helix Core CLI client is installed with a version earlier than 2025.2 Patch 2 and is accessible to untrusted users or processes.
Generated from the published advisory. Verify against your own configuration.
Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.
dbcve · scopedUpgrade Helix Core Server Command-Line Client to version 2025.2 Patch 2 or later to remediate this vulnerability.
2025.2 Patch 2 (or later)
- 1. Identify the current version of your P4 (Helix Core) Command-Line Client by running 'p4 -V' or 'p4 version'
- 2. Navigate to the Perforce download portal at portal.perforce.com
- 3. Locate and download Helix Core version 2025.2 Patch 2 (or later) for your platform
- 4. Backup your current P4 client installation and configuration
- 5. Install the 2025.2 Patch 2 version of the P4 command-line client
- 6. Verify the installation by running 'p4 -V' and confirming the version shows 2025.2 Patch 2 or later
- 7. If you also run Helix Core Server (p4d), ensure that component is also updated to 2025.2 Patch 2
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation2.0 h
- Implementation4.0 h
- Testing3.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,088.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-6902 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2026-6902 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
No notes yet
Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.
A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.
- Verified mitigations, workarounds, and config changes
- Version or environment caveats, and links to real fixes
- No weaponised exploit code, or anything meant to cause harm
- No spam, self-promotion, credentials, or personal data