CVE-2026-103507: Arbitrary file-write via log configuration path in P4Search
Perforce · P4 (Helix Core)
Vendor fix available · Affected: Perforce P4 (Helix Core) · Exploitation: not established
At a glance
Higher than 44% of scored CVEs
What it isNVD
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.
ExploitationNot established
Not in CISA KEV as of catalogue 2026.11.18 (18 Nov)
- Not establishedNothing in the sources we check
Not seen so far: in CISA KEV · exploited (reported) · scanning observed · proof of concept public.
Weakness and public checks
- Public check
- No public nuclei template
- Weakness
- External Control of File Name or Path · File and Path Handling
Other CVEs in P4 (Helix Core)
Every published CVE for Perforce P4 (Helix Core), by how far exploitation has gone. This one is among them.
Coverage1 article · 1 outlet
First in our coverage: SecurityOnline, 5 Oct.
- Perforce P4 Search Flaws Let Attackers Seize Unprotected ServicesSecurityOnline · first in our coverage · mentions it in passing
New articles also arrive in the RSS feed.