CVE-2026-103510: fallo crítico en Perforce P4 (Helix Core)
Authentication bypass via blank auth token in P4Search
Publicada el
28Vexday Risk Score
Sin señal de explotación. Ningún artefacto público de explotación conocido hasta ahora.
ssvc Trackcvss 9.5epss 0.3%
probabilidad de explotación
0.3%top 74% de las CVE
explotación observada
noninguna fuente lo reporta
P4 Search prior to 2026.4.2 does not fail securely when its service authentication token is blank. In affected configurations, an unauthenticated attacker with network access can obtain the highest application privilege, potentially leading to compromise of P4 Search and the connected P4 Server.
CVSS:4.0/AV:N/AC:L/AT:P/PR:N/UI:N/VC:H/VI:H/VA:H/SC:H/SI:H/SA:H
Productos afectados
Perforce · P4 (Helix Core)CVEs relacionadas — Perforce P4 (Helix Core)
En el mismo producto, de las más peligrosas a las menos.
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-103511MEDIUMArbitrary file-write via extension installation in P4SearchEPSS 0.3%