{"answers":{"affected":"","exploited":"There is no known exploitation of CVE-2026-109758 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2026-109758 yet. Limit exposure of the affected software until one is available.","what":"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."},"fix_prompt":"Check this codebase for CVE-2026-109758 and fix it if it is affected.\n\nWhat 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.\nExploitation: There is no known exploitation of CVE-2026-109758 in the wild and no public exploit code.\n\nAffected product: Perforce Helix Authentication Service. No package-level version data is available, so check the vendor advisory linked from the reference page.\n\nTask:\n1. 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.\n2. 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.\n3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.\n4. Run the tests and summarise what changed and why.\n5. If nothing in the project is affected, say so and change nothing.\n\nReference: https://insights.sbomify.com/CVE-2026-109758/ (Markdown: https://insights.sbomify.com/CVE-2026-109758/index.md)","id":"CVE-2026-109758","markdown":"https://insights.sbomify.com/CVE-2026-109758/index.md","name":"CVE-2026-109758","record":{"aliases":["GHSA-8m68-j7cp-5rcm"],"analysis":{"component_type":"server_software","fix_type":"upgrade","impacts":["privilege_escalation","data_modify"],"network_reachable":"yes","non_default_config":false,"product_category":"Perforce Helix Authentication Service","requires_auth":"none","summary":"Attackers can use default SCIM bearer tokens to authenticate and modify user/group data in Perforce Helix Authentication Service.","user_interaction":"not_required","vuln_class":"hardcoded_credentials"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"Perforce","cpe":[],"cvss":{"score":9.3,"severity":"critical","source":"cna","vector":"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","version":"4.0"},"cwes":[{"id":"CWE-798","name":"Use of Hard-coded Credentials"},{"id":"CWE-1321","name":"Improperly Controlled Modification of Object Prototype Attributes"}],"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.\n\nThis issue can be chained with CVE-2026-61834 in affected releases of the scim-patch dependency.\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.","ecosystems":[],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"none_known"},"has_fix":null,"headline":"Hardcoded credentials in Helix Authentication Service","id":"CVE-2026-109758","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"hardcoded_credentials","year":"2026"},"n_packages":0,"n_references":1,"next":{"headline":"Site isolation issue in the Networking component","id":"CVE-2026-109759"},"packages":[],"prev":{"headline":"Sandbox escape due to race condition in the Networking component","id":"CVE-2026-109757"},"products":["Helix Authentication Service"],"published":"2026-10-13","related":[],"sources":[{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"},{"class":"attribution","licence":"CWE Terms of Use","name":"CWE (MITRE)"},{"class":"attribution","licence":"FIRST CVSS licence","name":"CVSS (FIRST)"}],"ssvc":{"automatable":"yes","exploitation":"none","technical_impact":"total"},"state":"PUBLISHED","updated":"2026-10-15","vendors":["Perforce"]},"summary":"Attackers can use default SCIM bearer tokens to authenticate and modify user/group data in Perforce Helix Authentication Service.","url":"https://insights.sbomify.com/CVE-2026-109758/"}