CVE-2025-59698
Entrust Nshield 5C Firmware ≤ 13.6.12
Raw vector
CVSS:3.1/AV:P/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:HCVSS and EPSS are reproduced from their sources (NVD, FIRST EPSS). Risk Priority is our own derived reading, not an NVD score.
Summary
CVE-2025-59698 is a medium-severity Generation of Incorrect Security Tokens (CWE-1270) vulnerability in Entrust Nshield 5C Firmware. Its CVSS base score is 6.8 (Medium).
Operationally, exploitation aligns with the MITRE ATT&CK technique Forge Web Credentials (T1606); ranked at the 21th percentile by exploit likelihood (below the median); it is not currently listed in the CISA KEV catalog; a public proof-of-concept is referenced.
The strongest mitigations our analysis identified map to SA-11 (Developer Testing and Evaluation) and AC-16 (Security and Privacy Attributes) — see the control section below for these in your framework.
EU & UK References
- 🇪🇺 ENISA EUVD: EUVD-2025-200256
Vulnerability Data
Entrust nShield Connect XC, nShield 5c, and nShield HSMi through 13.6.11, or 13.7 (patched in 13.6.12 (LTS) and 13.9.0 (STS)), might allow a physically proximate attacker to gain access to the EOL legacy bootloader.
- CWE(s)
Related Threats
MITRE ATT&CK Enterprise Techniques
CVEs Like This One
Affected Assets
Mitigating Controls
Mitigating Controls (NIST 800-53 r5) AI
Developer testing and evaluation can discover flaws that produce incorrect security tokens before deployment.
Correct association and handling of security attributes directly governs generation of valid tokens used for authorization decisions.
Requiring documented, secure development processes and tools reduces the chance of implementing faulty token-generation logic.
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.
Security testing in development can detect incorrect token generation before deployment.
Proper use of cryptography ensures tokens are generated with correct algorithms, keys and entropy.
Secure development lifecycle practices include requirements and reviews that prevent flawed token-generation logic.
Application security requirements explicitly call for correct token issuance and validation mechanisms.
Secure coding standards reduce the likelihood of implementation errors that produce incorrect tokens.
Secure authentication mechanisms directly govern the correct generation and validation of security tokens.