IT SBIT Services
Schneeberger
DEEN
CVE tracker

Perforce Helix Authentication Service: Hard-coded default SCIM bearer token

CVE-2026-109758Critical 9.3

← All vulnerabilities

Summary

Perforce Helix Authentication Service (HAS) versions 2022.1 through 2025.2 ship with a default SCIM bearer token that the installer copies into the active configuration without replacing it. An attacker who knows this static token and can reach the SCIM endpoint can authenticate to the SCIM API and perform user and group operations allowed by the configured provisioning backend. The issue can be chained with CVE-2026-61834 in the scim-patch dependency. The vendor's CVE title refers to remote code execution via prototype pollution, but RCE is not confirmed in the vendor advisory.

Affected

  • Perforce Helix Authentication Service 2022.1 through 2025.2
  • Dependency scim-patch before 0.9.2 (CVE-2026-61834) in affected releases; bundled version per HAS release unknown
  • Default configurations that retain the shipped SCIM bearer token and expose the SCIM endpoint

Fixed in

  • Perforce Helix Authentication Service 2026.1 (released July 17, 2026)
  • scim-patch 0.9.2 for the chained dependency issue

Workaround

  • Rotate the SCIM bearer token to a unique random value, since the installer does not do this automatically
  • Restrict network access to the SCIM endpoint to the identity provider or other trusted sources (recommendation, not a vendor statement)
  • Verify the current token-handling procedure in the admin guide
  • No vendor-documented interim workaround found; upgrading is the primary fix

Exploitation

  • Not listed in CISA's Known Exploited Vulnerabilities catalog; no reports of exploitation found
  • No public exploit code confirmed
  • CISA SSVC: exploitation none, automatable yes, technical impact total
  • The chained scim-patch issue (CVE-2026-61834) is marked with a proof of concept in CISA ADP SSVC data

Our recommendation

  • Upgrade Perforce Helix Authentication Service to 2026.1 or later
  • If upgrading is not immediately possible, rotate the SCIM bearer token and restrict SCIM endpoint access
  • Check whether SCIM is enabled and whether the endpoint is reachable from the internet or untrusted networks; treat internet-reachable deployments as high priority
  • Review the scim-patch version in your HAS installation and lockfiles and update to 0.9.2 or later
  • Review SCIM provisioning logs for unexpected user or group changes

Public exploits

PoC-in-GitHub, Metasploit and Exploit-DB list nothing for this CVE.

Research sources

Researched and written up in English and German by an AI (Claude by Anthropic) based on NVD, CISA, EPSS and the sources listed. The vendor information is authoritative. Researched on 31 Oct 2026, 02:23.

Original description (NVD)

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.

NVD references (1)

Sources

The tracker combines official, freely usable data sources – updated continuously:

This product uses data from the NVD API but is not endorsed or certified by the NVD. EPSS data © FIRST.org.

Affected? We can help.

We check whether your systems are affected, install updates and close the gap – continuously with the System Health Checker if you wish.