Authentication bypass via default token in Perforce P4Search
Key facts
- Attack vector
- Network
- Privileges required
- None
- User interaction
- None
- Attack complexity
- Low
- Attack requirements
- None
- Impact type
- —
- Confidentiality · integrity · availability
- High · High · High
- Fix status
- Fixed
Attack profile from CVSS 4.0 · CNA. Fix status from CNA.
Summary
Perforce P4Search container images through 2026.4.1 reset the service authentication token to a publicly documented default value (CWE-1392). An unauthenticated remote attacker can obtain the highest application privilege, which can lead to arbitrary code execution and compromise of the connected P4 Server.
Written with Claude Haiku 5.5 from the sources below · 2026-10-29
Description from the CNA
Perforce P4 Search container images prior to 2026.4.2 reset the service authentication token to a publicly documented default value. An unauthenticated attacker with network access can obtain the highest application privilege, potentially leading to arbitrary code execution and compromise of the connected P4 Server.
Why it matters now
SSVC decision points
CISA ADP · SSVC 2.0.3
- Exploitation
- None
- Automatable
- No
- Technical impact
- Total
The decision (Track, Attend, Act) also depends on your mission and well-being impact; see CISA's SSVC guide.
Affected products
Remediation
Update Perforce P4Search container images to version 2026.4.2, which fixes the issue.
Written with Claude Haiku 5.5 from the sources below · 2026-10-29
- Fix · CNA P4 (Helix Core) (Perfoce) Fixed in 2026.4.2
Timeline
- 2026-10-05 Threatist record created from CVE-2026-100103
- 2026-10-05 Alias added: GHSA-crr7-cpqh-vjm5
References
Sources
- CVE-2026-100103 · CVE Program
- CVE-2026-100103 · NVD
- FIRST EPSS
- GHSA-crr7-cpqh-vjm5 · GitHub Advisory Database · CC BY 4.0
This product uses the NVD API but is not endorsed or certified by the NVD. Sources and licences