# CVE-2026-6902: Code Injection in Perforce P4 (Helix Core)

> Attackers can execute arbitrary code on Perforce Helix Core servers via the command-line client, requiring an upgrade to the latest patch.

- **Severity:** High 7.7 (`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`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** A user has to click or open something
- **Fix available:** No
- **Published:** 18 May 2026
- **Updated:** 20 May 2026
- **Also known as:** GHSA-9fr9-58h7-gj3c

## What is CVE-2026-6902?

CVE-2026-6902 is a high-severity code injection vulnerability in Perforce P4 (Helix Core), published on 18 May 2026. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.

### Official description

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.

Weakness: CWE-94 (Improper Control of Generation of Code)

## Which versions are affected by CVE-2026-6902?


## How do I fix CVE-2026-6902?

No fix has been published for CVE-2026-6902 yet. Limit exposure of the affected software until one is available.

## Is CVE-2026-6902 being exploited?

There is no known exploitation of CVE-2026-6902 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-6902 and fix it if it is affected.

What it is: CVE-2026-6902 is a high-severity code injection vulnerability in Perforce P4 (Helix Core), published on 18 May 2026. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.
Exploitation: There is no known exploitation of CVE-2026-6902 in the wild and no public exploit code.

Affected product: Perforce P4 (Helix Core). No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-6902/ (Markdown: https://insights.sbomify.com/CVE-2026-6902/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-6902
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-6902
- OSV: https://osv.dev/vulnerability/CVE-2026-6902

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-6902/
Summaries are generated and may contain mistakes; the official description above is the record.