# CVE-2026-100103: Perforce P4 Search authentication bypass via default token

Source: https://junglewise.ai/threats/cve-2026-100103-perforce-p4-search-container-images-prior-to-2026-4-2-reset-the  
Publisher: Junglewise Threat Intelligence, https://junglewise.ai/threats  
Published: 2026-10-05. Updated: 2026-10-05  
License: CC BY 4.0 with a link back

CVE-2026-100103 · Severity: info · Published 2026-10-05

Perforce P4 Search is a container-based search indexing service for Perforce's version control system. Container images prior to version 2026.4.2 ship with a hardcoded default authentication token that is publicly documented, allowing any network attacker to gain full administrative access and execute arbitrary code on the P4 Server.

Technologies: [Perforce P4 Search](https://junglewise.ai/threats/technologies/p4-search). Vendors: [Perforce](https://junglewise.ai/threats/vendors/perforce).

## Quick answers

**Is CVE-2026-100103 exploited in the wild?** No. Junglewise Threat Intelligence has no report of CVE-2026-100103 being exploited in the wild.

**How severe is CVE-2026-100103?** Informational severity, published 5 October 2026.

**Which products and versions are affected?** Perforce P4 Search prior to 2026.4.2.

**Is there a fix for CVE-2026-100103?** Yes: fixed in 2026.4.2. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.

**How is CVE-2026-100103 attacked?** It is attacked over the network, in a network appliance.

**Am I affected by CVE-2026-100103?** Check whether you run Perforce P4 Search at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.

## How to fix

- Fixed in 2026.4.2

## Technical details

The service authentication token in P4 Search container images is reset to a publicly documented default value, enabling unauthenticated network attackers to obtain the highest application privilege level. This authentication bypass allows direct access to the P4 Search service without valid credentials, and when connected to a P4 Server, can be leveraged to achieve arbitrary code execution on the server infrastructure.

## Affected products

- Perforce P4 Search prior to 2026.4.2

## Timeline

- 2026-10-05: disclosed

## References

- [https://portal.perforce.com/s/cve/a91Qi000003FE8zIAG/authentication-bypass-via-default-auth-token-in-p4search](https://portal.perforce.com/s/cve/a91Qi000003FE8zIAG/authentication-bypass-via-default-auth-token-in-p4search)

## Related threats

- [P4 Search credential disclosure in configuration API](https://junglewise.ai/threats/cve-2026-103509-p4-search-formerly-helix-search-returns-stored-credentials-in)
- [Perforce P4 Search path traversal via logging configuration](https://junglewise.ai/threats/cve-2026-103508-p4-search-formerly-helix-search-allows-an-authenticated-user)
- [Perforce P4 Search ticket validation bypass in client IP handling](https://junglewise.ai/threats/cve-2026-103512-perforce-p4-search-prior-to-2026-4-2-trusts-a-client-supplied)
- [Perforce P4 Search arbitrary file write in extension installation](https://junglewise.ai/threats/cve-2026-103511-perforce-p4-search-prior-to-2026-4-2-does-not-validate-file)
- [Perforce P4 Search authentication bypass via blank auth token](https://junglewise.ai/threats/cve-2026-103510-p4-search-prior-to-2026-4-2-does-not-fail-securely-when-its)