CVE-2026-103507

Arbitrary file-write via log configuration path in P4Search

  • High 7.5

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.

Key facts

Published
5 Oct 2026
Last changed
5 Oct 2026
Assigned by
Perforce
EPSS
0.513% likely to be exploited in the next 30 days, higher than 44.34% of CVEs (scores for 17 Nov 2026)
SSVC (CISA)
Exploitation: none; Automatable: no; Technical impact: total

Severity scores

Each score is shown as its source gave it. They are not averaged or merged.

  • 7.5CVSS 4.0, Highfrom the CNA (Perforce)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

Historical context and remediation

This reference retains the original CVE publication date. A recent record update does not mean a new attack occurred.

No separately sourced impact summary is available on this page yet. Consult the description, version data and dated exploitation evidence.

No explicit remediation statement is available on this page yet. Consult the original record and vendor references before choosing a fix.

Version statuses below come from the CNA. An “unaffected” version is not necessarily a currently supported release or proof of a patch date. EPSS is a dated risk estimate, not a count of historical attacks.

Read the original CVE record.

Affected products

VendorProductVersions
PerforceP4 (Helix Core)
  • Default status: affected
  • 0 up to and including 2026.4.1 (affected)
  • 2026.4.2 (unaffected)

Timeline

  1. 5 Oct 2026 Published

Weakness

References