# CVE-2026-103509: P4 Search credential disclosure in configuration API

Source: https://junglewise.ai/threats/cve-2026-103509-p4-search-formerly-helix-search-returns-stored-credentials-in  
Publisher: Junglewise Threat Intelligence, https://junglewise.ai/threats  
Published: 2026-10-15. Updated: 2026-10-16  
License: CC BY 4.0 with a link back

CVE-2026-103509 · Severity: info · Published 2026-10-15

P4 Search (formerly Helix Search) is a search and indexing tool for Perforce version control systems. An administrative user can retrieve cleartext stored credentials through the configuration API, potentially allowing them to escalate privileges or access systems the credentials protect. This affects P4 Search 2026.4.2 and earlier.

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

## Quick answers

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

**How severe is CVE-2026-103509?** Informational severity, published 15 October 2026.

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

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

**How is CVE-2026-103509 attacked?** It is attacked over the network, in a hosted service.

**Am I affected by CVE-2026-103509?** 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.3

## Technical details

P4 Search stores credentials for connecting to P4 Server and other integrated systems. The configuration API returns these credentials in cleartext to users with administrative privileges on the connected P4 Server, rather than masking or encrypting them. An attacker with admin access to P4 Server can extract stored credentials and potentially access downstream systems or escalate privileges.

## Affected products

- Perforce P4 Search 2026.4.2 and earlier

## Timeline

- 2026-10-15: disclosed

## References

- [https://portal.perforce.com/s/cve/a91Qi000003Gdi1IAC/credential-disclosure-in-p4-search-configuration-api](https://portal.perforce.com/s/cve/a91Qi000003Gdi1IAC/credential-disclosure-in-p4-search-configuration-api)

## Related threats

- [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)
- [Perforce P4 Search arbitrary file write in logging configuration](https://junglewise.ai/threats/cve-2026-103507-perforce-p4-search-prior-to-2026-4-2-does-not-restrict-file)