# CVE-2026-109758: Hardcoded credentials in Helix Authentication Service

> Attackers can use default SCIM bearer tokens to authenticate and modify user/group data in Perforce Helix Authentication Service.

- **Severity:** Critical 9.3 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 13 Oct 2026
- **Updated:** 15 Oct 2026
- **Also known as:** GHSA-8m68-j7cp-5rcm

## What is CVE-2026-109758?

CVE-2026-109758 is a critical vulnerability in Perforce Helix Authentication Service, published on 13 Oct 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

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.

Weakness: CWE-798 (Use of Hard-coded Credentials), CWE-1321 (Improperly Controlled Modification of Object Prototype Attributes)

## Which versions are affected by CVE-2026-109758?


## How do I fix CVE-2026-109758?

No fix has been published for CVE-2026-109758 yet. Limit exposure of the affected software until one is available.

## Is CVE-2026-109758 being exploited?

There is no known exploitation of CVE-2026-109758 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-109758 and fix it if it is affected.

What it is: CVE-2026-109758 is a critical vulnerability in Perforce Helix Authentication Service, published on 13 Oct 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2026-109758 in the wild and no public exploit code.

Affected product: Perforce Helix Authentication Service. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-109758/ (Markdown: https://insights.sbomify.com/CVE-2026-109758/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-109758
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-109758
- OSV: https://osv.dev/vulnerability/CVE-2026-109758

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-109758/
Summaries are generated and may contain mistakes; the official description above is the record.