CVE-2025-59870: HCL Software MyXalytics · CWE-323
Affects HCL Software MyXalyticsSource CVE Database V5
Not known to be exploited · CVSS 7.4 High : upgrade to 6.7 soon.
Data as of 26 Oct 2026, 10:12 UTC
- EPSS
- 0.2% chance of exploitation in 30 days – higher than 19% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
- Patch
- Available – fixed in 6.7
CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:NExploitation evidence
Disclosed: evidence found.
CVE published 16 Jan 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponised: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors
A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 26 Oct 2026.
What to do
Upgrade HCL Software MyXalytics to 6.7.
Affected software
| Product | Affected | Fixed in |
|---|---|---|
| HCL SoftwareMyXalytics | Affected
| Fixed in
|
AI-suggested
- Implement immediate rotation of the JWT signing secret to invalidate any potentially compromised tokens and reduce exposure time.
- Restrict access to the signing secret within the application environment using strict access controls and environment segmentation.
- Monitor authentication logs and token usage patterns for anomalies indicative of token forgery or misuse.
- Apply network-level protections such as Web Application Firewalls (WAFs) to detect and block suspicious token-related activities.
- 6. Consider deploying additional authentication layers, such as multi-factor authentication (MFA), to reduce the risk of unauthorized access even if tokens are forged. 7. Conduct a security review of JWT implementation across the environment to ensure adherence to best practices, including secret rotation policies and secure storage. 8. Educate development and operations teams on secure key management and the risks of static secrets. 9. If patching is delayed, consider temporary mitigations such as reducing token lifetime to limit the window of exploitation.
Description
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