Cyber Resilience

CVE-2026-9222

Published
26 June 2026
Modified
03 August 2026
CVSS Score v4 9.2
Click a component to see what it means
Raw vectorCVSS:4.0/AV:N/AC:L/AT:P/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
EPSS Score 0.0024 16th percentile
Risk Priority 44 floored blend · peak EPSS

Summary

CVE-2026-9222 is a critical-severity Use of Password Hash Instead of Password for Authentication (CWE-836) vulnerability in Githubusercontent (inferred from references). Its CVSS base score is 9.2 (Critical).

Operationally, exploitation aligns with the MITRE ATT&CK technique Pass the Hash (T1550.002); ranked at the 16th percentile by exploit likelihood (below the median); it is not currently listed in the CISA KEV catalog.

The strongest mitigations our analysis identified map to IA-2 (Identification and Authentication (Organizational Users)) and IA-5 (Authenticator Management) — see the control section below for these in your framework.

EU & UK References

Vulnerability Data

Setracker2 Android Companion App com.tgelec.setracker versions 3.1.5 and prior only require the password hash when authenticating with backend services from the client. This could allow an attacker, who knows the hash, to authenticate and gain full access.

CWE(s)
CWE-836

Related Threats

MITRE ATT&CK Enterprise Techniques

T1550.002 Pass the Hash Lateral Movement
Adversaries may “pass the hash” using stolen password hashes to move laterally within an environment, bypassing normal system access controls.
attack.mitre.org →
T1550 Use Alternate Authentication Material Lateral Movement
Adversaries may use alternate authentication material, such as password hashes, Kerberos tickets, and application access tokens, in order to move laterally within an environment and bypass normal system access controls.
attack.mitre.org →
Derived from this CVE’s CWE(s) via the direct CWE→ATT&CK cross-walk.

CVEs Like This One

CVE-2025-64471Shared CWE-836
CVE-2023-4299Shared CWE-836
CVE-2019-25552Shared CWE-836
CVE-2023-39546Shared CWE-836
CVE-2025-48925Shared CWE-836
CVE-2025-52543Shared CWE-836
CVE-2026-40103Shared CWE-836
CVE-2023-34132Shared CWE-836
CVE-2023-23614Shared CWE-836
CVE-2023-23450Shared CWE-836

Affected Assets

Githubusercontent
—
inferred from references and description; NVD did not file a CPE for this CVE

Mitigating Controls

Mitigating Controls (NIST 800-53 r5) AI

IA-2 Identification and Authentication (Organizational Users) partial match

Requires proper identification and authentication of users, which structurally precludes accepting password hashes in place of passwords.

IA-5 Authenticator Management partial match

Authenticator management requires secure distribution, verification, and handling of passwords rather than allowing direct submission and comparison of hashes.

Mitigating Controls (NIST CSF 2.0) AI

Derived directly from the weakness types (CWEs) cited in the NVD entry via our AI-authored CWE→CSF cross-walk (authority under review) — links open the control.

PR.AA-03 mostly match
prevents

Proper authentication mechanisms require passwords (not pre-hashed values) to be supplied by the claimant and verified server-side.

Mitigating Controls (ISO/IEC 27001:2022 Annex A) AI

Derived directly from the weakness types (CWEs) cited in the NVD entry via our AI-authored CWE→ISO cross-walk (authority under review) — links open the control.

A.5.17 Authentication information full match
degrades

Directly requires secure handling and protection of authentication credentials, preventing storage or comparison of password hashes as if they were passwords.

A.8.5 Secure authentication full match
degrades

Mandates secure authentication mechanisms that preclude the flawed practice of treating password hashes as authenticators.

A.8.24 Use of cryptography partial match
degrades

Requires proper cryptographic practices for protecting passwords, indirectly mitigating misuse of hashes in authentication.

A.8.28 Secure coding partial match
prevents

Secure coding guidance can prevent this implementation error but does not address the control's broader intent.

References