Perforce Helix Authentication Service (HAS) deployments that retain the shipped default SCIM bearer token are vulnerable to unauthorized access when the SCIM endpoint is reachable by an attacker. In affected versions of HAS, the installation templates contain a default credential which the installer copies into the active configuration; the installer and configuration script do not automatically replace that value with a random token. An attacker who knows the default token can authenticate to the SCIM API and perform user and group operations allowed by the configured provisioning backend.
This issue can be chained with CVE-2026-61834 in affected releases of the scim-patch dependency.
This vulnerability exists in version 2022.1 - 2025.2 of HAS however the underlying defect was removed in version 2026.1 which was released July 17th 2026. The vulnerability was identified in older versions of HAS after version 2026.1 was released.
0.4%(unchanged from 0.4% a week ago; 0.4% 30 days ago) estimated probability of exploitation activity in the next 30 days; 30th percentile. Scored 2026-11-17. A forecast for this CVE across the internet, not for your own systems.
CISA's assessment (SSVC)
Exploitation: none · Automatable: yes · Technical impact: total, assessed 2026-10-14. From CISA's Vulnrichment in the CVE List: whether it is exploited, whether exploiting it can be automated, and how much control it gives.
CWEs
CWE-798Use of Hard-coded Credentials CWE-1321Improperly Controlled Modification of Object Prototype Attributes (Prototype Pollution)
Show the promptExplain CVE-2026-109758 for an engineer deciding whether to act. Use https://cve.bz/api/public/cves/CVE-2026-109758?via=ask-ai-copy and https://cve.bz/cve/CVE-2026-109758?via=ask-ai-copy as the source of truth: what is affected and which versions fix it, whether it is in CISA KEV, public exploits, and its EPSS (an internet-wide 30-day estimate of exploitation activity, not a forecast for my systems). If they give no fixed versions, use the CVE record https://cveawg.mitre.org/api/cve/CVE-2026-109758 or the vendor advisory, not third-party mirrors. Tell me how to check whether I am affected and how to verify a fix. Cite the sources and say where they are uncertain.
Opens a third-party assistant; its answer is its own, not cve.bz's. The prompt holds only this CVE's id and public links.
Affected
perforce:helix authentication service
Versions
From the CNA's record in the CVE List.
Product
Affected
Perforce Helix Authentication Service
from 2022.1 through 2025.2
Fixed in
Product
Fixed in
Perforce Helix Authentication Service
2026.1
Attack patterns (CAPEC)
CAPEC-70 Try Common or Default Usernames and Passwords Likelihood: Medium · Severity: High
CAPEC-191 Read Sensitive Constants Within an Executable Severity: Low
CAPEC-1 Accessing Functionality Not Properly Constrained by ACLs Likelihood: High · Severity: High
CAPEC-77 Manipulating User-Controlled Variables Likelihood: High · Severity: Very High
CAPEC-180 Exploiting Incorrectly Configured Access Control Security Levels Likelihood: High · Severity: Medium
The attack patterns MITRE's CAPEC relates to this record's weaknesses, as MITRE names them. Credits.