CVE Catalog

CVE-2026-109758

CriticalCVSS 9.3
Published: Translated: NVD NIST

Summary

Perforce Helix Authentication Service (HAS) versions 2022.1-2025.2 retain a default SCIM bearer token that is not automatically replaced with a random value during installation. An attacker knowing this token can gain unauthorized access to the SCIM API and perform user and group operations. This issue can be chained with CVE-2026-61834, potentially leading to remote code execution.

Risk Assessment

The organization is exposed to unauthorized access to the authentication system, which could result in account takeover, data modification, and potential remote code execution on the server. When chained with another vulnerability, the attack could lead to full compromise of the service.

Recommendation

Immediately upgrade Perforce Helix Authentication Service to version 2026.1 or later, which removes this flaw. Additionally, manually generate and configure a random SCIM token in the active configuration to prevent exploitation of the default credential.

Related vulnerabilities

Original NVD description (English source)

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 version 25.2, 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. A crafted SCIM PATCH request can cause server-side prototype pollution, corrupt application state, and disrupt service availability, including health checks and SCIM or SSO requests. In a later test, this primitive was confirmed to enable remote code execution in a Node.js 24/Express deployment through available gadget chains involving child_process, EJS/Pug, or Passport.  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.

Vulnerability data from NVD (NIST) · CISA KEV · EPSS