CVE-2026-28745
Raw 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/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:XCVSS and EPSS are reproduced from their sources (NVD, FIRST EPSS). Risk Priority is our own derived reading, not an NVD score.
Summary
CVE-2026-28745 is a critical-severity Storing Passwords in a Recoverable Format (CWE-257) vulnerability in Hms Networks (inferred from references). Its CVSS base score is 9.3 (Critical).
Operationally, exploitation aligns with the MITRE ATT&CK technique Data Obfuscation (T1001); ranked at the 11th 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-5 (Authenticator Management) — see the control section below for these in your framework.
EU & UK References
- 🇪🇺 ENISA EUVD: EUVD-2026-95811
Vulnerability Data
Usernames and passwords, including the default credentials, are stored in the configuration file using weak encryption. If the default credentials are known by a malicious user, they could obtain other credentials on the system.
- CWE(s)
Related Threats
MITRE ATT&CK Enterprise Techniques
CVEs Like This One
Affected Assets
Mitigating Controls
Control response
—
—
—
V11.4.2V11.4.4
Mitigating Controls (NIST 800-53 r5) AI
Where authenticator management reaches, recoverable-format storage never arises. Mostly, not full: the base text is less specific than IA-5(1) and the locus does not cleanly reach every first-party application store.
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.
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's password management system requirements (h: store/transmit in protected form; approved crypto per 8.24; no recoverable formats implied by strong practices) stop exploitation of recoverable storage for most cases, but the remainder (non-password auth info or systems outside the password management system) is nameable.
Requires proper use of cryptography, which can mitigate recoverable storage if applied correctly to passwords.
A.8.25 requires that security be designed and implemented in the SDLC (including secure coding, requirements, testing and training), but does not itself stop a recoverable-format password from being written into the product or stop that stored password from being exploited afterwards
A.8.26 only requires that recoverable-format storage be identified as a risk and specified as a requirement; it does not itself mandate, design or implement non-recoverable storage, so the flaw (passwords stored in recoverable form) can still exist after the control is satisfied.