CVE-2025-59870
Published: 16 January 2026
Summary
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, exploitation aligns with the MITRE ATT&CK technique Forge Web Credentials (T1606); ranked at the 14.4th percentile by exploit likelihood (below the median); it is not currently listed in the CISA KEV catalog.
The strongest mitigations our analysis identified are NIST 800-53 SC-12 (Cryptographic Key Establishment and Management) and IA-5 (Authenticator Management).
Deeper analysis
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 details
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
MITRE ATT&CK Enterprise TechniquesAI
Why these techniques?
Static unrotated JWT signing secret directly enables adversaries to forge valid JWT tokens for authentication bypass and impersonation (T1606 Forge Web Credentials).
CVEs Like This One
Affected Assets
Mitigating Controls
Mitigating Controls (NIST 800-53 r5) AI
Directly requires cryptographic key establishment and management procedures that include rotation of secrets such as the static JWT signing key.
Mandates secure authenticator management practices that encompass generation, distribution, and rotation of secrets used for authentication tokens like JWTs.
Requires mechanisms to protect session authenticity, which is undermined when a static unrotated JWT signing secret allows forgery or tampering.