CVE-2025-59870: HCL MyXalytics is affected by improper management of a static JWT signing secret in the web application, wher

Routine

HIGH 7.4REMOTEDOWNGRADE

CVE-2025-59870 is a high-severity flaw (CVSS 7.4) affecting myxalytics. Below: why it ranks where it does, which versions are affected, what to do, and the exact commands.

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

Why this priority

High severity
Remotely exploitable, no login, no user action

No fix is published yet: follow the downgrade or mitigation steps.

Risk facts

CVSS score	7.4 (High)
Attack vector	Network (remote)
Attack complexity	High
Privileges needed	None
User interaction	None
EPSS exploit chance	0.3% (top 80%)
CISA exploited list	No
Weakness	CWE-323
Published	2026-01-16
Last modified	2026-06-17

Publisher (CNA): HCL Software · Vendor: hcltech

Last updated 2026-06-17 · Sources: CVE Program, NVD, CISA KEV, EPSS and vendor advisories · How we score

Am I affected?

Timeline

2026-01-16 11:16 UTCPublished CVE record published
2026-06-17 09:46 UTCUpdated Record last modified

hcltech myxalytics DOWNGRADE

Affected: 6.2 · 6.3 · 6.4 · 6.5 · 6.6 · 6.7

Fixed in: no fixed release known

Safe to downgrade to: a release before 6.2

1. Check installed version

apt-cache policy myxalytics || rpm -q myxalytics || myxalytics --version

2. No fixed release: DOWNGRADE to a release before 6.2 (Debian / Ubuntu)

apt-cache madison myxalytics sudo apt install myxalytics=<VERSION_BEFORE_6.2> sudo apt-mark hold myxalytics

2. No fixed release: DOWNGRADE (RHEL / Amazon Linux / Fedora)

dnf --showduplicates list myxalytics sudo dnf downgrade myxalytics-<VERSION_BEFORE_6.2> sudo dnf versionlock add myxalytics

Downgrade risk

Downgrading can break dependent software and may reopen older bugs. Read the distro advisory first and test on a non-production host.

After downgrade

Restart the service, and keep the package held until a fixed release ships.

Verify at the official source NVD · CVE Program · Report a problem with this page
Scores and fixes here are computed automatically from those and other public sources. Confirm with the vendor advisory before changing production systems.

Quick answers

How do I fix CVE-2025-59870?

myxalytics: downgrade or apply the listed mitigation. Exact commands for each OS are on this page.

Is CVE-2025-59870 being exploited?

CVE-2025-59870 is not on the CISA Known Exploited Vulnerabilities list at the time of the last update. Check again, as this can change.

What does CVE-2025-59870 affect?

CVE-2025-59870 affects myxalytics. Severity is high (CVSS 7.4). 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

How urgent is CVE-2025-59870?

Priority 36/100. High severity; Remotely exploitable, no login, no user action

References

← Back to latest CVEs