CVE-2026-109758: Software Security Vulnerability Vulnerability

CRITICAL
Advisory Identifier: GHSA-8m68-j7cp-5rcm
Share
CWE-798
Published
Advisory Summary

CVE-2026-109758 is a CRITICAL security vulnerability vulnerability (CWE-798: Use of Hard-coded Credentials) affecting Software libraries in the Maven ecosystem. The weakness occurs when the product contains hard-coded credentials, such as a password or cryptographic key.. Remediation is available in the latest vendor maintenance releases.

CVE-2026-109758 at a Glance

CVE Identifier CVE-2026-109758
GHSA Identifier GHSA-8m68-j7cp-5rcm
Severity CRITICAL
CVSS v3.1 Base Score N/A
CWE Classification CWE-798: Use of Hard-coded Credentials
Affected Product Software
Package Ecosystem Maven
Published Date
Last Updated

How to Fix CVE-2026-109758

To remediate this vulnerability, upgrade all affected Software dependencies to a patched release. Both direct and transitive dependencies should be checked, as frameworks or security libraries may pull in vulnerable versions transitively.

Verify Direct and Transitive Dependencies

Run the following command in your project directory to verify that all resolved dependencies use the patched release: 

mvn dependency:tree

How to Check if You Are Affected

To determine whether your Java application is affected by CVE-2026-109758, inspect your build dependencies using the Maven Dependency Plugin:

mvn dependency:tree

Analyze the terminal output to locate any version of Software in your dependency tree. If any resolved version matches the vulnerable ranges listed in the table below (for example, versions earlier than the patched release), your application is affected.

Note: The mvn dependency:tree command inspects the resolved dependency graph declared in your project's POM files; it does not perform automated security scanning or inspect runtime dynamic classpaths. Always verify runtime container classpaths and shaded JARs.

Technical Details

Vulnerability Mechanism & Technical Analysis

This vulnerability is classified under CWE-798: Use of Hard-coded Credentials, where the product contains hard-coded credentials, such as a password or cryptographic key. In Software, software state validation or input boundaries are circumvented during processing. Review the official source advisory statement below for specific affected components, classes, and reproduction details.

Source Advisory Statement

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.

References

NVD — CVE-2026-109758 NVD
https://nvd.nist.gov/vuln/detail/CVE-2026-109758
perforce1.lightning.force.com/lightning/r/cve__c/... WEB
https://perforce1.lightning.force.com/lightning/r/CVE__c/a91Qi000003GITtIAO/view
portal.perforce.com/s/cve/a91qi000003gi... WEB
https://portal.perforce.com/s/cve/a91Qi000003GITtIAO/unauthenticated-rce-via-prototype-pollution-in-helix-authentication-service

Frequently Asked Questions

What is CVE-2026-109758?
CVE-2026-109758 is a security vulnerability in Software classified as a security vulnerability vulnerability under CWE-798: Use of Hard-coded Credentials.
Which Software versions are affected?
Affected versions include releases prior to current release patches.
What version fixes CVE-2026-109758?
Upgrading to current release patches (or the latest patched release for your respective branch) resolves the vulnerability.
What CWE is associated with CVE-2026-109758?
CVE-2026-109758 is classified under CWE-798: Use of Hard-coded Credentials (The product contains hard-coded credentials, such as a password or cryptographic key.).
How can I check Maven dependencies for CVE-2026-109758?
Run the dependency tree command: 'mvn dependency:tree'. This command lists direct and transitive dependencies in your build configuration so you can verify if a vulnerable version is resolved.
Machine-readable OSV JSON OSV v1.5 Schema
Normalized schema output
View Raw JSON 
{
  "schema_version" : "1.4.0",
  "id" : "GHSA-8m68-j7cp-5rcm",
  "modified" : "2026-10-15T18:31:51Z",
  "published" : "2026-10-13T06:30:26Z",
  "aliases" : [ "CVE-2026-109758" ],
  "details" : "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. \n\n\n\n\n\nThis 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. \n\n\n\n\n\nThis 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.",
  "severity" : [ {
    "type" : "CVSS_V4",
    "score" : "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/E:X/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:X"
  } ],
  "affected" : [ ],
  "references" : [ {
    "type" : "ADVISORY",
    "url" : "https://nvd.nist.gov/vuln/detail/CVE-2026-109758"
  }, {
    "type" : "WEB",
    "url" : "https://perforce1.lightning.force.com/lightning/r/CVE__c/a91Qi000003GITtIAO/view"
  }, {
    "type" : "WEB",
    "url" : "https://portal.perforce.com/s/cve/a91Qi000003GITtIAO/unauthenticated-rce-via-prototype-pollution-in-helix-authentication-service"
  } ],
  "database_specific" : {
    "cwe_ids" : [ "CWE-798" ],
    "severity" : "CRITICAL",
    "github_reviewed" : false,
    "github_reviewed_at" : null,
    "nvd_published_at" : "2026-10-13T04:17:14Z"
  }
}