CVE-2026-103511: Perforce P4 (Helix Core) · External control of file name or path
Affects Perforce P4 (Helix Core)Source CVE Database V5
Not known to be exploited · CVSS 5.1 Medium · fixed in 2026.4.2 : update Perforce P4 (Helix Core) when convenient.
Data as of 18 Nov 2026, 20:25 UTC
- EPSS
- 0.3% chance of exploitation in 30 days – higher than 26% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
- Patch
- Available – fixed in 2026.4.2
CVSS:4.0/AV:N/AC:L/AT:N/PR:H/UI:N/VC:N/VI:L/VA:L/SC:N/SI:N/SA:NExploitation evidence
Disclosed: evidence found.
CVE published 5 Oct 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponized: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors
A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 17 Nov 2026.
What to do
Affected software
| Product | Affected | Fixed in |
|---|---|---|
| PerforceP4 (Helix Core) | Affected
| Fixed in– |
AI-suggested
A fix is available in Perforce P4 (Helix Core) version 2026.4.2. Users should upgrade to version 2026.4.2 or later to remediate this vulnerability. Since this is not a cloud service, remediation depends on applying the official patch. Patch status is confirmed by the vendor advisory indicating the fix in 2026.4.2.
Description
Perforce P4 Search prior to 2026.4.2 does not validate file names supplied to its extension installation feature. An attacker with super-user or service-token privileges can write files with arbitrary content to the P4 Search installation directory.