Raw vector
CVSS:3.1/AV:L/AC:L/PR:H/UI:N/S:C/C:H/I:N/A:NSummary
CVE-2025-26486 is a medium-severity Use of a Broken or Risky Cryptographic Algorithm (CWE-327) vulnerability in Europa (inferred from references). Its CVSS base score is 6.0 (Medium).
Operationally, exploitation aligns with the MITRE ATT&CK technique OS Credential Dumping (T1003); ranked at the 2th 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 SC-13 (Cryptographic Protection) and IA-5 (Authenticator Management) — see the control section below for these in your framework.
OWASP Top 10 for Web (2025)
EU & UK References
- 🇪🇺 ENISA EUVD: EUVD-2025-6781
- 🇪🇺 ENISA: euvd.enisa.europa.eu
Vulnerability Data
Broken or Risky Cryptographic Algorithm, Use of Password Hash With Insufficient Computational Effort, Use of Weak Hash, Use of a One-Way Hash with a Predictable Salt vulnerabilities in Beta80 "Life 1st Identity Manager" enable an attacker with access to password…
more
hashes to bruteforce user passwords or find a collision to ultimately while attempting to gain access to a target application that uses "Life 1st Identity Manager" as a service for authentication. This issue affects Life 1st: 1.5.2.14234.
- CWE(s)
Related Threats
MITRE ATT&CK Enterprise Techniques
CVEs Like This One
Affected Assets
Mitigating Controls
Control response
—
—
- 13 hardening rules · 6 OS baselines
V11.2.3V6.5.2V11.4.2
Mitigating Controls (NIST 800-53 r5) AI
SC-13 requires selection and implementation of specific cryptography types, directly stopping use of broken algorithms.
Authenticator management requires secure generation, distribution, and storage of passwords, directly enforcing computationally expensive hashing schemes.
Protection of information at rest requires cryptographic safeguards on stored password hashes, reducing exposure to offline cracking.
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.
Secure-SDLC requirements explicitly forbid weak cryptographic algorithms, fully preventing CWE-328 while covering only one aspect of development practice.
Proper data-at-rest integrity protection requires strong cryptographic hashes, directly blocking weak-hash usage.
Data-in-transit integrity likewise depends on strong hashes, so the control prevents the weakness while the weakness only partially satisfies the outcome.
Authentication policies may reference password handling but do not address storage or computational cost of hashes.
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.
Mandating approved algorithms, cipher strength and usage standards directly stops the selection of broken or weak cryptographic primitives that attackers can exploit.
Security testing can detect weak-hash usage but does not prescribe algorithm choice.
Requires secure handling of authentication information, which includes choosing strong password hashing schemes.
The explicit call-out of cryptography-related legal constraints (import/export, key escrow, digital-signature validity) reduces the likelihood that an organization will adopt broken or non-compliant cryptographic algorithms that violate those rules.
Access to current specialist guidance and early vulnerability alerts enables timely replacement of broken or risky cryptographic algorithms with stronger alternatives.
Secure development life cycle includes secure coding practices that would catch predictable-salt usage during design and implementation.
Hardening callouts derived
Configuration rules from DISA STIG baselines that bear on weaknesses of the type cited by this CVE. Each rule is shown with the relationship its mapping actually records, against the CWE it was authored against. Derived via CVE→CWE over `controls_xwalks` (authoritative rows only; rows rated `none` are excluded).
Oracle Linux 8 (1 rule)
- V-248524 OL 8 must implement NIST FIPS-validated cryptography for the following: To provision digital signatures, to generate cryptographic hashes, and to protect data requiring data-at-rest protections in accordance with applicable federal laws, Executive Orders, directives, policies, regulations, and standards. prevents CWE-327
Windows 10 (1 rule)
- V-220937 The system must be configured to prevent the storage of the LAN Manager hash of passwords. prevents CWE-327, CWE-328
Windows 11 (1 rule)
- V-253461 The system must be configured to prevent the storage of the LAN Manager hash of passwords. prevents CWE-327, CWE-328
Windows Server 2016 (1 rule)
- V-225053 Windows Server 2016 must be configured to prevent the storage of the LAN Manager hash of passwords. prevents CWE-327, CWE-328
Windows Server 2019 (1 rule)
- V-205654 Windows Server 2019 must be configured to prevent the storage of the LAN Manager hash of passwords. prevents CWE-327, CWE-328
Windows Server 2022 (1 rule)
- V-254474 Windows Server 2022 must be configured to prevent the storage of the LAN Manager hash of passwords. prevents CWE-327, CWE-328