Skip to main content
VulnerabilityPublished

CVE-2026-103507: Perforce P4 (Helix Core) · External control of file name or path

Affects Perforce P4 (Helix Core)Source CVE Database V5

0
Compare

Not known to be exploited · CVSS 7.5 High.

Data as of 18 Nov 2026, 20:25 UTC

CVSS 4.0 base score
7.5High
How severe the flaw is on the 0–10 CVSS scale.
EPSS
0.5% chance of exploitation in 30 days – higher than 44% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
CVSS:4.0/AV:N/AC:L/AT:P/PR:H/UI:N/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 5 Oct 2026

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponized: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq 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 18 Nov 2026.

What to do

Affected software

ProductAffectedFixed in
PerforceP4 (Helix Core)Affected
  • <=2026.4.1
Fixed in–

AI-suggested

A fix is available in Perforce P4 (Helix Core) version 2026.4.2. Users should upgrade to this version or later to remediate the vulnerability. Since this is not a cloud service, remediation requires applying the official patch or upgrade provided by Perforce.

Description

Perforce P4 Search prior to 2026.4.2 does not restrict file paths written through its logging configuration interface. An attacker holding the service authentication token can write arbitrary files on the host, potentially leading to code execution as the P4 Search service account.

References

Community reviews

Loading reviews…