Quick answers
- Is CVE-2026-109758 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-109758 being exploited in the wild.
- How severe is CVE-2026-109758?
- Informational severity, published 13 October 2026.
- Which products and versions are affected?
- Perforce Helix Authentication Service 2022.1 - 2025.2.
- Is there a fix for CVE-2026-109758?
- Yes: fixed in 2026.1. Until then: Change the SCIM bearer token from the default value to a randomly generated credential during installation or post-deployment configuration. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
- How is CVE-2026-109758 attacked?
- It is attacked over the network, in a hosted service.
- Am I affected by CVE-2026-109758?
- Check whether you run Perforce Helix Authentication Service 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.1
Change the SCIM bearer token from the default value to a randomly generated credential during installation or post-deployment configuration.
Technical details
The installation templates of HAS versions 2022.1 through 2025.2 contain a hardcoded default SCIM bearer token that the installer does not automatically replace during deployment. An attacker with network access to the SCIM endpoint can use this known token to authenticate and perform user and group provisioning operations supported by the configured backend. The defect was removed in version 2026.1 (released July 17, 2026).
Affected products
- Perforce Helix Authentication Service 2022.1 - 2025.2
Timeline
- 2026-10-13: disclosed
- 2026-07-17: patched: Version 2026.1 released with defect removed