CVE-2025-59870
Hcltech Myxalytics 6.2 … 6.7
Raw vector
CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:NSummary
CVE-2025-59870 is a high-severity Reusing a Nonce, Key Pair in Encryption (CWE-323) vulnerability in Hcltech Myxalytics. Its CVSS base score is 7.4 (High).
Operationally, ranked at the 15th 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 SA-11 (Developer Testing and Evaluation) and SA-8 (Security and Privacy Engineering Principles) — see the control section below for these in your framework.
Deeper analysis AI-assisted summary
Synthesised by an AI model from the NVD description and linked references — a reading aid, not an authoritative source.
CVE-2025-59870 is a vulnerability in HCL MyXalytics, specifically affecting the web application due to improper management of a static JWT signing secret that lacks rotation, thereby introducing a security risk. Published on 2026-01-16, it carries a CVSS v3.1 base score of 7.4 (AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:N) and maps to CWE-323 (Reused Configuration Management Secret).
Remote attackers require no privileges or user interaction to exploit this vulnerability over the network, though it demands high attack complexity. Successful exploitation enables high-impact compromise of confidentiality and integrity, such as forging or tampering with JWTs using the static, unrotated signing secret.
HCL provides mitigation guidance in its advisory at https://support.hcl-software.com/csm?id=kb_article&sysparm_article=KB0128115.
OWASP Top 10 for Web (2025)
EU & UK References
- 🇪🇺 ENISA EUVD: EUVD-2026-2950
Vulnerability Data
HCL MyXalytics is affected by improper management of a static JWT signing secret in the web application, where the secret lacks rotation , introducing a security risk
- CWE(s)
Related Threats
CVEs Like This One
Affected Assets
Mitigating Controls
Control response
—
—
—
V6.8.3V11.3.4
Mitigating Controls (NIST 800-53 r5) AI
Developer testing and evaluation can discover nonce reuse through static analysis, fuzzing, or known-answer tests.
Engineering principles include correct use of cryptographic primitives such as unique nonces per key.
Selecting and implementing appropriate cryptographic algorithms and modes reduces nonce-reuse exposure.
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 practices directly prevent nonce/key reuse errors in cryptographic implementations.
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.
Mandates proper cryptographic key and nonce management, directly preventing nonce/key-pair reuse.
Security testing can detect nonce reuse, yet the control addresses many other issues beyond this CWE.
Secure-coding rules can require unique nonces, but the control is broader than this single weakness.