CVE-2026-103511: medium-severity vulnerability in Perforce P4 (Helix Core)
Arbitrary file-write via extension installation in P4Search
Published
13Vexday Risk Score
No sign of exploitation. No public exploitation artifact known so far.
ssvc Trackcvss 5.1epss 0.3%
exploitation probability
0.3%top 76% of all CVEs
observed exploitation
nono source reports it
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.
CVSS:4.0/AV:N/AC:L/AT:N/PR:H/UI:N/VC:N/VI:L/VA:L/SC:N/SI:N/SA:N
Affected products
Perforce · P4 (Helix Core)Related CVEs — Perforce P4 (Helix Core)
In the same product, most dangerous first.
CVE-2026-6902HIGHCode Injection in Perforce P4 (Helix Core)EPSS 0.7%CVE-2026-103507HIGHArbitrary file-write via log configuration path in P4SearchEPSS 0.5%CVE-2026-103512MEDIUMTicket host-binding bypass via spoofed client IP in P4SearchEPSS 0.4%CVE-2026-100102CRITICALRCE via exposed JDWP debug agent in P4SearchEPSS 0.4%CVE-2026-103510CRITICALAuthentication bypass via blank auth token in P4SearchEPSS 0.3%