CVE-2026-5794
Raw vector
CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:N/VI:N/VA:H/SC:N/SI:N/SA:N/E:U/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:XSummary
CVE-2026-5794 is a medium-severity Use of Multiple Resources with Duplicate Identifier (CWE-694) vulnerability in Cryptobox (inferred from references). Its CVSS base score is 4.9 (Medium).
Operationally, ranked at the 17th 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-4 (Identifier Management) — see the control section below for these in your framework.
EU & UK References
- 🇪🇺 ENISA EUVD: EUVD-2026-26070
Vulnerability Data
A vulnerability affecting the detailed versions of Cryptobox allows a legitimate user to prevent another to login by triggering an account lockout via sending a specially crafted request.
- CWE(s)
Related Threats
CVEs Like This One
Affected Assets
Mitigating Controls
Control response
—
—
—
V8.4.1V3.5.4V6.8.1V9.2.4
Mitigating Controls (NIST 800-53 r5) AI
Identifier management directly requires authorization and uniqueness controls that stop duplicate resource identifiers from being assigned or used.
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.
Maintaining software/service inventories requires and enforces unique identifiers to avoid collisions.
Managing identities and credentials for users/services/hardware directly requires unique identifiers.
Lifecycle management of assets includes identifier uniqueness as a supporting practice.
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.
Security testing can detect duplicate identifiers before deployment.
Identity management processes that enforce unique identifiers directly prevent duplicate resource IDs.
Secure development lifecycle practices can catch duplicate-ID issues during design and code review.
Secure coding standards can mandate unique identifier generation and validation.
Configuration management ensures unique identifiers are assigned and maintained across resources.